Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/i18n/sync-translations

19 lines
515 B
Plaintext
Raw Normal View History

tools: Add new script to sync translations. We just learned we should be using the "onlytranslated" mode of Transifex. Since the command is getting a bit complex (and you need to remember to run `makemessages` first), it makes sense to have a tool for it.
2017-10-06 08:07:16 +02:00
#!/usr/bin/env bash
docs: Add comment links to i18n documentation.
2020-09-18 20:43:19 +02:00
# See https://zulip.readthedocs.io/en/latest/translating/internationalization.html
# for background on this subsystem.
tools: Add new script to sync translations. We just learned we should be using the "onlytranslated" mode of Transifex. Since the command is getting a bit complex (and you need to remember to run `makemessages` first), it makes sense to have a tool for it.
2017-10-06 08:07:16 +02:00
set -e
set -x
i18n: Tweak makemessages for Django 3.1 parameters. Apparently the default for how this works changed in the Django 2.1 to 3.1 upgrade.
2021-03-23 02:01:38 +01:00
./manage.py makemessages --all
i18n: Adjust Transifex sync-translations download mode. It appears that some server-side change to Transifex resulted in the "onlytranslated" mode deleting some (all?) strings from django.po files that were not translated. Testing determined that the "translator" mode appears to now be the only mode that works with both our django.po and translations.json files (We want to avoid both copying the English strings and deleting strings), so we're switching to that. Background is available here: https://chat.zulip.org/#narrow/stream/3-backend/topic/4.2Ex.20branch.20translations.20sync/near/1187324
2021-06-02 18:33:16 +02:00
tx pull -a -f --mode=translator --minimum-perc=5 "$@"
i18n: Unescape Unicode sequences in JSON. This greatly improves the readability of the diffs and in-codebase translation strings over using ASCII sequences for unicode in the JSON. We've previously noticed [^1] some JSON translation files ending up with escaped Unicode sequences on disk, which Transifex indicates is expected behavior [^2], though it is sometimes fixed by `manage.py compilemessages` [^3]. Further, as noted in #23932 [^4], some JSON translation files include HTML-escaped entities like quotation marks. This script will ingest valid JSON files and output them as proper UTF-8 files with appropriately unescaped (unless otherwise necessary, like double quotes being backslash-escaped) sequences, except when the key itself contains HTML escape sequences (as it's presumed the value of such entries must be pre-escaped before being passed to consumers). [^1]: https://chat.zulip.org/#narrow/stream/58-translation/topic/Transifex.20client/near/1479205 [^2]: https://chat.zulip.org/#narrow/stream/58-translation/topic/an.20email.20for.20Transifex.20support/near/1481287 [^3]: https://chat.zulip.org/#narrow/stream/58-translation/topic/an.20email.20for.20Transifex.20support/near/1481908 [^4]: Which is not end-to-end fixed yet by this commit: that will require a new release of Zulip Server. gitlint-ignore: B1, title-trailing-punctuation, body-min-length, body-is-missing
2023-01-05 04:12:15 +01:00
# For readability, we prefer UTF-8, not ascii, in these JSON files.
find ./locale \
-regextype sed \
-regex '^\./locale/.*/\(mobile\|translations\).json$' \
-exec ./tools/i18n/unescape-contents {} \;
tools: Add new script to sync translations. We just learned we should be using the "onlytranslated" mode of Transifex. Since the command is getting a bit complex (and you need to remember to run `makemessages` first), it makes sense to have a tool for it.
2017-10-06 08:07:16 +02:00
./manage.py compilemessages
scripts: Move mobile i18n code out scripts/. Like other code that is only used in the development environment, this doesn't belong in scripts/.
2019-09-24 21:57:42 +02:00
./tools/i18n/process-mobile-i18n