rilpoint_mw113

Localisation Technology

 
Line 1: Line 1:
-
== Localization Technology : ==
+
<br>'''Localization Technology :'''
 +
 
Gettext is a mature, widely used framework for modular translation of software. It is the standard for localization in the open source/free software . Gettext uses message-level translation — that is, every "message" displayed to users is translated individually, whether it be a paragraph or a single word,all messages are passed through two functions:
Gettext is a mature, widely used framework for modular translation of software. It is the standard for localization in the open source/free software . Gettext uses message-level translation — that is, every "message" displayed to users is translated individually, whether it be a paragraph or a single word,all messages are passed through two functions:
-
 
+
'''Gettext Files:'''
-
== Gettext Files: ==
+
-
 
+
There are three types of files used in the Gettext translation framework. Depending on the tool you use to translate, you will need to be familiar with some or all of these files. The official Gettext tools package contains command-line tools for creating POTs, manipulating POs, and generating MOs. For those comfortable with a command shell.
There are three types of files used in the Gettext translation framework. Depending on the tool you use to translate, you will need to be familiar with some or all of these files. The official Gettext tools package contains command-line tools for creating POTs, manipulating POs, and generating MOs. For those comfortable with a command shell.
-
 
+
'''POT (Portable Object Template) Files:'''
-
== POT (Portable Object Template) Files: ==
+
-
 
+
The first step in the localization process. A program is used to search through the source code and pick out every string passed.This list is put together in a specially-formatted template file that will form the basis of all translations.
The first step in the localization process. A program is used to search through the source code and pick out every string passed.This list is put together in a specially-formatted template file that will form the basis of all translations.
-
 
+
'''PO (Portable Object) Files:'''
-
== PO (Portable Object) Files: ==
+
-
 
+
The second step in the localization process. Using the POT file as a template, the list of messages are translated and saved as a PO file.
The second step in the localization process. Using the POT file as a template, the list of messages are translated and saved as a PO file.
-
 
+
'''MO (Machine Object) Files:'''
-
== MO (Machine Object) Files: ==
+
-
 
+
The final step in the localization process. The PO file is run through a program that turns it into an optimized machine-readable binary file, which is the MO file. Compiling the translations to machine code makes the localized program much faster in retrieving the translations while it is running.
The final step in the localization process. The PO file is run through a program that turns it into an optimized machine-readable binary file, which is the MO file. Compiling the translations to machine code makes the localized program much faster in retrieving the translations while it is running.

Current revision as of 11:36, 18 February 2011