Open rdeltour opened 5 years ago
See also the current tooling provided by @danielweck in #257 and #262.
Note that the localization documentation does not mention such crowd-sourcing / collaborative l10n service, yet. The l10n wiki pages currently only describe the tooling available to developers, there are no suggestions for end-user-oriented, human-friendly tools. See: https://github.com/daisy/ace/wiki/Localization https://github.com/daisy/ace-gui/wiki/Localization
Currently, localization is stored in JSON files. We're using custom scripts to manage some localization chores (e.g. missing strings in some locales, keeping locales in sync, etc). However, not all localization contributors are developers, and we can consider using a third party service with a more user-friendly UI for localization contributors (like e.g. Transifex, that is used for EPUBCheck’s localization).
Note: this is primarily for the contributor-facing chores (e.g. identifying missing localized strings, looking-up strings, reviewing localization). The developer-facing chores (e.g. identifying redundant keys, detecting non-localized strings) would still be covered by custom scripts.