You can contribute by helping us to translate the bot to your language.
-
Copy the src/i18n/
en.jsonto src/i18n/<lang_code>.json. -
Ensure the following keys are correct:
| key | e.g. 1 | e.g. 2 | e.g. 3 | e.g. 4 |
|---|---|---|---|---|
lang_code1 |
en |
zh-Hans |
yue2 |
zh-Hant |
iso_639_code3 |
en |
zh |
yue |
4 |
language_name |
English |
Simplified Chinese |
Cantonese |
Traditional Chinese |
lang_native_name |
English |
简体中文 |
廣東話 |
正體中文 |
-
Translate other keys to your language.
-
Commit your translation and create a Pull Request.
Special thanks to their free hosting service for libre projects!
Recommended for those who are not familiar with Git or GitHub. You may both improve existing translations or start a new translation for your language.
https://hosted.weblate.org/projects/rss-to-telegram-bot/glossary/
| Language | Translator(s) | Status |
|---|---|---|
| en / English | @Rongronggg9 |  |
| zh-Hans / Simplified Chinese / 简体中文 | @Rongronggg9 |  |
| zh-Hant / Traditional Chinese / 正體中文 | @Rongronggg9 |  |
| yue / Cantonese / 廣東話 | @Rongronggg9 |  |
| it / Italian / Italiano | @Alfy (@AlfyT96) |  |
| ca / Catalan / Català | @maite.guix |  |
| tr / Turkish / Türkçe | @wiseweb-works |  |
| fr / French / français | @Edanas |  |
| id / Indonesian / Bahasa Indonesia | @liimee |  |
Footnotes
-
Shorter is better. Usually, it's the same as
iso_639_code. However, if a language does have multiple common variants and of which no one can be a common standard, consider using an extended IETF language tag instead. Please make sure the language code is IANA-registered and not deprecated or not about to be deprecated. ↩ -
yueis a valid ISO 639-3 code, whilezh-yueis non-standard. ↩ -
Use for fallback. If your language has an ISO 639-1 code, use it. Otherwise, use an ISO 639-2/3 code. Ref: List of ISO 639-1 codes ↩
-
If a language has multiple variants, only the most widely-used one can set
iso_639_code. ↩