Note: This post assumes that you have cloned and setup Misago installation for development on your machine, as is documented in readme.
Misago is powered by Django which holds translations directly within application's source. At start of translation work one usually extracts those into separate
django.po file that can then be translated and then compiled into
django.mo file that application loads back and uses to replace its messages with. Both of those steps are described in the detail in Django documentation, so I'll won't get into detail here.
Assuming you are on *nix/macos, you may generate
po files for Misago using two commands within
misago directory, just make sure you replace
$1 with your language's code, eg.
django-admin.py makemessages -l $1 -e html,txt,py django-admin.py makemessages -l $1 -d djangojs
This will produce two translation files:
djangojs.po for JS UI, and
django.po for the rest. Those can be compiled by running
django-admin.py compilemessages -l $1 in same directory that
makemessages was ran previously.
Misago0.6 is on Transifex, here. I've generated and uploaded current language files.
About Right to Left languages
Coming from European Culture, Misago was written from left to right and its strings API's don't support right-to-left languages. And even after those were changed to work with r2l languages, there are many more problems to solve like how to handle rl2 and l2r mixing and how to change way output is rendered for those languages.
Ultimately all those problems can be solved somehow, especially if we accept some simplifications. APIs can be easily improved and fork can be maintained by interested party that implements default templates in r2l versions. This means that ultimatelly Misago can be made localizeable to 100% r2l language, but it will require somebody to take task of maintaining "flipped" versions of default templates on himself.