No objections were raised, some of the members actually loved it :-)
So the modifications we can do:
For the source English file we can have it like this:
<string id="392" context="Weather addon, chance of rain">Medium</string>
For the translation files we can have them like this.
<string id="392" source="Medium">Közepes</string>
@Viljo: Can you help me create a py script which fetches the English source string at specific revision, and also fetches the language file at latest git revision and creates the new language strings.xml file like the second sample format.
Also would be good if you could modify the source xliff creation script to be able to use the context attribute field I presented in the first sample format.
Well the best would be if we could implement to read these new format files in Transifex. As the xliff parser is pretty simple http://code.indifex.com/transifex/src/02...s/xliff.py we could directly use these new format xml files as we now have in one xml file the source and target not like before.
Viljo, can you help out, or should I start them it in C++ ?
Thanks in advance
ps.: I had Transifex working quite well on Fedora 16 using the current snapshot. I modified the Google shared doc, how I did it. I don't want to run it on a server, but for maybe implementing a native new xbmc strings.xml format it is needed to test the parser before we send to the Transifex developers.