Thank you! Although I still don't see every detail, the outlines became clearer.
So for a trunk script it looks like this to me at the moment:
- Use the translate key in the script.
- Write keys and values (translations) into rewrite/i18n subdirectory.
- Commit both.
- On update, trunk will get the values from rewrite as externals
automatically. 5. Tell Siebrand about the new keys. 6. Siebrands imports new keys (new values as well?) to TW manually. 7. Translators translate. 8. New translations are exported from TW to SVN autonatically. Right?
Seems right. The howto you could find at http://www.mediawiki.org/wiki/Manual:Pywikipediabot/i18n_conversion
So shall I install the rewrite branch as well to be able to commit translations, or is it enough to download the i18n subdirectory and set the repository for it?
only i18n subdirectory is needed if you don't want so play with other stuff of rewrite branch.
Which is the place I am supposed to do a new translation for an existing key? TW or SVN?
Please suppose new translations to existing keys at twn only. Otherwise the must be backported or mostly they would be deleted by overriding the existing files during twn export.
Regards xqt