For the moment, only the Classic Theme can be translated from the main translation page. Also, all the translations systems are now down.
We have to adapt all the translation system to get similar functionalities.
1. Translation selection
The user should select what he want to translate. We have to re-add a select input allowing the user to select between :
If the user select the Themes option, another select input became visible showing :
- Classic (forced)
- All the themes the merchant have installed
As we have a domain tree provided by Crowdin, the base options will get the user on the translation page at a specific point on this tree. A mapping system will be added to allow this system. The first mapping will be:
|Select option||Domain tree path|
The system will be as simple as possible so we can easily modify the mapping.
2. Translation export
A theme translation will be easily exported so the themes creator can translate and ship their themes with some translations.
3. Translation system
For the moment, the translations for a specific domain are application wide, not constrained to a theme. When a theme is installed, the shipped xlf files will be readed but not writed on the database to allow the translations overrides.