Skip to end of metadata
Go to start of metadata

Translating Booktype interface

There are two components of Booktype to translate: lib/booki and lib/booktypecontrol.

Booktype is a Django application and all rules for translating other Django applications should apply as well. For more info please check this document

Checkout the Booktype repository

If you have Github account you can just fork Booktype repository. You should checkout devel branch.

git clone -b devel

New directories

Create new locale directories (e.g. locale/de/LC_MESSAGES/ for German) for each component.

mkdir -p Booktype/lib/booki/locale/de/LC_MESSAGES/

Create message file

Then in each component directory run the makemessages command (You might have to install a few gettext packages first, before the above command will work), eg for German:

 cd Booktype/lib/booki/ makemessages -l de

 cd ../../Booktype/lib/booktypecontrol/ makemessages -l de

You should end up with two untranslated .po files:


Update info

Update the header information in the commented part at the top of each file.

Start translating

Load these .po files into Poedit and start translating. Enter the team contact information and language into your poedit Edit -> Preferences and Catalog -> Settings, they will be added to the file.

When you save in Poedit, files will be compiled.

Source text is original text you will have to transate. Notes for translators should tell you more about the context of the original text. Be aware, fuzzy translations will not be visible in the Booktype interface. You will have to remove fuzzy flag if you want them to be visible.

Send changes

Now you can send .po and .mo files to the Booktype team. If you have Github account you should send pull request to the Booktype team.

  • No labels