By astra on

Both of module I18n and Localizer provide multi-language support. What are differences between them? Which one should be selected if want to create a multi-language site?

⋅ Categories: Drupal 4.7.x

Comments

zerok’s picture

zerok commented

From what I've seen in the announcement of this module, it looks like Localizer is more or less a fork from i18n (or at least very much inspired by it). It also seems like i18n has support for the Views module, while Localizer doesn't (yet!).

Can't really help you with which one to pick, though. I still have this evaluation task for one of my sites ahead of me.

Roberto Gerola’s picture

Roberto Gerola commented

Hi
>while Localizer doesn't (yet!).
It is available a generic support, but I'm working to implement
also the option to show locale field in a view and
activate also a filter on one or more languages.

Roberto
--
http://www.speedtech.it/drupal/localizermodule

natuk’s picture

natuk
Primary language English
Location Cymru
commented

Shouldn't the two projects join forces? Why waste energy to develop two separate (major) modules that essentially do the same thing?

Marc Bijl’s picture

Marc Bijl commented

- Why reinvent the wheel?
- Why confuse us drupallers?
- Why make it hard to choose?

___________________
discover new oceans
lose sight of the shore

Pamplinas’s picture

Pamplinas commented

A few weeks ago I'd say that you should use i18n, but newest versions of localizer are improving a lot, and now, for me, this module is the clear winner in the internazionalizing of Drupal, at least if i18n don't change the way the it translates the taxonomy...

I mean, among other issues, i18n duplicates the taxonomy !!! That is a really bad thing that Localizer has resolved, although localizer has to improve a little... I think that in a few weeks we'll have a real choice to insert into Drupal Core !!!

Marc Bijl’s picture

Marc Bijl commented

Hi Jose,

Can you please explain why Localizer is far superiour (while at the same time it has to improve a little)? Is duplication of taxonomy that bad? Nodes are duplicated too. And what about the menu (haven't tried localizer yet), but isn't that duplicated too?

I have used i18n for quite some time and I'm very happy with it. Now there's another player in the field: localizer module. Because I want to make a good decision between the two, can you please tell me why I should choose for localizer - instead of i18n?

___________________
discover new oceans
lose sight of the shore

zmove’s picture

zmove commented

yeah, I'm really interested too by a better explanation of "what module between i18n and localizer is the better ?"

Gaco-1’s picture

Gaco-1 commented

I was very excited to give Localizer a try, but it seems it may be a bit hard if you have your site(s) on a webhost. Localizer requires you to apply patches to some modules, I assume to replace the generic t() for the new locale_t() on these modules.
Since I cannot apply these patches on my webhost, it means that in able for me to try Localizer, I would need to download the modules to my local machine... install a tool to apply patches (I run on windows, I know, that's no good)... then upload the patched modules... Just to give it a try!!!
Now, I'm wondering... about this patch issue... does it mean I need to manually patch other modules? What about upgrades (drupal, modules, etc).

Is all the trouble truly worth it?

thanks.
-OG

shipal’s picture

shipal commented

I'd also like to know if I go for Localizer would I have to patch the modules that I've installed on my site? And if so, wouldn't it be a nightmare to update the modules later?

Thanks !

--
I'm from Hong Kong. My profile shows Thailand because Hong Kong was not available from the country list.