Translation: Difference between revisions
Line 41: | Line 41: | ||
====Converting between Unicode notations==== | ====Converting between Unicode notations==== | ||
To convert a file in UTF-8 into \uXXXX Unicode escape notation, you may use [http://java.sun.com/j2se/1.3/docs/tooldocs/win32/native2ascii.html native2ascii] tool included with the Java SDK. Example of use (Resources_cs.properties.txt is before conversion): | To convert a file in UTF-8 into <tt>\uXXXX</tt> Unicode escape notation, you may use [http://java.sun.com/j2se/1.3/docs/tooldocs/win32/native2ascii.html native2ascii] tool included with the Java SDK. Example of use (Resources_cs.properties.txt is before conversion): | ||
<small><!-- Better in CSS style sheet --> | <small><!-- Better in CSS style sheet --> |
Revision as of 10:53, 2 June 2007
How to contribute translations to FreeMind follows. Step-by-step overview
Getting the latest translationsLook for a translation into your language present in the development branch. If such a translation is not present, take the latest revision of Resources_en.properties. Choosing the editing toolTranslation files can be edited using variety of tools. PopeyePopeye Screenshot | Download can deal with several language property files at the same time, so you can contrast the original property file data with their translations. Also, the program can highlight all properties that do not have a translation set in one of the selected languages.
PropeditPropeditScreenshot can directly edit property files written in Unicode reference characters, thereby saving the time and effort of converting into Unicode through native2ascii. Its plugin is integrated with Eclipse and JBuilder. Files can be opened in the IDE and saved in Unicode. See also Propedit project page. Plain text editorA plain text editor is the tool of choice if you are well acquainted with them and prefer them. If so, you already probably have your favorite tool. If not, these tools include Microsoft Notepad, Notepad++, Vim, Emacs and a vast variety of other tools. Using plain text editor is more tricky in that the language translation files are using Java unicode notatiton, encoding a single non-latin character like \u4567, making the file less readable. A workaround is to convert the language file into UTF-8 encoding first, then edit it, and finally convert to Java notation again. The conversion is described in the following section. Once the text is in UTF-8 encoding, tools like Microsoft Notepad can be used, and the non-latin characters are shown as you would see them in a WYSIWYG editor. However, various plain text editors differ in their capability to show UTF-8 characters. Notepad on Windows XP is definitely able to do that. Converting between Unicode notationsTo convert a file in UTF-8 into \uXXXX Unicode escape notation, you may use native2ascii tool included with the Java SDK. Example of use (Resources_cs.properties.txt is before conversion):
cd C:\j2sdk1.4.2\bin> native2ascii.exe -encoding UTF8 Resources_cs.properties.utf8.txt Resources_cs.properties
Ideally, your file's name will be Resources_xx.properties, where xx is the code of the language (e.g. en, de, dk etc.). To convert \uXXXX Unicode encoded file back to UTF-8, use a command similar to the following.
cd C:\j2sdk1.4.2\bin> native2ascii.exe -reverse -encoding UTF8 Resources_cs.properties Resources_cs.properties.utf8.txt
Posting translationsSend your translation to Translations tracker. To be able to do it, you need a SourceForge user. Using new translation in FreeMind
State of translationCurrently, we have the following languages translated. The table below is out of date. It would be nice if the translators would update it. Up-to-date information of the state of translation can in any case be found in CVS and in Translations tracker.
|