localizer and drupal 6

Hello.

I don't have yet an action plan for the jump to Drupal 6.
Here : http://www.developmentseed.org/blog/internationalization/comparison_chart
you can see what features will be provided directly by the core in the upcoming new release
of Drupal.

The first step will be a migration strategy to move the data out of localizer's
db tables and insert them in the Drupal db tables.

The mainly features will be already integrated in the core. The additional features
will need a complete rewriting probably.

I'll begin to look at Drupal 6 in the next days / weeks.
I'm looking also for some sponsorship for the porting of Localizer to Drupal 6.

@Roberto: have you found some time? I'm missing a translatable Taxonomy and some other important parts in D6...

The coming 3 release for Drupal 5 will help to port Localizer to Drupal 6.
It was a necessary step for the migration.

I hadn't the time to try Drupal 6, so for me it isn't yet clear how I should manage
menu / taxonomy / variable translations and if is already integrated in the locale module.

When the 3 release will be out I'll be able to begin to think at one Drupal 6 version.

?

There will be no version of localizer for Drupal 6.

Why this?

We need Menu, Taxonomy and some other parts translated... is there any upgrade path?

Hi, I share hass' concern; it seems that there is no need for a localizer module for drupal6, ... then, I would like to know what would you recommend if I have drupal5+localizer and want to upgrade to drupal6.

Thank you.

Hello.
See my comment here : http://drupal.org/node/222865#comment-836154
and here : http://drupal.org/node/222865#comment-837943

At now I don't have any project that requires a port of the data from D5 to D6,
so I cannot say when this upgrading feature will be available.

Porting nodes isn't a problem because D6 has already a support for them.
Menu and taxonomy translations support is yet an open issue.

Menu translation support has been extremely complex.
Perhaps a simple solution would be to implement this through
a theme function :
http://api.drupal.org/api/function/theme_menu_item/6

But there is yet an issue open. Where to store the translated strings ?
We should store them yet in a separate table (and not using the translation interface system),
but this has caused some confusion to the users.

Taxonomy in D6 doesn't offer many ways to implement multilingual as far as I see, but I could be wrong,
and patching the module isn't an option for me anymore. It takes too much time to keep it in sync.

Hello Roberto Gerola,

I'm having a little problem on my site, maybe you have an idea.

I have 2 languages on my site, most of the translate issues I can sort out with i18n and D6 core. But I can't find a solution for translating the site name into the secondary language. I need to display the site name in the secondary language when users change into that. I even created a small module that does a form_alter on the system_site_information_settings form so the $form['site_name'] will be translateable, I can search for that string and enter my translation but Drupal doesn't change the site name.

Any ideas would be really appreciated!

Thanks

How to upgrade from Dru5 with Localizer to Dru6? Without loosing any data, translations?