Difference between revisions of "Extensions/website/Translating"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Translating each desciption and living content)
Line 26: Line 26:
The categories/tags will also be translatable.
The categories/tags will also be translatable.
[[Extensions/website/Translating/description|Implementation details]]
== The Native-Lang representative ==
== The Native-Lang representative ==

Revision as of 11:20, 30 January 2008

The website and its content needs to be translated.

There are 3 parts to be worked on

  • the website itself
  • the extension descriptions on the site
  • the extension itself

If tools can be built to address point 3, we only will work the first 2 points

Translating the website

The user will have the correct language displayed based on the navigator/browser settings. Maybe some preferences may be stored (but not on the first version). The available languages are easilly accessible by country flags or better a dropdown language list.

The translation mechanism should join the l10n project if possible

If a part is not translated, english is displayed.

Translating each desciption and living content

The drupal framework will have to be used. The process has to be light so it can be done by non-technical volunteers that volunteer on the site. They can then choose the extensions to translate for their language. Once the translations are submitted, an email is sent to the owner of the extension (see below).

At creation time, the extension owner should be able to provide translations in the language(s) they want. English should be highly recommended if not mandatory.

When a translation is provided, an email is sent to the extension owner to inform him.

The categories/tags will also be translatable.

Implementation details

The Native-Lang representative

Each native lang community willing to have the extension website and descriptions in their language will have to nominate a representative that will be the bridge between the translators and the extensions project. This representative will have to check that the submitted translations are correct and not offending. A first list is gathered in this dedicated page Extensions/website/Translating/NL_Representative

The website will have to provide some tools for them.

  • an email generated for each new translation needed (new or updated extension)
  • some basic lists (non-translated extensions, waiting for review)

This representative will be helped by volunteers that identify on the extension website and provide translations for targeted extension.

Useful Drupal information/documentation

Drupal seems to be very powerful and provides several modules that can help to provide a multilingual webpage. How it works in detail have to be checked.

Some useful Links are

  • Internationalization module
    "This is a collection of modules to add multi-lingual capabilities to Drupal sites. Provides content translation -nodes and taxonomy-, interface translation for anonymous users -with the locale module- and browser language detection. Includes a block for language selection and manages translation relationships for nodes and taxonomy terms."


  • The default drupal module 'locale' is enough for a first start.
  • Strings to be translated will get delivered as '.po' files - further details will follow.
  • Strings and files need to get drawn from system and edited with respect to UTF8
  • Language selection will happen through additional module 'localisation'. With a listbox on the top of the site.
  • Current languages:
Deutsch: http://extensions.services.openoffice.org/?locale=de
English: http://extensions.services.openoffice.org/?locale=en
Français: http://extensions.services.openoffice.org/?locale=fr
Español: http://extensions.services.openoffice.org/?locale=es
Magyar: http://extensions.services.openoffice.org/?locale=hu
X Test: http://extensions.services.openoffice.org/?locale=xx
  • Languages are added on request and get initial translation from: http://drupal.org/project/Translations
  • Findings: All strings would be about: 5.000; but we need mainly only about 1.000;
  • Priorities: Translation for anonymous and registered users - everything that they can't see is not needed.
  • How to get now just the needed strings? Drupal got modified to write the last access date of a translation access.
  • With that it is possible just to extract strings that got used e.g the last month.
Personal tools