I’ve talked to the author of the localization module ( http://drupal.org/project/localizer ), and I’m planning on building off of that. (As opposed to the i18n module). Talking to the developers about drupal 6 is a good idea though, or at the least looking at the code and how they’re doing it.

I hit up a drupal meeting last night ( http://micropipes.com/blog/2007/06/14/june-pdx-drupal-meetup/ ), but didn’t find anyone else doing a multilingual site. Good times though.

The code-freeze is a tough issue. It’s nice to stick to advertised deadlines, but really Drupal typically has at least as long of a bugfix period post-code-freeze as it does feature addition pre-code-freeze period so Drupal6 will likely take until q3 or q4 of 2007 to be released. Delaying that by a month isn’t terribly significant and there’s so much work that is close to being ready for inclusion but isn’t _quite_ there. Hopefully that makes some sense.

I’ve been looking at Drupal 6, and I applaud that they’re taking localization seriously in it. I was disappointed to read it the next revision of it was delayed another month, although I can understand and certainly relate to that.

We’ll be starting work with Drupal 5.1 and modules. I’ve looked at the i18n and Localization modules, and neither will work out of the box. My current (rough) plan is to build off the Localization module. (The first hiccup is permissions – it has no concept of user/group permissions).