Help translate @YTAudioBot — a YouTube audio downloader for Telegram Messenger

Stay tuned for news and updates on our Telegram Channel

---

YTAudioBot is currently available in the following languages:

Language	Contributors
🇺🇸 English (en_US)	Dan
🇮🇹 Italiano (it_IT)	Dan
🇪🇸 Español (es_ES)	Gerardo
🇧🇷 Português (pt_BR)	Rafael
🇮🇱 עברית (he_IL)	PhantomGitHub
🇩🇪 Deutsch (de_DE)	Julian, Alex
🇫🇮 Suomi (fi_FI)	Elias
🇬🇷 Ελληνικά (el_GR)	stamsarger
🇷🇴 Română (ro_RO)	NicuG
🇺🇿 O'zbek (Lt_uz_UZ)	HusanboyBayern
🇮🇩 Bahasa Indonesia (id_ID)	Aldian Hudaya
🇨🇳 简体中文 (zh_CN)	Kris
🦃 Türkçe (tr_TR)	EypCnn, Ilker Binzet

Add yourself here once you submit your translations

All translations, except English (en_US) and Italiano (it_IT), are made by volunteers who decided to help. More translations and improved translations in any language are gratefully accepted!

You don't need to know how to program to create or improve translations. All you need is a text editor, knowledge of the English language and of course knowledge of your own language.

Localization guidelines

• Source/fallback is in English (en_US), updated simultaneously with Italian (it_IT).
• Locale files are stored under messages in JSON format: {"key": "value"}.
• You only need to modify the value of the strings; do not translate the key.
• Keep symbols like *bold*, _italic_, `code`, \\n, \\\" unaltered.
• Do not translate format fields such as {EMOJI} and {keyword}.
• Do not add or omit any text, also try to keep the same string length.
• Some strings are actually a ["list ", "of ", "strings"]. This is a cosmetic need to make .json files tidy.
• Split lines every \\n, but be aware that some long lines have a white space at the end .

How to improve or create a new localization

The process is slightly different depending upon whether you are improving an existing localization or creating a new one.

Improving an existing localization

• Look for the language file you want to review and compare it with English (en_US).
• Edit the translated strings you want to improve or translate the missing ones (null) by following the localization guidelines.
• Send a pull request with your changes.

Creating a new localization

To avoid different people working on the same language at the same time, first check whether your language is not already taken by someone else. So, if it's not listed under Open Issues:

• Open a New Issue to let other people know you are working on a new translation.
  • Put language name and code in the title, e.g. Deutsch (de_DE).

Then, you can start.

• Copy en_US.json and rename the file to your language code, e.g. de_DE.json.
• Edit the file to change the English strings to your language strings by following the localization guidelines.
• Send a pull request with your changes.

If you don't know exactly how to translate a specific string you can set the entire value to null, e.g. "send_feedback": null. This way, it will be replaced with the corresponding string in English (en_US) as a fallback until the translated string is available.

---

I tried to do my best in writing both the English (en_US) translation source and this page to allow a broader access to contributors, but since it's not my native language there might be some imperfections. If you happen to find something to improve (without completely change the meaning), feel free to make changes.

Contacts

• Telegram: @haskell.
• E-Mail: [email protected].
• YTAudioBot: ⚙️ Settings > 💬 Feedback > 📝 Send feedback.