Dita Scanner
Overview. The Dita scanner reads in the original Dita-files and writes out localized files, without breaking the structure of the original files.
The Dita scanner options allow the user to specify how to localize Dita files. The most important settings are the following:
- File (Project tab); the Dita file to localize
- Context attribute (Settings tab); a user-specified unique attribute that will be the context of the translation.
- Elements (Elements tab); which tags are localized.
Usage
Dita scanner is very simple to use; the user specifies the context id (Settings tab) and the tags to localize (Elements tab).
Nested tags
If elements that user wants to localize contain nested tags, they will be localized too. Nested tags are shown in localizable text and can be modified.
Nested tags can be
- removed
- reordered
- added
- changed
When building the localized files, Multilizer gives warnings about all actions performed on nested tags.
Tabs
The Dita scanner options has the following four tabs:
Settings
Context mode. Dita scanner provides two methods for identifying localizable data:
- Unique attribute value. Dita scanner assumes that all elements intended for localization are have an attribute that contains a unique value. Multilizer Dita scanner uses this value to form the context of the translation. When Multilizer reads the original Dita-file, it checks that the values are unique.
- Combination of node name + value hash. Localizable data is identified by a combination of node name and its value.
The use of unique attribute values for identifying localizable data is strongly encouraged.
Encodings
Native language. Specifies the native language that is used in the target . Set this to match the language in the original user interface. If the original user interface contains two or more languages mixed, set the language to most widely used.
Default language. Specifies the default language. It is the language that is used in the build process, if there is no translation given in the the build language. The translation search order is following: first the build languages, then the country neutral languages (if the build language is country specific), then the default language. If no translation is found then the native value is used. For example if the project contains English, German and German (Austria) and the build language is German (Austria) and the default language is English the search order is German (Austria) - German - English - native.
Native encoding. Specifies the native encoding that is used in the target with each character set.
Encoding list. Contains the encodings to be used in the localized files. To change the value right click the line and select a new value.
Output
Output directory. Specifies the directory where the localized files will be created. This is the directory where Multilizer creates the localized output files and sub directories. You can control the name of the localized files and directories by setting Type, Coding, Locale separator and Country separator.
Output file name
Type. Specifies how and where MULTILIZER creates the localized file version(s). Possible options are:
| Subdirectory | Create localized file(s) in sub directories named by language and locale. |
| Bundle name | Append the language and locale information in the output file name. |
| File extension | Replace the original file extension with language and locale information. |
Coding. Selects file name initial coding style. Possible values are:
| ISO | ISO standard coding style. |
| .NET | Microsoft .Net coding style. |
| Windows | Windows coding style. |
Elements
Not necessarily all nodes in Dita-files contain localizable data. The names of those tags that contain localizable text can be specified in elements tab. If the localizable tags contain child nodes, they will be localized as well.