← Back to team overview

widelands-dev team mailing list archive

Widelands and the launchpad translation process

 

Hi,

i've some question to the whole translation process in launchpad:

1.) the lp translation facility reads the *.pot files of trunk
2.) Those strings can be translated by the user via lp web gui.
3.) Once a day lp generates the po-files and stores them in the branch
"translations"

Correct me, if i am wrong so far ;).

My question is, how to include the new user translation perhaps on a
more regular base in my (daily) builds?
Just merging the translation branch doesn't seem to do the thing,
because the pot files in trunk were outdated. Perhaps we can agree on
updating the pot files in trunk at least once a week?

Also i noticed due to the updating of the pot files in trunk by SirVer
last night, that many translations got lost in launchpad. Before the
update the new tutorial campaign was completely translated in german.
Now 125 out of 163 strings are untranslated.
I am not sure if really the strings in the campaign changed so much to
cause this...
But when, we should find a way to prevent users from translating in
launchpad during some phases of development when the language catalogs
are under constant changes. Otherwise user get perhaps discouraged to
translate in the future when they have to do it twice or more often...

Kind regards,
Tino


PS@SirVer:
Is it intended that the strings in the tutorial campaign have so many
hardcoded line breaks?



Follow ups