locale

One of my three proposed subprojects for this year's Google Summer of Code was about improvements for Drupal 6 to include the autolocale functionality developed for Drupal 5. As always, putting autolocale module into core is not simply a code copy-paste issue, there are several outstanding issues that need to be worked out. The main problem is that when we need to parse and import a half of a megabyte in translation files, PHP can easily time out. So a batch processing framework was in need to process multiple operations in subsequent HTTP requests. Fortunately yched already did a big amount of groundwork on this, and Jakub Suchy tried to map the batch API to autolocale, so I only needed to dig deeper into these to try to make them work nicely together.

[scroll down for English version]

Adjunto un archivo "po" para la localización del Drupal 5.0
Es mejor que uno simplemente exportado del 4.7 porque hemos agregado muchos términos que faltan en 5.0.
Pero no es completo.
El grupo debería trabajar juntos para completarlo y normalizarlo para argentina.
El archivo está listo para utilizar en poedit (los seteos para los plurales está ajustado).
Discutiremos en la próxima reunión como proceder, entre tanto, utilizar y que les venga bien, y ... agreguen términos!

Steven recently got frustrated enough with the Drupal core restriction on international letters in path module that he removed it..

So, now pathauto and urlify can use any character from the node title that the user submits.

I've created an issue for pathauto to see how to best handle this. Please provide your input on the ideas there.

Op de DrupalCon in Brussel heb ik gesproken met veel Nederlandse / Nederlandstalige Drupal ontwikkelaars en gebruikers. En waar de vorige DrupalCon nog een zeer beperkt aantal consultants telde die full time hun geld (proberen te) verdienen, waren in Brussel meer dan een dozijn pro's aanwezig. En allen vonden het een goed idee om samen te komen in Nederland om te praten over mogelijkheden, uitdagingen "and everything Drupal"

We kunnen het doen in Amsterdam of bijvoorbeeld Den Haag, in een kroeg of in een bedrijfsruimte. Mocht je een voorkeur hebben voor een datum (een weekend eind oktober?) of een voorzet willen doen voor een (onofficiele) agenda, plaats dan een comment in deze thread!

I just posted an experience installing og on a multilingual site. The short version is that it ground to a halt because of the t() function. Maybe og is still a little early in it's 4.7 release, but I think it's an example of bad things happenning to good modules. Does anyone else have any experience, ideas about scaling t()? I can see there's some caching going on, and maybe I just need to adjust a cache size somewhere ...

[a while later]

aha, here it is: http://drupal.org/node/42463 - it's a problem with 'incomplete translations', and a proposed sql index fix didn't make it into 4.7 as per the discussion.

I'm half way though an enhancement to organic groups module where a group admin can pick a group locale. I need a volunteer who will figure out what languages are in good enough shape to install on this site. This person should also field requests for new languages, and update existing languages as their translations mature.

I'm pretty excited that we'll finally have a showcase site for Drupal's localization features. Also, Mozilla Group specifically asked for this feature for one of their sites and i just love paying them back.