Exporting to a Useable format
Once an application has been translated, selected languages or bundles can be exported to a usable format by clicking Generate in the main menu.
The form lets you select which bundles and languages to generate. The completion threshhold enables languages which are partially complete to be omitted from the generated zip file, and the Include Summary checkbox includes a summary of the generated resource files detailing the completion of each language with the zip file.
The ProjectDisplayName.properties file uses the same format as Java.
File Format of ProjectDisplayName.dtd
<!ENTITY ElementName "Translation for element">
<!ENTITY DifferentElementName "Translation for different element">
For more information see Firefox format.
GNU Portable Object (PO)
Each bundle is contained within a different directory in the generated zip file. The language of each bundle is used to generated the filenames. The element comment field is used to hold meta data including references, flags, the message context and any comments extracted from the source code.
# translator comments
#. source code comments
msgctx "context info"
msgid "Untranslated String"
msgstr "Translated String"
For more information see GNU PO Format.
Exporting to Java creates .properties files. The bundle name and locale are used to determine the filename.
ElementName=Translation for element
AnotherElement=Translation for the second element
For example: A bundle called strings in Czech would create a file called strings_cs.properties.
If Escape unicode characters is checked, characters with code points above 127 are converted to unicode escape sequences (\uXXXX). If this is unchecked and the bundle contains high ASCII characters, Java may throw an exception when the resource bundle is loaded.
For more information see Java format.
.NET applications use .resx files. In the example above, the generated file would be called strings.cs.resx.
For more information see .NET format.
.NET Compact Framework
Same as .NET, but with some compatibility changes with some language codes.
Elements are output to PHP files as key/value pairs in an array so they can be used with the print or echo functions. The generated PHP file must be include()d first.
$BundleName = array(
"ElementName" => "Translation for element",
"AnotherElement" => "Translation for the second element",
Elements are output to PHP files as constants so they can be used with the print or echo functions. The generated PHP file just needs to be include()d first.
define("ElementName","Translation for element");
define("AnotherElement","Translation for the second element");