i18n

I think we should learn something from WPML Multilingual CMS plugin for wordpress. Yesterday I made site that was too simple for Drupal in Wordpress and at the last moment client asked for multi language support. My hands went cold. Used WPML and was surprised how easy, fast and simple process was comparing to Drupal - most importantly because of KISS aproach to many parts of plugin and how it works.

Buenas...

I'm encountering an issue with URL's to nodes in a different language than the user's current language. Currently, the site is set up with English as the default language, and French in a path prefix of /fr. On the home page, there is a view of all book nodes, some in French and some in English. However, if your current language is English, the French bookURL's are set to fr/node/. If you switch to French, all English books are shown as node/.

I've found out that if I insert the appropriate paths into the url_alias table I can make things work as expected. For example:

Jakie znacie metody przełączenie jezyka interfejsu na angielski, lecz pozostawienie polskiego kontentu ? Chodzi mi strikte o strony administracyjne. Pamiętam, że do drupala 4.7 była poprostu paczka z admin interfejsem angielskim lecz co z 6 ?

Walczyłem z tym http://drupal.org/project/preserve_language lecz to nie to.

Dzięki za pomoc

Estamos escribiendo una guía sobre la multilingualidad en los sitios Drupal. Está escrita en Inglés y traducida a Español y Alemán. La misma enseña cómo utilizar el módulo i18n y cómo administrar casos especiales en los cuales no es tan obvio cómo localizar.

While currently the majority of Drupal people speak English as a native or second language, I think it would artificially limit the scope of the LUGO group to require it. I deliberately did not choose a language when I created this group because there was not an 'all' option. The audience and membership of this group is intended to be anyone, anywhere, who organizes a local Drupal User Group currently, or wants to start one. If we are going to encourage that second group to become part of the first, we will need to accommodate people that do not speak English at all.

A report back from the virtual code sprint on internationalization in Drupal core

What if the new Fields API in Drupal core could be used in multiple languages, so that any object type could be internationalized just by adding fields?

That's exactly what the "multilingual fields" patch currently being developed would make possible.

Multilingual fields is one of two major improvements to Drupal core's multilingual support to come out of the recent code sprint on internationalization.

I posted an update on our first day of the sprint here (so it would get to Drupal planet):

http://civicactions.com/blog/2009/feb/03/internationalization_core_code_...

Want to join in the sprint? Please do! Join us in #drupal-i18n any time on Wednesday Feb. 4. If you're looking for a way to contribute, look through http://drupal.org/project/issues/3060/term/301 and choose an issue you want to take on. Then come into #drupal-i18n and talk talk through the issue.

Never contributed to Drupal core before? Don't worry--we'll help you get started.

See you there!

I've just released the first alpha of a new module called i18n_access. This module aims to fill a gap in access control for sites using i18n.

The module adds a list of checkboxes for each available language to the user add/edit form (only visible to users with 'administer users' permission). These language permissions are combined with the normal user permissions to give more fine-grained access control.

There are several major modules and few dosens of additional tools on internationalisation. I find it quite confusing to figure out, what particular combination of modules and settings will lead to the expected behaviour. So I'm addressing other group members with this request to help me.