Designed for multi-language sites, Language Sections provides a way of storing content sections for different languages in a single text area.
- A simple multi-language site front-page.
- Views module header, footer and "empty" text sections, to make them "language aware".
- Language-specific custom 404 pages etc.
- Node bodies, to display something like "This content is only available in English" when someone tries to view in a language for which no translated version of the content exists.
- Text sections provided by other modules which do not offer multi-language capability.
- An easy to manage alternative to the Content translation module in some situations, typically on small sites.
This module provides an "input filter", so will only be useful for text sections which make use of "input formats". See also Language Sections Extras.
How to build a multi-language site
Please note this module is not designed to be a complete solution for building a multi-language site - the standard way to do that is to use the Drupal core Content translation module and optionally add the Internationalization module. However, Language Sections, possibly in combination with LS Extras, offers a simple alternative to that approach which may be adequate for small sites, especially where the number of languages is small and content in two or more languages is often created by a single author.
Combined use of Language Sections with the standard (Content translation module etc.) approach works well and offers increased flexibility. For example, node-based translations might be used for major languages, with other languages handled via a single node.
See also the tutorial on building a multi-language site.
Text and sections are marked in a simple way, here's an example:
=== es ===
This text will only be displayed when Spanish language is selected by the user.
=== fr ===
This text will only be displayed when French language is selected by the user.
=== others ===
This part will be displayed when the user's selected language is neither Spanish nor French, i.e. all other languages, and so might provide text in a common language such as English.
=== all ===
This part will be displayed for all languages.
Please read the documentation for further information.
- LS should probably be the first or among the first filters in your input format configuration.
- You can build some very flexible methods to display multi-language content using a combination of Language Sections, MultiLink and InsertNode. Maybe add LS Node Titles too so that MultiLink and InsertNode can see translated node titles for LS-based content.
Commercial support and customization
For general comments, complaints, praise etc, please add a review.