This is exactly what Pootle [1] and Translate project/Wordforge is trying to achieve.
Current stable Pootle [2] is still a standalone Python server, but I'm putting in an effort to rewrite it as a Django app [3], though my work has currently stalled due to university exams. I'm nearing usable app so if anyone wants to join, consider this as an invitation. Any help would be greatly appreciated. Regards, Gasper Zejn [1] http://translate.sourceforge.net/ [2] http://pootle.wordforge.org/ [3] http://translate.svn.sourceforge.net/viewvc/translate/src/ branches/django-migration/ On Sep 15, 2007, at 9:13 AM, rcoup wrote: > > Hi All, > > As part of the django sprint today Malcolm, I, and others had a > discussion about improving the translation processes so its easier for > everyone. The following idea is based off my experiences managing > translations for the apps I develop as well as Malcolm's comments on > Django core. > > So, what I'm thinking of: > > A django app lurking around djangoproject.com somewhere. > > Our translator (Julie) logs on and can select a language she wants to > translate (Australian). She gets easy access to see all new & fuzzy > messages for that language, which are automatically pulled from > subversion. She can search for specific messages she's after to > correct errors (by file/line or by base/translated strings). Once she > finds a message to translate, she can edit the translation, and it is > verified as being correctly formatted (for string substitutions, etc). > Encodings are always enforced as utf-8, so no worries there either. > She can download a new po/mo file for the language for immediate use > in her project. > > Later the Australian language maintainer (John) comes along. He's been > approved by Malcolm or someone else important as having the ability to > directly commit translations for the Australian language. In addition > to all the above stuff, he can see the "uncommitted" changes for the > Australian language. For each change he can accept/edit/reject it. > When he's happy, he can commit the edited changes to subversion (the > system will generate the .po and .mo files and check them in). For big > changes there's no problem to checkout and edit files offline, just > like now. > > Problems this is designed to solve: > * Making it very easy for non-technical people to do small > translation updates (no need to learn about diff, subversion, etc). > * Reducing clashes/regressions of updates (everyone is always working > with the latest) > * Problems with encodings/validation go away > * Less work for developers (reviewing and merging patches, etc) > * QA via language maintainers > * Developers can install it and use it for their own django projects, > not just core. > > Launchpad translations is one similar idea I've been referred to, but > other links are always appreciated. > > Criticism, comments, ideas? > > Rob :) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" 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/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
