Java Scanner

Overview. Java scanner options allow the user to specify how to localize Java files. By default Multilizer localizes properties files, but it can also be configured to localize Java code files.

The most important settings are the following:

  • Scan directory (Project tab); the base directory for files to localize.
  • Process *.properties files (Project tab); check this setting to ensure that all .properties files get localized.

 

This plug-in is available as a separate plug-in.


Tabs

Project

Scan Directory. This is the most important setting; it tells in which directory the files to localize are located. This field should contain an absolute path or relative path. If the files to localized are in same directory as the Multilizer project, specify '.' here.

Process subfolders. Check this, if there are more files to localize under Scan directory.

Process localized files. By default Multilizer doesn't scan localized .properties files, such as dcalc_en.properties by example. Check this, if you have a good reason to scan something else than the original properties files. Generally this setting should be unchecked, as Multilizer aims to localize properties files following Java standards.

Process *.java files. Checking this enables the localization of .java code files. Normally localizable information is in .properties files, so this setting should be unchecked.

Process *.properties files. Check this to enable localization of .properties files.

Support for Jar files

The Java Scanner supports the localization of files that are inside a Jar package. To enable this, check Process Jar files.

During the localization the files are extracted from the Jar file so the directory should be specified for these temporary files. Ensure that the Folder to extract content of jar files exists.

Output

This tab contains settings that affect localization of .properties files.

Property files

  • Check Write comments to output file, if the localized file should have the same comments as the original file.
  • Check Write empty lines, if the localized property file should have the same empty lines (line feed only) as the original file.
  • Check Write lines where translation equals source string, if you want that the localized file contains all keys that the original file has. In this case missing translations have the Native text instead. Uncheck this setting if you want to create Java standards compliant properties file -- including only those keys for which there is a translation.
  • Check Sort the content of the localized files during the build, if the localized file content should be sorted alphabetically by the key names. If there are comments or empty lines in the file, they will be sorted in the beginning of the document.

Java Escapes

  • Check Remove backslashes from native when not a part of an escape, if there are backslashes that should be removed. For instance the text "Not\epad" in original property file would be converted to "Notepad" when reading the text.
  • Check Convert C-like escapes to Unicode, if the original texts contain C escapes, such as \t. If this setting is enabled the "Note\tab" text in original file would be read in to project as "Noteab" (where is the tab character). This option is enabled only, if the native encoding (Encodings tab) is Unicode escape.
  • Check Use C-like escapes instead of Unicode escapes, if the localized file should contain C-like escapes (e.g., \t) instead of Java Unicode escapes (e.g., \u0009).

Encodings

Native language. Specifies the native language that is used in the target. Set this to match the language in the original file.

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 default language.

Native encoding. Specifies the native encoding that is used when reading the original files. If the encoding is not specified, Unicode escapes are assumed.

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.

Fall-Back language: Specifies the default (base) language for which the software is intended; in other words, specifies the fall-back language.

Excluded Files

Specify here the files that should not be localized.

By default Multilizer localizes all .properties files.