Documentation Updates

Please don't post comments here other than "documentation", usage hints, or links to such things. If you have questions or bug reports, open an issue. Thanks.

All languages section

A section marked with all will be output for any language, regardless of whether or not a language-specific section or default section has already been used. For example, these sections might be used to include images, PHP code or other content which is not language specific. Or you could use the any language section to show the main content in English, with short summaries in other languages, each within their own language-specific section.

Other languages section

A section marked with other ("other languages") is similar to an any language section, but will only be used when no specific section was previously found for the current language. Therefore, the position of any other section(s) is important - they should be placed after language-specific sections. For example, you might have language-specific sections in French, Spanish and German followed by an other section in English.

You can have multiple other sections, i.e:

--- language-specific sections
--- other section
--- more language-specific sections
--- second other section

I'm new to Drupal - is this module what I need?

Multi-language content in Drupal is usually handled via a combination of the built-in Locale and optional i18n modules. Other possibly applicable modules can be found here.

The Language Sections module provides some features not available when using Locale and i18n alone, but you probably need to first understand what those modules can and can't provide before implementing Language Sections.

Search engines see only the filtered output, just like any other web-site visitor. So if Google is looking at www.example.com/en/mypage it will see only the English version, and it won't see the section markers.

As of version 1.7, you can use all and other for all languages and other language. The old markers (qq and qz) are still supported for backward-compatibility with existing content. Version 2.x goes further - makes these triggers fully configurable, and allows multiple triggers. Multiple triggers might include a meaningful words in several languages, such as all, todos, toutes so that content creators could use whichever made most sense to them.

With Version 2.x now released, this documentation is a little out of date, but the majority of it is still valid.

With the new options in version 2, a typical Language Sections based page might hold:

=== french ===
Text in French, displayed to users who have chosen French.
=== spanish ===
Text in Spanish, displayed to users who have chosen Spanish.
=== english ===
Text in English, displayed to users who have chosen a language other than French or Spanish - we are are using English as a "generic" language.

That would be a configuration where triggers were set to use language name and english was set as a trigger for other language sections.

Updated for more recent versions.

others->other

I'm not sure if I understand the question. You could do it with LS, but you might also want to take a look at MultiLink.

D7 version

The current 7.x-2.x release has identical functionality to 6.x-2.5 except for the following changes:

• Settings for the module are global for all input formats (equivalent to setting the shared configuration option in D6 versions.)
• The old qq and qz markers have been removed. If you have a site upgraded from D6 and existing content which uses qq/qz, simply define them in the settings page.