-On [20060916 09:37], Nicolas Ternisien ([EMAIL PROTECTED]) wrote: >My first question is : What about putting TracFrenchTranslation >directly in Trac SVN, in a branch for example. With this, it will be >really easier to apply trunk/ patches using svn merge. Of course, this >will need to remove the current project in trac-hacks.org, but it >should not be a problem if French translation is located in main Trac >project.
Having done my share of various i18n projects and translations I want to point out the following: 1) Adding them to the main project means you would need someone active for every language you add in this manner, simply because if the main authors change things around these changes need to be reflected in the translations. If they are not you get either outdated texts, English default texts. Both look bad. 2) I am not entirely sure how much the source tree would grow if you add every translation to the tree. The tarballs aren't a problem since you will effectively compress them using gzip or bzip2 anyway and text compresses perfectly. 3) Putting the translations in the tree would typically encourage native speakers or people with a sufficient proficiency level to work on these texts. This as opposed to some external project. Also you can leverage from typical l10n frameworks to minimize duplication and only focus on the texts. -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ Time will tell everything - given time... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~----------~----~----~----~------~----~------~--~---
