This project is read-only.


The language selector supports 3 modes: menu, flags and hyperlinks. Although you can use the 3 modes concurrently, typically you will select either one of the modes. The advantage of using the flags mode or the hyperlinksmode is that these modes cause the selector to render basic hyperlinks which can be easily followed by any search indexing spider. using this will make sure that search engines find all languages of your site, not only the default language!

Another feature of the MLLanguageSelector is the ability to map languages to another language. This is useful in the following situation: suppose you have a portal that supports 3 languages, and you finished adding content for 2 languages, and are still working on content for the 3rd language. If your portal is publicly available, your visitors will be able to also see the 3th language. If you disable the 3rd language in admin>languages, then the language can still be "automatically" selected if it's the first preferred language in the browsersettings of the anonymous user. Furthermore, you won't be able to select the language yourself, so how would you be able to continue adding your content?. Comes in MLLanguageSelector. With the MapLanguages feature, you can redirect all requests for the 3rd language to one of the 2 other languages, but you yourself will always be able to see and select the third language. So you can edit content for your third language in peace, and just make it available whenever you like (by removing the mapped language setting). Of course mapped languages will be invisible in the language selector

If only one language would be rendered in the selector, and attribute HideCurrent has been set to True, then the languageselector will render nothing at all

The module with a basic module.css stylesheet (in the folder /DesktopModules/MLLanguageSelector/), which is used for both the module and the skinobject. This stylesheet is used to format the tables that are used to render the language selector. You can edit these settings, or override them in your skin.css to make the display different. You can turn off the usage of the stylesheet for skinobjects by adding the attribute UseStyleSheetForSkinobject = "False" to the skinobject definition. This option is not available in the module settings, simply because it has no meaning for a module. This means that this attribute will not be generated by the Generate SkinObject attributes option in the module settings either.

Last edited Jul 11, 2011 at 7:11 AM by erikvb, version 1


No comments yet.