[viljoviitanen]

Wow ! This is getting there :-)

A few things I noticed:

- We have 1351 strings in Transifex for Hun and Finnish. In the XML we have much more. The Ids are only there up to 16022. Is it a limitation of the API or curl or why the rest did not go in ?

- When we initially create the language, I think we should always use the base English strings in the version when the translated string was translated. This way the translator not only can see the missing ones, but also the changed ones compared to the fresh git version. It will be a PITA first but I think worth it. I will help of course to figure out all git versions for each language.

- I still believe (and that is the wish of the XBMC team) to have some kind of supervision control for the native language team members over what is going into trunk or what should be revised etc. Therefore I think it is necessary to maintain one git repository just for all the language files. After revision from other team members, here the language files will be pulled in by me manually. This repo is also useful to control what is actually should come to public translation. I mean there are some envelopment tasks where the strings change frequently until they reach a more less stable state. That is when I wish to push these strings into the intermediate git repo. This repo is also quite useful to maintain the addon strings coming from various sources from git, svn, to normal zip. I undertake to maintain this and cooperate with addon developers. As I read Transifex has an automatic pull function from GIT. So might be that we don't need to use the API for language file update. Only maybe fetching down the translated files.

Could you please upload the used xliff files for review ?

Anyway things looking very promising. Thanks for the help !

ps.: Do you know where can the gui language of Transifex itself can be set ? When I tested it running myself it had an option to change, but on transifex.net I don't see it.

I got the missing strings thing, transifex stops processing when the source string is empty.

Last string in transifex core translation is Bob (inverted), and:

<string id="16022">Bob (inverted)</string>
<string id="16023"></string>

You can recreate the xliff files with the shell script easily from any unix machine which has bash, wget and python.. so almost any

Anyway I fixed the xliff generator not to put empty strings in the xliff files, now all the non-empty strings are there. I deleted the previous translations from transifex and uploaded new strings there with the script. I also updated my github repo with the changes.

...

About control and intermediate repos:

You're absolutely right, an intermediate repo is probably the best thing to do.

But the automatic pull from transifex can be done if we host xliff files in the "intermediate" repo. But even then it's only for source files. So it's really not much use, it's better to do the integration via the api anyway and store xbmc string.xml files in the intermediate repo, I think. We'll want to keep integration simple between the intermediate repo and other repos, and do the converting between transifex and intermediate repo.

Actually an option would be to keep "control" in transifex, but when addon developers (hopefully) start using this thing, an intermediate repo probably is the best thing to do, with direct two-way transifex integration and then from there controlled pulls to main repos.

Perhaps the intermediate repo could also automatically pull any changes from main repos, so any changes there would be automatically pushed to transifex, as probably a portion of the translation work will still be done the old way. And at least the source files would need automatic updates to the intermediate repo anyway.