I would like to add here an issue which I also posted in the Internationalization group forum, as I think it will be important for some sites. I can not imagine the cost to be incorporated in the Localizer module, please consider removing this issue.

Some users can understand more than their native language, therefore they could benefit of being shown more content than they are now. Imagine in my user profile I specify locale=English, but I extend the user profile so that I can also specify understandLocales=English,Spanish.

As a result, Drupal could show a mix of English an Spanish posts. The "Search" button would also take that into account when providing results.

Best regards.

Comments

Roberto Gerola’s picture

Roberto Gerola commented

It can be implemented.
I'm not sure how much control can I have on search results, but I see what it is possible.

Roberto Gerola’s picture

Roberto Gerola commented
Assigned: Unassigned » Roberto Gerola

This feature has been implemented.
Tomorrow I'll the CVS and make an official release.

It will work in this manner :

A new block is added : Multilingual content, where
a visitor can select which languages he / she wants
see the contents lists in.

This preference can also be set as user preference under my account section
and also globally under localizer settings,
both for anonymous and authenticated users.

Localizer use this order to determine which languages to use :
- from the block (if present)
- from the user preferences (if present)
- from the globally preferences (if present)
- from the current locale in which the interface appears

funana’s picture

funana commented

Great! Exactly what I was looking for! Very very good work, Roberto. I love this module since I have kicked i18n... It really was a nightmare...

Roberto Gerola’s picture

Roberto Gerola commented
Status: Active » Fixed

Available in 2.4 release

Roberto Gerola’s picture

Roberto Gerola commented

I've decided to separate the user interface locale from the content languages.
The user interface locale will be used as fallback option if no content language is specified.

This is already partially implemented, but I'll create some APIs
like (localizer_get_ui_locale(), localizer_get_content_locales())
to make it more clear.

Roberto

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

Roberto Gerola’s picture

Roberto Gerola commented
Status: Fixed » Closed (fixed)

Closed in release x.6