You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want to localize the installer ubports-installer#101, we also need to translate the instruction strings on here. I think it is important not to bloat the config files themselves, so i suggest we continue writing them in English and then build translated versions for the API.
We could make a script to collect all the strings that need to be translated, such as user action bodies and titles and option descriptions. It should output a file to be committed to the repository and parsed by UBports Weblate. Translators gonna translate. Weblate then makes a PR once a week with the updated translated strings. The api build script will then build localized json files in namespaces (eg /v3/devices/eo/bacon.json) with all available translated strings replaced. Unavailable strings remain in English.
Since the API is statically built, we might want to avoid offering languages that are only partially translated or unlikely to be maintained in the future. Once added, it'll be impossible to remove a language again.
The text was updated successfully, but these errors were encountered:
If we want to localize the installer ubports-installer#101, we also need to translate the instruction strings on here. I think it is important not to bloat the config files themselves, so i suggest we continue writing them in English and then build translated versions for the API.
We could make a script to collect all the strings that need to be translated, such as user action bodies and titles and option descriptions. It should output a file to be committed to the repository and parsed by UBports Weblate. Translators gonna translate. Weblate then makes a PR once a week with the updated translated strings. The api build script will then build localized json files in namespaces (eg
/v3/devices/eo/bacon.json
) with all available translated strings replaced. Unavailable strings remain in English.Since the API is statically built, we might want to avoid offering languages that are only partially translated or unlikely to be maintained in the future. Once added, it'll be impossible to remove a language again.
The text was updated successfully, but these errors were encountered: