651b1c4376
* show missed-call,started-call and answered call notification in chat * fix types for createLastMessageUpdate * show incoming dialog if we have a pending call when enable call receptio * simplify a bit the avatar component * move disableDrag to a custom hook * speed up hash colors of avatarPlaceHolders * fixup text selection and double click reply on message * keep avatar decoded items longer before releasing memory * add incoming/outgoing/missed call notification also, merge that notification with the timer and group notification component * hangup call if no answer after 30sec * refactor SessionInput using hook + add testid field for recovery * disable message request feature flag for now * fix merge issue * force loading screen to be black instead of white for our dark theme user's eyes safety * add type for i18n to run update after crowdin fetch with tools/updateI18nKeysType.py * update to latest translations |
3 years ago | |
|---|---|---|
| .. | ||
| README.md | 5 years ago | |
| afterCrowdInFetch.sh | 4 years ago | |
| compareLocalizedStrings.py | 5 years ago | |
| unusedLocalizedString.py | 4 years ago | |
| updateI18nKeysType.py | 3 years ago | |
README.md
Those tools can be used to keep in sync our locale in the app between different language and with android translations
Step 1: Find unused key locales in EN
tools/unusedLocalizedString.py is iterating over all root keys in _locales/en/message.json and try to find them on the code with a regex. If it does not find it, it will print a line with False.
Some key exceptions are hardcoded to not report false negative
So just run:
tools/unusedLocalizedString.py |grep False
and double check by searching in the app if you can effectively remove those keys.
Step 2: Sync keys between each locales on desktop
This step removes every key in all locales not found in the locale EN.
So if for example, you have a key in it which is not present in en, it will be removed and the it file will be written without it.
A summary for each language file is printed on the screen to let you know if anything was changed during the process
python3 tools/compareLocalizedStrings.py
Step 3: Map translations from android to desktop
This step matches translations from android to desktop. It needs to be run for each locale you want to update.
python3 tools/mapAndroidTranslationsToDesktop.py fr <path_to_android_root_project>
Under the hood, it uses a item from the EN desktop locale called androidKey to find the matching translation for each locale.
Note that if a desktop key does not have an androidKey set, it will just be skipped
The goal is to have an androidKey for each item, if possible. But for now apps are too different for that to make sense.