2012/2/12 <info@gno.de>
As i18n stared during a hackatron it was implemented for rewrite branch only and I ported it to the trunk version. That's the reason why the files are place in the rewrite branch. You should not place new translation files to the trunk but the rewrite release. All new translations should be done at twn only after the file is ported.

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:
1. Use the translate key in the script.
2. Write keys and  values (translations) into rewrite/i18n subdirectory.
3. Commit both.
4. 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?

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?

Which is the place I am supposed to do a new translation for an existing key? TW or SVN?

--
Bináris