Localizer for Drupal6 ?

> Hi Roberto,
Hi

> Will you port Localizer to Drupal6 ?
Well, there have been enough requests, I think, to convince me :)

>The internationalization support of the default installation of Drupal6 is not as comprehensive as I expected
I am just beginning in these days to dive in the new Drupal 6 features to understand
what and how is necessary to do.

I really need to avoid patching core modules files this time.
It seems that the new menu system is more easy to manage for translations,
taxonomy not. It seems that the approach should be to duplicate taxonomy trees.

I'm not sure how I could implement the new language fallback support I introduced
in Localizer 3.

Roberto

Yes - I must say I was kind of disappointed by my first glance at the localization functionality included in the D6 core. I switch the language, but the front page still displays nodes in both languages instead of only the relevant one, and I cannot quickly find a way to fix it.

Regarding the new Localizer 3: it looks nice, but does it support identical page names - say, en/contacts and it/contacts? In Localizer 1, you can specify these paths manually; with language prefix automatically added by v.3, they become en/en/contacts and it/it/contacts; and if you try to change the URLs back to en/contacts and it/contacts by removing "en" and "it" from path aliases, you run into the problem of identical aliases not being allowed for different nodes.
Is disabling the language prefix the only solution?

Thank you so much for the great job you are doing with the Localizer module!

I am interested in this as well, so, subscribing.

Definitely interested!!!!!!!! 100%

Hi.

I won't create any version of Localizer for D6.
All "critical" multilingual features that pushed me to create Localizer
are already in the core now.

The most critical features were language and language dependent path handling.
That are now in the core.

Besides this :
- having two mutlingual modules has caused a lot of confusion in the community
- hopefully, in D7, no contrib multilingual module will be necessary
- there is too much (unpaid) work for me. I cannot continue on this project.

I'll help Jose` with i18n instead. I think it is better now to join our forces
to create only one solution.

Don't worry about your multilingual data. Porting them from D5 to D6
will be possible.

hi roberto!

We all must agree with you on the idea of collaporation with Jose on i18n. I think having one powerful ellogant sollution for our multilingual needs serves the community better. hopefully this will push for a more powerful intigration in drupal 7 so that we won't need any contrib module.

"Don't worry about your multilingual data. Porting them from D5 to D6
will be possible."

could you please elaborate on this? how is this going to be possible?

thanks.

> "Don't worry about your multilingual data. Porting them from D5 to D6
> will be possible."
> could you please elaborate on this? how is this going to be possible?

D6 stores node translations as separate nodes as do Localizer and i18n.
It possible to migrate these relations very easy.

Strings translations : menu, variables, are not a problem.
The translation system works, less or more, as a dictionary.

I agree that it makes more sense to join efforts with Jose, and would like to thank you Roberto once again for all the work you have done for Localizer for D5.
A little less than a year ago, I wanted to test Localizer, and it inspired me to create a Drupal version of a bilingual site powered by a commercial CMS, and it turned out to be much better than the original one and replaced it :).

This is now a core/i8n issue.