The export options of CrowdIn are mentioned at https://support.crowdin.com/enterprise/project-settings/export/. I have the feeling that the currently active option is “Skip untranslated files”: Only 100% translated files will be included in the exported translation archive.
- OpenHAB should also download partially translated files, where some strings are translated.
In case of bundles/org.openhab.core.semantics/src/main/resources/tags.properties the file is translated in 20 languages in git. The _no file contains 128 lines, the tags_de.properties and tags.property files contain 345 lines (translated strings). The property Property_StateOfCharge is translated only in German and Danish.
At the same time string for “Location_Indoor_Floor_Attic” was translated and approved to Bulgarian 5 years ago, but the file bundles/org.openhab.core.semantics/src/main/resources/tags_bg.properties does not exist yet.
For me to download the translation only when all strings are translated makes no-sense. Because on the next day a new string can be added to the English template.properties file, and then the previously downloaded complete translations will not be any more complete (translate all strings), but will nevertheless be used. At the same time for some strings it is clear how to translate, for others it is not, so it is best to translate only some of the strings. So if a translated string in shipped with openHAB currently depends only on if that string was at the time of the translation the only string in the file. It does not matter how the English-template.properties file has emerged afterwards.
The export options of CrowdIn are mentioned at https://support.crowdin.com/enterprise/project-settings/export/. I have the feeling that the currently active option is “Skip untranslated files”: Only 100% translated files will be included in the exported translation archive.
In case of bundles/org.openhab.core.semantics/src/main/resources/tags.properties the file is translated in 20 languages in git. The _no file contains 128 lines, the tags_de.properties and tags.property files contain 345 lines (translated strings). The property
Property_StateOfChargeis translated only in German and Danish.At the same time string for “Location_Indoor_Floor_Attic” was translated and approved to Bulgarian 5 years ago, but the file bundles/org.openhab.core.semantics/src/main/resources/tags_bg.properties does not exist yet.
For me to download the translation only when all strings are translated makes no-sense. Because on the next day a new string can be added to the English template.properties file, and then the previously downloaded complete translations will not be any more complete (translate all strings), but will nevertheless be used. At the same time for some strings it is clear how to translate, for others it is not, so it is best to translate only some of the strings. So if a translated string in shipped with openHAB currently depends only on if that string was at the time of the translation the only string in the file. It does not matter how the English-template.properties file has emerged afterwards.