Hey all, First off, the site is looking great! You all do awesome work.
I'm working a lot with localization in Drupal right now. I'm working for Mozilla for the summer and I am working to put a layer of Drupal 5.1 under mozilla.com. The main reason for this is localization workflow. So my current work sounds very familiar to what your team is headed for. I'd be glad to offer any help, experience, and advice I can. For starters, an overview of the tools being used: Drupal 5.1 Modules: * Localizer - enables multilingual content support * Locale - included in core, Enables the translation of the user interface * Workflow - used to create workflow states for nodes being translated ( e.g work in progress, needs review, reviewed -- needs work, published) * Workflow_access - provides CRUD and state change permissions to each state for each role * Localized_path - this is a custom module I made by modifying the Path module included with core. What it does is automatically prefix the URL alias set in the node edit form with the locale code. so if a user wants an english locale node to be aliased with "foo", they put "foo" in the alias box on the form, and it is aliased to "en/foo" behind the scenes. This is not necessarily specific to OOo Ext's setup, just something to think about. * Views - using this to create views for various reasons, e.g. list nodes in each workflow state To be done: * Create a module to restrict users to specific locales on update/delete access. e.g. we translation editors and publishers to only have access to their particular languages. This has been tricky so far, as Drupal's node access system can be confusing/difficult to work with * A lot of testing and verification Things to watch out for: * http://drupal.org/node/156525 * http://drupal.org/node/116733 * localizer and views aren't working together right now (for me at least) Hopefully that was a relevant overview, although it was brief. Feel free to shoot me questions or comments at [EMAIL PROTECTED] Cheers, Alex Buchanan On 7/16/07, Laurent Godard < [EMAIL PROTECTED]> wrote:
Hi all The extensions website is being designed and things are going the good way ... Nevertheless, due to lack of volunteers, the translation part is not taken into account and the site is actually designed in english. So we need some volunteers to help the dev. team to setup this framework. The site is created with drupal 5.1 and i think one could use an existing framework Could you please relay this call for volunteers to your native-lang communities. Job to be done - evaluate the needs : site translation, extensions presentation translation - setup the framework under drupal so that the site can be translated Feel free to ask if any question the volunteers can joçin et say an "Hello guys" on the dedicated mailing list [EMAIL PROTECTED] Thanks in advance Laurent -- Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org - http://www.indesko.com Nuxeo Enterprise Content Management >> http://www.nuxeo.com - http://www.nuxeo.org Livre "Programmation OpenOffice.org", Eyrolles 2004-2006 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
