Translating the OTRS Admin Manual
Martin Gruner09. Apr 2013 | Development
The practical examples presented in our technical blog (blog.otrs.com) and now in the expert category in our FAQ blog section serve as a source of ideas and documentation to show what is theoretically possible with OTRS in concrete scenarios or sometimes even for more exotic configurations. All configurations presented here were developed under laboratory conditions as a proof of concept.
We can only guarantee testing and implementation of these concepts to be error-free and productive if implemented in a workshop with one of our OTRS consultants. Without this, the responsibility lies with the customer himself. Please note that configurations from older OTRS versions may not work in the newer ones.
UPDATE: Please note that since OTRS 4, translations are managed exclusively via transifex.
As you may know, the admin manual of OTRS can be translated. We currently have the English source version online at http://otrs.github.io/doc/manual/admin/3.3/en/html/. There are also German and Russian versions, but they are only partly translated and therefore not currently online.
Translating the admin manual is (technically) easy:
Basically, all you have to do to start a new translation is to download one file:
and save it as doc-admin.$YourLanguage.po. For updating an existing translation, just download the existing file. Then translate it with any tool that is able to handle gettext files, there are plenty out there. Just make sure the embedded XML strings are correct also in the translated version. Then send the file to the i18n mailing list, we’ll take care of verifying the xml validity and of generating the translated xml files. You can also send snapshots of the work for verification, of course.
Are there people interested in translating the admin manual to their language? We are particularly interested in help with German and Russian (as there are partial translations available), but any other language will also be welcome. Please send a message to the i18n list if you are interested.
The documentation is licensed under the GNU FDL to make sure that your work stays freely available.