aaptaha / aaptaha-translations

Translations for Aaptaha.

Translations for Aaptaha

This is a required Aaptaha submodule.

This repo contains the strings for the bot's interface for all languages.

The files are arranged in the same directory structure as in the main repo, with the exception that the files in repo's root folder are in a separate folder named Root here, and a cog's class is in the respective Cog folder.

This must be in sync with the main root, since changes can be critically breaking w.r.t. UX.

English translation serves as the reference translation.

---

Contributing

Join Aaptaha's meta server by using the about command.

Note that all translations will be a part of Aaptaha, and will not be owned by any specific third-party contributor.

Setup

Use Poedit. It is available directly in most package repos, so you can install it directly. For example: sudo apt install poedit.

All commits must be GPG signed. Please see https://docs.github.com/articles/about-gpg/ for knowing more about it and how to set it up.

So the entire setup can be as follows:

sudo apt install poedit
git clone [email protected]:aaptaha/anuvaada.git
cd anuvaada
git config commit.gpgsign=true

Repo

• 0_pot folder will only have the base .pot files.

• Each language must have its own folder for its development, and will only contain the translated strings (i.e., the .po files).

• No folder except 0_generated will have .mo files.

• 0_generated folder will have all the language branches merged and compiled using the script compile.sh. No manual modification should be done.

• 0_* folders must not be touched by anyone except Aaptaha's maintainer.

Translation files

• Project name: Aaptaha Translations.

• PO-Revision-Date must be there.

• Language-Team should be name of language, for eg., Hindi.

• Last Translator field should have your name and email. If you are not comfortable sharing IRL details like me, use your GitHub name and email. Please use the commit email.

• Filename should be name_<lang>.po, where name is the one in .pot file.

• File should be stored in the path by replacing 0_pot with language code. For example, if the .pot file is stored in 0_pot/some_path/name.pot, then the translated .po file should use similar path and thus be stored in <lang>/some_path/name_<lang>.po. This is done to aid in auto-generation.

Translating

Creating new translation files

• Open .pot file in Poedit, then choose the appropriate language.

• In Translation -> Properties, fill the fields appropriately as mentioned above.

• Translate the strings and save in the correct location.

• Commit the .po files.

• Open PR for the respective branch.

Editing existing translation files

• Directly open the .po file in Poedit.

• Do necessary modifications.

• Commit the .po files.

• Open PR for the respective branch.

---

License

Copyright (C) 2021 Gouenji Shuuya (https://github.com/gouenji-shuuya).

Licensed under GNU Affero General Public License v3.0.