Hello, the aim of this e-mail is to look at the current status/workflow of l10n for subversion, and propose the move to Apache's Pootle instance for better tooling and the inclusion of potential translators.
Pootle is a web based localisation system. It works with po files and offers web based editing and reviewing. I think the most important benefit for our project would be the openness to translation suggestions from irregular or first time contributors who might be facing a non-trivial barrier to entry.[1] Let's look at numbers fist: Translation status report for trunk@r1509800 > lang trans untrans fuzzy obs > -------------------------------------- > de 2627 13 30 417 +++++++++++++++++++++++++++++~oooo > es 2160 480 674 501 +++++++++++++++++++UUUU~~~~~~~oooo > fr 2449 191 308 62 ++++++++++++++++++++++++UU~~~~ > it 2024 616 812 314 +++++++++++++++++UUUUU~~~~~~~~oo > ja 2150 490 723 742 +++++++++++++++++++UUUU~~~~~~~oooooo > ko 2286 354 482 187 +++++++++++++++++++++UUUU~~~~~o > nb 2206 434 619 476 ++++++++++++++++++++UUUU~~~~~~oooo > pl 2229 411 584 268 ++++++++++++++++++++UUUU~~~~~~oo > pt_BR 1993 647 822 301 +++++++++++++++++UUUUU~~~~~~~~oo > sv 2601 39 72 0 ++++++++++++++++++++++++++++U~ > zh_CN 2461 179 241 2 +++++++++++++++++++++++++UU~~~ > zh_TW 1934 706 867 358 ++++++++++++++++UUUUUU~~~~~~~~ooo Only de, sv, zh_CN have been updated in 2013 and can be considered active. I worked with asfinfra to get access to Apache's pootle instance[2]. The translation project is configured and I have made a successful run of changes back and forth. As such I am confident that po files can be maintained in such a web based system. I would also like to note that offline editing of po files in your favourite tool will work with this process as well. What I have yet to configure with asfinfra is regular scans of the trunk code, and commits of added/updated/reviewed translations into svn. I would like to hear from active translation maintainers if they are happy to move their respective translations into Pootle and work on that system. If so I am willing to coordinate the import, even if just for trying it out. With sufficient support from active translation maintainers we can bring all languages in. I propose that suggesting new/changed translations remain open to unauthenticated users and that the translation maintainers review these suggestions. The hope is to attract translators from the casual level up, and to recruit maintainers from the pool of contributors for abandoned languages. Please let me know your thoughts. [1] https://subversion.apache.org/docs/community-guide/l10n.html [2] https://translate.apache.org/projects/Subversion With kind regards, Andreas Stieger
