IF YOU USE A NON-ENGLISH BROWSER PLEASE READ After all the comments about localisation: - Go to http://gnomedotorg.ourproject.org/ and look at the "Who's online" block in the right sidebar. You should see it automatically in your browser's language for Catalan, French, German, Italian and Spanish. This means you could see the rest of the homepage in your locale if the content would be translated. If you have a different locale please tell me and I'll upload it as well. - See the language selection block in the left sidebar. You can browse the site in different languages. Again, you'll find the contents mostly in English because no translations have been made, but the functionality is already there. I insist this is no look&feel. This language selection can be a dropdown menu, can be put elsewhere... - Now go to http://gnomedotorg.ourproject.org/index.php?q=about . Check at the bottom of the page and the left sidebar to see if you still are locale (you are). Most parts would be in English but, again, because they haven't been translated yet. - If you visit this page as a registered user you will find a "translate" tab at the top. If you click you will find the current state of the translation of this page i.e.: Translation Status Language Title Actions English About GNOME edit Catalan Sobre GNOME edit French Not translated create translation German Not translated create translation Italian Not translated create translation Spanish Not translated create translation - If you click on "create translation" you will have the edit form wit all the fields filled with the default English information, including the original text and its code. You can translate directly the text keeping the code. Enabling rich text in you user profile you could even translate the pages with simple codification without even seeing the code, working directly on bold, italic, lists... - You can create a new page in the language you prefer. This will automatically give the other languages the chance to replicate you new page in their locales, but a language can have own pages that won't be missed by other languages, it is just their decision. I think this covers all what has been requested about the localisation of the core wgo. All this has been powered by the Drupal i18n module, developed by Jose Reyero, which just happens to be a GNOME user. Installing the module took me about 20 minutes, configuring other 20. Now adding a new language is a matter of few minutes. Independently from the tool we choose, we will need to define the list of pages considered essential (main) and required as literal translations for any locale aspiring to become an official language of wgo. The translators team will need to coordinate the translations of updates of pages, as they do with the GNOME and press releases, but we could allow some more flexibility, as far as we don't have main pages outdated or with poor quality translation. Then any language team could go and define their own set of local only pages i.e. regional information and activities. We would still need to test how does this work with the non-static content aiming to be localised: feeds, forums, blogs, etc. We will find better answers when we get used to the multilingual wgo idea, I guess. -- Quim Gil - http://desdeamericaconamor.org
Attachment:
signature.asc
Description: OpenPGP digital signature