Three simple steps to localize
The German and French Online-Help pages have been created with the help of machine translation. In doubt please read the English original.
Use this sheet to specify the XML file options.
Specifies the formatting options when writing the localized XML files. Possible values are:
|Keep original format||Retain the XML file original format in localized files.|
|Remove white spaces||Remove the leading and trailing white spaces from the elements.|
Specifies how XML entities are processed. Sisulizer always decodes predefined XML entities when reading an XML file. The following table contains the predefined entities:
|Character||Name entity||Hex entity||Integer entity|
Sisulizer always decodes any hex or integer entity. For example if the XML file contains * it will be read as "*".
When creating localized XML file Sisulizer always encodes & and <. Encoding of other predefined entities depends on their usage in the original file. If the original file has encoded them then the localized files created by Sisulizer use the same encoding. If the original uses several encoding methods Sisulizer prefers name encoding over hex and integer encoding, and hex encoding over integer encoding.
If original XML files contains hex or integer encoding that do not belong to the above predefined entities Sisulizer does never use any encoding when writing characters to the localized XML file. Plain character is written instead.
If String entities is checked Sisulizer decodes custom string entities when reading the XML file and encodes them when writing the XML file. A custom string entity is a entity defined either in DOCTYPE element or in the DTD file.
<!ENTITY sportname "Downhill skiing">
Whenever an XML element contains &sportname; it will be expanded to Downhill skiing. For example:
<sample>&sportname; is very fast sport.</sample>
will be expanded to "Downhill skiing is very fast sport".
If String entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as "&sportname; is very fast sport".
When writing localized XML file Sisulizer does never use string entities but writes plain characters.
If File entities is checked Sisulizer decodes custom file entities when reading the XML file and encodes them when writing the XML file. A custom file entity is a file based entity defined either in DOCTYPE element or in the DTD file.
<!ENTITY vehicle SYSTEM "Sports.xml">
The content of Vehicle.xml is:
<?xml version="1.0" encoding="UTF-8"?> <sport>Skiing</sport> <sport>Cycling</sport>
Whenever an XML element contains &sports; it will be expanded to content of Sports.xml file. For example:
will be expanded to:
<sample> <sport>Skiing</sport> <sport>Cycling</sport> </sample>
If File entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as will be read as "&sports;".
When writing localized XML file Sisulizer does never use file entities but writes plain characters.
Localize only those elements that have enabled localize attribute if checked make Sisulizer to localize only those XML elements that contain positive localize attribute.
Context method specifies how context value of formed. Possible values are:
|Item index||Item index is the string context. Each item (code or string) has an index value that is a counting integer values starting from 0.
Compared to String value method this method creates own row for each instance of the same string letting you to translate them in a different way.
This is the default value.
|String value||String value is the string context.
If the source code contains same string twice of more then all instances share the single row and they all are translated in the same way.
Both methods can be used with any file. The difference is how duplicates strings are handled. Item index creates as many rows as there are duplicate strings. String value method always only one row for each string.