1. You wanted to have one editor anyway, why would we keep multiple configs for different ones?
2. Atom.io is designed to be very flexible, I'm 99% sure there is a way to add more colors
3. That IS a problem but there is nothing we can do about that, the best we could do anyway is to make the editor guess what type of file is that or change extensions to be something custom
4. From what I understand, the gettext architecture is not designed to work like that, but exactly the opposite. You are supposed to edit only the one *.po file so you don't have to even open original files, because you have the original text in the line above. It also makes sure the general structure of the file is the same across all the languages (you cannot freely modify it).
As for our non standard syntax, like I said, atom.io is very flexible. From what I've seen, you don't specify the keywords to highlight, you actually specify regexps, and configure a color for each match group. So you can, for example set an regexp on \l;something\u target_file; and have the link text, target and formatting tags each colored differently but only if the WHOLE thing is correct.
EDIT: Oh, and I'm pretty sure you could make SatCom preview render in atom.io if you have time to learn the API
2. Atom.io is designed to be very flexible, I'm 99% sure there is a way to add more colors
3. That IS a problem but there is nothing we can do about that, the best we could do anyway is to make the editor guess what type of file is that or change extensions to be something custom
4. From what I understand, the gettext architecture is not designed to work like that, but exactly the opposite. You are supposed to edit only the one *.po file so you don't have to even open original files, because you have the original text in the line above. It also makes sure the general structure of the file is the same across all the languages (you cannot freely modify it).
As for our non standard syntax, like I said, atom.io is very flexible. From what I've seen, you don't specify the keywords to highlight, you actually specify regexps, and configure a color for each match group. So you can, for example set an regexp on \l;something\u target_file; and have the link text, target and formatting tags each colored differently but only if the WHOLE thing is correct.
EDIT: Oh, and I'm pretty sure you could make SatCom preview render in atom.io if you have time to learn the API