Skip to content
This repository
Fetching contributors…

Cannot retrieve contributors at this time

file 57 lines (57 sloc) 9.908 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Howto: Translate LameXP v4.xx</title>
<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
<style type="text/css">
<!--
a { text-decoration:none; color:#0000EE; transition:color 0.5s ease; -moz-transition:background-color 0.5s ease; -o-transition:background-color 0.5s ease; -webkit-transition:background-color 0.5s ease; }
a:hover { background-color: #CCCCCC; }
a:active { color: #551A8B; }
a:visited { color: #0000EE; }
-->
</style>
</head>
<body>
<h1>Howto: Translate LameXP</h1>
<p><b>If you are willing to contribute a new LameXP v4.xx translation or update/fix an existing translation, then this guide will help you to do so :-)</b></p>
<br>
<img src="http://lamexp.sourceforge.net/lamexp.png" alt="Screenshot"><br>
<br>
<h3>Prerequisites:</h3>
<p>LameXP v4.xx is a complete re-write of LameXP. This time LameXP is developed in C++ and it is based on the <a href="http://qt.nokia.com/products/" target="_blank">Qt</a> cross-platform application framework. The good news for translators is that Qt provides <i>full Unicode support</i>, which was also one of the main reasons for the re-write. Consequently there will be no more headache with different Codepages! Furthermore the Qt framework provides a sophisticated translation system, which allows for easy internationalization and localization. There even is an easy-to-use graphical tool for translating Qt application, the <a href="http://doc.qt.nokia.com/latest/linguist-manual.html" target="_blank">Qt Linguist</a>. So before you start translating, you should make yourself familiar with the <i>Qt Linguist</i> application. As a translator, having a quick look at the <a href="http://doc.qt.nokia.com/latest/linguist-translators.html" target="_blank">guide for translators</a> is sufficient.</p>
<p>You can download <i>Qt Linguist</i> as a part of the Qt Framework (SDK), which is available as a free download from the <a href="http://qt.nokia.com/downloads" target="_blank">Qt download site</a>. You should pick the "Qt SDK" and download the "Online installer" (&sim;15 MB), but you do <b>not</b> need to worry about a "commercial" license. In the Qt SDK Setup wizard, make sure you select the "Custom" install type. Then un-check all components, except for "Qt SDK" &rArr; "Development Tools" &rArr; "Qt Liguist". Alternatively, if you don't want to install the Qt SDK on your computer, you can find Qt Linguist for Windows as a <i>stand-alone</i> download at <a href="http://sourceforge.net/projects/lamexp/files/Miscellaneous/Qt%20Linguist/" target="_blank">this</a> location (only &sim;4 MB). The stand-alone Linguist version has been built using <i>static</i> Qt libraries and thus should work "out of the box", just unzip the ZIP file and run the "linguist.exe" file.</p>
<br>
<h3>Editing the language file:</h3>
<p>LameXP v4.xx translations are created as TS (translation) files, which can be edited using the <i>Qt Linguist</i> application. For new translations an empty TS file ("Blank.ts") is provided in the LameXP Git repository. When you open the empty TS file for the first time, Qt Linguist will ask for some basic settings. Here you must keep the "Source language" options at "English" and "Any Country". Change the "Target language" options to whatever language (region) you are going to translate to. Once you have edited all (or some) text strings, you can save your work to a TS file again. It is recommended to save your work to "LameXP_XX.ts", where <i>XX</i> should be replaced with the suitable upper-case <a href="http://www.loc.gov/standards/iso639-2/php/code_list.php" target="_blank">ISO 639-1</a> Code for the representation of names of languages (for example the German translation is saved as "LameXP_DE.ts", because the corresponding ISO 639-1 code is DE). You can re-open your TS file at any time in order to continue with your work. In case you want to improve an existing LameXP translation, simply download the corresponding TS file from the LameXP Git repository and edit it using the Qt Linguist tool.</p>
<p>The latest translation (TS) files can always be found in the LameXP Git repository at:<br><a href="https://github.com/lordmulder/LameXP/tree/master/etc/Translation" target="_blank">https://github.com/lordmulder/LameXP/tree/master/etc/Translation</a><br><br style="line-height:10px">After you have chosen a file from the directory tree, you can download the file by right-clicking on <b>"raw"</b> button (in the upper right corner) an choosing "Save Link Target As...".<br><img src="http://img192.imageshack.us/img192/803/rawy.png" alt="Raw"></p>
<p style="border-width:2px;border-style:solid;border-color:darkred;margin-top:2em"><font color="darkred"><b>IMPORTANT:</b> Before you start to create a new translation, always make sure you downloaded the <i>latest</i> "Blank.ts" file from the LameXP Git repository. Also before you start editing or updating an <i>existing</i> translation, including translations you have created yourself, make sure you downloaded the <i>latest</i> TS file from the LameXP Git repository. <i>Never</i> do any translations based on an old working copy (TS file) from your local system! The translation files (TS) in the Git repository will be updated/extended continuously, as the development proceeds. We cannot accept translations based on an <i>outdated</i> TS file!</font></p>
<br>
<h3>Language file editing rules:</h3>
Only language files that have been edited according to the following rules can be accepted:
<ul>
<li>The translated string should <i>not</i> be significant longer (or shorter) than the original string, so the layout isn't destroyed.
<li>Strings don't have to be translated literally, as long as the original meaning is retained.
<li>Do <i>not</i> use any HTML-style tags, like <tt>&lt;b&gt;&hellip;&lt;/b&gt;</tt>, <tt>&lt;i&gt;&hellip;&lt;/i&gt;</tt> or <tt>&lt;u&gt;&hellip;&lt;/u&gt;</tt> in your translated text, except when present in the original string.
<li>Take care of the <a href="http://en.wikipedia.org/wiki/Printf" target="_blank">C printf</a> syntax: All the <tt>%s</tt> and <tt>%d</tt> placeholders <i>must</i> remain in the translated strings, at the appropriate position.
<li>All Qt-style placeholders, like <tt>%1</tt>, <tt>%2</tt> and so on, <i>must</i> remain in the translated strings, at the appropriate position.
<li>Once the translation for a string is finished, please click the 'mark item as done' button, so the item (string) gets a green <font style="color:darkgreen">&#10004;</font> icon.
<li>Note that the red <font style="color:darkred;font-weight:bold">!</font> icon and the yellow <font style="color:#AA8B0F">&#10004;</font> icon indicate that there is some problem with your translation, which needs to be resolved!
</ul>
<br>
<h3>Testing your translation:</h3>
<p>LameXP v4.xx needs to be re-built from the sources in order to integrate a new translation or to update one of the "built-in" translations. However there is an easy method to test your translation file <i>without</i> re-building LameXP: Open your current translation (TS) file in the Qt Linguist application and goto "File" &rArr; "Release As...", which allows you to save your translation as a "release" (QM) file. Once saved as a QM file, you can load your translation in LameXP. Just goto "View" &rArr; "Language" &rArr; "From File..." and choose the desired QM file. Your translation should be in effect immediately. If you notice that your translation needs further modifications, go back to the TS file for editing. Then, for your next test run, create a new QM file from the updated TS file.</p>
<br>
<h3>Submitting your translation:</h3>
<p>Once you are done with your translation (i.e. all items and all contexts have a green <font style="color:darkgreen">&#10004;</font> icon), you can submit it, so it can be integrated into the next LameXP release. You can contact me by e-mail:<br><b><a href="mailto:mulder2%20[at]%20gmx%20[dot]%20de">mulder2<font color="dimgray">[at]</font>gmx<font color="dimgray">[dot]</font>de</a></b></p>
<p>Please do <i>not</i> submit translations that have any items/context with <font style="color:#AA8B0F">&#10004;</font>, <font style="color:#AA8B0F;font-weight:bold">?</font>, <font style="color:#427D7E;font-weight:bold">?</font> or even <font style="color:darkred;font-weight:bold">!</font> icon left. Also do <i>not</i> submit QM files, do <i>not</i> compress the submitted file (ZIP, RAR, etc) and do <i>not</i> attach a flag icon file. It is sufficient to submit the translation (TS) file.</p>
<p>(Note: Advanced translators can get write-access to the Git repository on request, so they can keep their translations up-to-date easily)</p>
<p style="border-width:2px;border-style:solid;border-color:darkred;margin-top:2em"><font color="darkred"><b>IMPORTANT:</b> Before you start to create a new translation, always make sure you downloaded the <i>latest</i> "Blank.ts" file from the LameXP Git repository. Also before you start editing or updating an <i>existing</i> translation, including translations you have created yourself, make sure you downloaded the <i>latest</i> TS file from the LameXP Git repository. <i>Never</i> do any translations based on an old working copy (TS file) from your local system! The translation files (TS) in the Git repository will be updated/extended continuously, as the development proceeds. We cannot accept translations based on an <i>outdated</i> TS file!</font></p>
<br>
<h3>Personalization:</h3>
<p>Usually all translators will be mentioned in the "About..." dialogue. If you don't want your (nick)name and/or e-mail address to appear there, please tell us how you want to be credited!</p>
<br>
<br>
Thanks in advance !!!<br><br><img src="http://forum.doom9.org/images/smilies/thanks-t.gif" alt="emoticon">
</body>
</html>
Something went wrong with that request. Please try again.