Langcodes and plural forms

clemens — Sat, 26 May 2012 14:25:36 +0000

We all know Drupal and Symfony do have multilingual support (i18n, l10n, pluralization). But do they match? Or do they equally well? How does one test this? This is what I did. I wanted to add tests for Symfonfy's PluralizationRules as there were none and I wanted to have support for PluralForms loading Drupals *.po files clean and simple. How hard can it be?!? These tests should cover:

Langcodes. Are all known language codes available (or easy to add)?
Parsing Gettext PluralForm rules like

nationalise your site with enlisted variables

clemens — Fri, 13 Nov 2009 09:27:48 +0000

With drupal we can enable the locale module and install the i18n module to internationalise and translate our site we can make our hands dirty by visiting the http://build2be.com/admin/build/translate/search.

Still our work is not finished yet. We have to dive into settings.php to translate more strings of our site.

Taken from http://drupal.org/node/275705#comment-1058360 and using http://drupal.org/projects/drush_sm we learn we may choose from a lot of variables.

By running the following command we can start cherry picking our variables enlisted to translate. We could off course run an SQL statement but that would spoil the fun.

drush sm list variables | less

After deciding what variables we need we can export these variable values to send over to a translator by running

drush sm export variables - site_name site_slogan site_mission site_footer anonymous | less

Next step is changing settings.php like this

$conf = array(
  'i18n' => array(
    'site_name',
    'site_slogan',
    'site_mission',
    'site_footer',
    'anonymous',
    'user_mail_password_reset_subject',
  ),

followed by uncommenting the line just after 'reverse_proxy_addresses'

#   'reverse_proxy_addresses' => array('a.b.c.d', ...),
);

Not we told the i18n module to localise some of our site variables.

It would be great to run drush sm import variables for uploading our translated variables but unfortunately it doesn't work like that. The i18n module uses it's own tables for performance reason.

So we end with navigating to the appropriate language dependent pages and see 'This is a multilingual variable' next to our form fields on pages like

Site Information
User Information
etc depending on what variables you added to i18n_variables

Happy (inter)nationalise your site.

free form:

From _en_ into a translatable _en_

clemens — Mon, 25 May 2009 09:17:11 +0000

On a multi language site it is desirable to translate the drupal English into the customers Englich likings.

Steps taken

Goto /admin/settings/language/add
1. Add a custom languages with language prefix en, name en-ours, english English @ Our place and native English @ Our Place
2. Make your new language the default.
3. Disable drupal's en
4. Change the name en-ours into en

build2be/com/e - i18n

Langcodes and plural forms

nationalise your site with enlisted variables

From _en_ into a translatable _en_