Details for setting options

Last modified: February 9, 2008 - 08:39

The following explains what effect enabling/disabling various Localizer options will have.

Language switching block
Hide the current language-When checked, the current language being displayed will not be shown in the list of languages shown in the Select language block. If you want to show someone all the languages available, leave this unchecked. However, if it is unchecked, and a person is viewing in English, they can also select "English", but of course nothing will change, which may be confusing for some.

Show the language name-If you want the language name (as specified under Localization) to be displayed in the Select language block, check this box. If you want to save space, you may want to uncheck this and just show flags.

Show flags-When checked, the flag assigned to that language will be displayed in the Select language block. If both the flag and language name are enabled, both will be displayed. (Note that due to drupal.org distribution rules, the flags files are not included in the Localizer module download package. See the detailed HowTo.)

Flag and language separator-If you would like a character to be placed between the flag and language name in the Select language block, type that character here.

Flag icons path-Enter the relative path from the Drupal root to the flags. This is typically automatically detected and for a normal installation for Drupal 5.x is sites/all/modules/localizer/flags/*.png.

Flag icons size-This controls the display size of the flags. The original size of the flags that are recommend by the Localizer author is 16 x 11, so this will produce the best quality display if you are using those flags. However, the display size can be adjusted here as needed.

Note that other flags (with the same or different sizes) can be substituted for the language of your choice--just swap out the flag files under sites/all/modules/localizer/flags, leaving the filenames the same. Just remember that if you do this, you will want to save your modified flag files somewhere so that when you upgrade Localizer you can once again overwrite the default flag files.

Language initial detection options
Detect through browser's locale-When checked, if the preferred language set in a visitor’s browser is the same as a language available on the site, the site will automatically change to that language. This is mostly for anonymous users, as user-specific preferences can be set by registered users in their own account settings that will over-ride this. Note that anonymous users can still click on a language in the Select Language to view the site in a different language. If you always want anonymous visitors to view the site in a specific language, leave this unchecked.

Language switching options
Redirect front page to the localized version-The optional Drupal "front page" can also be translated into available languages. When this setting is checked, the appropriate language front page will be displayed.

Switch by hostname-When enabled, this feature allows changing locale via a language-specific site URL. For example, for English, en.mysite.com, and for Italian, it.mysite.com. Using this feature requires setting up Drupal for multi-sites, and setting DNS entries accordingly, so only use this if you are willing to configure Drupal and hosting accordingly first.

Content settings
Content type-When enabled, that content type will be integrated by Localizer. So, when a "new" node is created, there is a choice of language available, and once submitted, translations can be done. For any content types created after Localizer is installed, return to this area and enable/disable Localizer integration as required.

Activate content language fallback support-Enabling this function allows a translation in a language other than the one being viewed to be displayed when a translation in the current language is not available. For bilingual sites, the "other" language translation will simply be displayed. For sites with more than two languages, the order (priority) in which alternate translations will display is based on the Weight given to each language.

As with other Drupal "weight" settings, the "lighter" items (smaller numbers) float to the top, or in other words, take priority. So, if you have a tri-lingual site in English, Italian, and Japanese, and set the weights to English=1, Italian=2, Japanese=3, this is the order of fallback priority.

  • EXAMPLE: Assume you have some content that has English and Italian translations, but not Japanese, and you are viewing the site in Japanese. In this case, the English translation of content (only) will display in place of the "missing" Japanese content. Of course if the English translation were also missing, then the Italian translation would display (if available). Note that if all available languages are left at the default "0" (or even to the same weight other than 0), then all translations will be displayed when the translation of the viewing language is missing. So, if you want to keep "duplicate" content from displaying, make sure the fallback weights are set appropriately.

Support for external modules
A list of external modules that are specifically supported by Localizer are presented. (As of this writing, only the Search and Views modules are supported.)

Searches return results in all languages-This option allows you to determine if searches are filtered by the current viewing language or not. Leave it unchecked if you want searches to stay within the current viewing language, or check it for global searching.

Views global support-When this is enabled, it provides Localizer integration with the Views module so that language filtering is available for Views. This can be enabled without issue regardless of whether you have installed Views or not.

 
 

Drupal is a registered trademark of Dries Buytaert.