07. Personalizing Localizer behavior

A registered visitor to a Localizer-enabled site can customize their viewing experience. Specific Localizer settings can be accessed from My account or User account, and clicking "edit".

The first setting is Interface language. The language selected here will be the default language for the site provided the user is logged in.

The second setting is Enabled languages. Each language checked will be a valid viewing language for that user, or, to put it a different way, no content for languages that remain unchecked will be displayed. Also, only enabled languages will be displayed in the Language switching block and in other lists, such as the Localizer strings translation and Localizer content translation management screens, as well as the content fallback languages settings.

The Content fallback languages settings allow the user to set up the "priority" of the content to be displayed. What this does is allow a "backup" translation to be displayed if there is no translation for the current language being viewed. For example, you may have a site with Italian, Japanese and English. If you are viewing the site in Italian, but a particular piece of content is only available in English, by enabling this and setting weights appropriately, the English content will appear. Selecting the "priority" of fallback languages to be displayed is done with a typical (if not hard-for-many-to-understand) Drupal weighting scheme. The languages assigned "lighter" (smaller numbers) will have priority over "heavier" (larger numbers) on. So, for our example of the Italian, Japanese and English site, let's assume that Italian was set to 1, Japanese to 2, and English to 3. If I am viewing in Italian, but the content was only available in Japanese and English, the Japanese content would display as the fallback because it's priority is higher ("lighter").