Mosaik internationalization

If you are working on a multilanguage website, and you want to use Mosaik, you'll surely need to enable i18n_mosaik.
Traslating a Mosaik is ... (please don't say "really similar" again!!)... easy!! :D

Just look at these screenshot:



So..that's all you need to know about Mosaik.

Setting OG and i18n contexts

Out-of-the-box contexts

A major component of localizing content is to be able to set language and other contexts so that your Views, blocks, and other data may be country and language aware.

Out of the box, for a multilingual site you can visit:


And for OG you can visit:

/admin/config/group/context (requires OG Context module)

To set the types of context providers you wish to use, along with priorities. IP-detection modules also extend the list of options for multilingual options.

Date Formats and Exposed Filters

Date formatting – the order of day, month, and year – is important to many websites. However, getting date formats working correctly with Views’ exposed filters can take a bit of administrative work.

The following modules should be installed and enabled:

Drupal 7 - How to use Drupal's i18n and Organic Groups modules to create an international website

This documentation section covers how to build an international Drupal site that will cover the required functionality for modifying the site structure, content, and integration with other services in order to have an effective and manageable site. We will also offer some tips on using custom modules to extend i18n and the locale module.

Determining your use case

Before you start building your site, you will first need to determine the overall use case for your site's current needs, and likely needs in the future. For example:

Import content and its translations from CSV (managing entityreference field)

In this page, we will see how to handle an entityreference field in content type 2 referencing a content of content type 1 without having the id of the target, only its title.

And of course in all the languages we want.


For the main language import, we will be using an entityfieldquery to get the id of the content of content type 1 in the main language.
For the other languages import, we will use the main language import to be sure of the id of the target.


Subscribe with RSS Subscribe to RSS - i18n