Articles about localisation
I didn't see this one coming but on a Multilingual Russian site we recently built, the client asked us to translate the Russian Rubble symbol "руб" to "RUB" when viewing products in English.
As there are no localized options for currency settings I had a look around the commerce code and came across commerce_currency_format() in commerce.module.
This is going to be a step by step guide for localizing & translating a Drupal 7 commerce site. there are many ways and tools Drupal and its contributed modules support and this is just one of them.
I will not go into too much explanations but will try and make sure I cover all the steps needed to translate a Drupal commerce site.
Note: commerce kickstart 2 comes with some of this but last time I checked it did not provide full localization and translations features.
Drupal 7 has great support for multilingual site and has various approaches to content translation and localization.
In this quick recipe post I will cover the setting up of a "Translator" role for the following translation approaches
- Interface translation: The translation of strings used throughout the site
- Entity translation: The translation of Nodes and other entities using entity/field translation
I will try and cover other translation & localization approaches at a later stage
i18n / Internationalization module
We use the i18n menu module that comes with the Internationalization module.
While the module provides configuration options for language specific menu items, simply enabling the module creates a new translation text group called "Menu" that exposes all menu items to the translation interface.
You can use the translate interface to translate all the menu items except for once created by nodes for those you should translate the node and specify the translated menu title.