Translators, please check your languages for common typos, before your languages will get released for all users on production (which is about to happen very soon):

1. Tap "View Strings" on built-in language (English) and search for " " (single space character). See what strings start or end with a space and check if your translation has ones as well.

On older app version same could be achieved by creating an empty custom localization and pressing "View Strings" on it.

2. Tap "View Strings" on your language and check for " " (two space characters) and see if you have placed extra space anywhere.

3. Tap "View Strings" on your language and check for " " (single space character) and see if you have put extra space/newline in the beginning or the end of the line of any string (which is missing in the built-in language).

Built-in value of the json_ChatDemo.

You can use JSON minifier to minify the value after translation.

Note: app won't recommend to switch to your language until language_continueInLanguage, language_continueInLanguagePopupText, language_appliedLanguage are translated.

New default json_ChatDemo value, which is used, when it's empty (0) or contains invalid JSON.

To simplify chat demo translations, a lot of new keys have been added in 0.21.0.989.

If you don't want to change the scene and want to just translate texts / names, you can set json_ChatDemo to 0 & just translate other json_* strings.

If you have already successfuly translated json_ChatDemo, you can keep it as is and don't translate separate strings, but if you don't modify the scene itself, I'd recommend setting json_ChatDemo to 0.

Updated: Added lang field description.

0.21.0.990 RC

- Added NoDocumentsToShowInChat
- Fixed: "Settings > Interface > Sticker Suggestions by emoji > Disabled" uses MarkdownDisabled key, although there is SuggestStickersNone key.

0.21.0.992 RC

- Separated passcode error messages by type: See PasscodeMismatch*, `PasscodeInvalid*`strings.
- Fixed: Can't install localization files with \ in strings (e.g. needed by json_ChatDemo).
- New strings used in the pop-up when opening application folder when sending files
- Probably fixed: garbage symbols in json_1_* default strings (when translation is missing) on some devices

If you are unable to install localization file or share it as XML, ensure you have translated required strings:

language_code
language_name
language_nameInEnglish
language_dateFormatLocale
language_continueInLanguage
language_continueInLanguagePopupText

Starting Telegram X version 0.21.7.1151 cloud localizations are fully supported.

You can now create your own localizations for Telegram X on Translations Platform and use links like these to share them with others:

https://translations.telegram.org/en/android_x
https://t.me/setlanguage/zh-hans-beta
https://t.me/setlanguage/zh-hant-beta

In-app tools for creating translations files will remain. Old localization files still can be installed and imported into your cloud localization.

Since all changes appear on the translation platform and this channel is no longer useful, it will no longer be used.

Thank you for translating Telegram X to your language!