To build a site in English and German I installed the localizer module.
I don't need pages to be translated, I only need the admin pages and the user messages in German.
On domain.com the language should be always in English and on de.domain.com always in German.
So I installed 2 different Drupal installations, one on domain.com and the other one on de.domain.com.
The locale switching options work fine without leaving the domain (and on the same Drupal installation).
But when I use the option switching by hostname it does not work.
Comments
Comment #1
Mojah commentedI don't think localizer works accross seperate installations. If you are not translating nodes or pages, the locale module will serve the purpose. Localizer will not be required in this case.
Comment #2
Roberto Gerola commented>But when I use the option switching by hostname it does not work.
Can you explain a little better ? So I can check if there is some problem in the code.
Thanks
Comment #3
unitec commentedYes I know I don't need the localizer module.
I only have to place a flag with a link from one to the other sites to change the language.
But using this method it's not possible to select the language by browser.
The localizer module does this perfect but only on the same site.
I think I've to live without an automatic language selection.
Comment #4
Roberto Gerola commented> But using this method it's not possible to select the language by browser.
You cannot have switch by hostname and also the other switching options.
It could create infinite loops in the switching mechanism.
Comment #5
sunIf you need completely different sites per language you should consider using Internationalization module instead. You will not only benefit from the current process of implementing i18n into core, it's actually exactly what you're trying to achieve - without separate installations.
Comment #6
unitec commentedI already tested the Internationalization module in the past but it did not work.
It seems that this module had problems to run with the category module.
I delete the category module and now the Internationalization module works fine.
It don't seems to be possible to have separate primary and secondary menus for each language on the top.
OK I can do it per node or move the navigation to the left bar.
But is there also another solution available?
Comment #7
sunNo, I'm sorry, there's no category.module support - neither in i18n, nor in localizer yet.
Comment #8
(not verified) commented