Twilight's localization feature makes it simple to extract strings in other languages, allowing Salla theme developers to effortlessly support multiple languages.
Information
In order to help merchants reach more people, Salla has chosen to support multilingual stores. This is a very effective way for them to reach a larger audience.
In this article, we will explore the localization:
The localization files, which are JSON based files, are located in the locales directory src/locales/ and are used to define translation strings. This directory will contain a JSON file for each language supported by the theme. For applications with a large number of translatable strings, this strategy is recommended.
Information
Supporting multiple languages is known as internationalization, or i18n (18 letters separate the i and n). Twilight i18n provides the developer with access to many translations that are ready made for your Twilight Theme.
Note
You can find a complete list of all the language translation files supported by Twilight here
Following is the location of the localization files:
The localization file is a list of key-value pairs, e.g. "Key":"Value", that can be found in a JSON string file. A colon sign : separates the key and value strings, which are then enclosed by a main key value that groups the key-value pairs according to their intended purpose. Below is a very basic JSON structure with a main key value and a list of key-value pairs for translation.
For example, the localization file for the Arabic language locales/ar.json can be as follows:
Best practices for Localizations
1.
All texts should be in 3 levels, eg. level1.level2.level3.
2.
All keys used on Salla platforms can be found here. In this essential directory, use the search box to find the specific key you need, then click to copy it. Additionally, ensure you incorporate the Localization file into the designated filepath.
For retrieving the translation strings, the developer can simply use the default helper trans() function. This helper translates the passed key to the current store language. Retrieving the translation can be done in different ways:
Simple key:
Key with variable:
Key with enforced locale/language:
A thing to know!
Arabic and English Languages should be supported when adding new keys.
By default English Language is set as a fallback language.
The developer can override, an existing translation, for example override الإضافة إلى السلة to تبرع الآن. Learn more about overriding process here.
