-Ardour's user interface can be translated into many languages. For this the application uses gettext engine. It works like this: there is a plain text editable PO file for every language that contains a number of sequences like: a line in English, a line in target language and a reference to a line in source code where original text in English comes from. The build system then creates a binary version of each PO file with MO file extension and places it in a system directory where running instance of Ardour will pick and use it.
+Ardour's user interface can be translated into many languages. For this the
+application uses gettext engine. It works like this: there is a plain text
+editable PO file for every language that contains a number of sequences like: a
+line in English, a line in target language and a reference to a line in source
+code where original text in English comes from. The build system then creates a
+binary version of each PO file with MO file extension and places it in a system
+directory where running instance of Ardour will pick and use it.
+
+Ardour has two main PO files to translate: for user interface and for Ardour's
+library. Some messages from the library are actually passed to user interface
+(various warnings, for example), so ideally you have to translate both. For
+example, Russian translations are located here:
+
+gtk2_ardour/po/ru.po
+libs/ardour/po/ru.po