Localization

Localisation

ZBrush 4R8 has localisation options so that users can choose how the ZBrush interface is displayed from a number of different languages. The ZFileUtils now allows users to add localisation to their plugins.

Warning!

ZBrush can only load ZScript TXT files as ANSI/ASCII encoding. This means that you cannot hard code Unicode strings, or include special characters for languages such as Japanese.

Translations for localisation are added to specially formatted XML files. The files must be named using the following form:

The button path applies to any of the interface items. The title text is the name of the button and the info text is the pop-up info.

Important!

The text for each of these must be exactly the same as in the plugin zscript code, otherwise the translation may fail.

Enter the translation for each button text after the trans= . Make sure to use double quotes around the whole string.

The second part of the XML file handles messages, grouped within the <messages> tag. These can be for pop-up messages when the plugin asks the user for input, or they can be used for input strings which can be retrieved by the plugin.

Each message has a tag so that it can be identified when needed during plugin operation. This must be made up of capital letters and underscores.

Enter the translation for each message text after the trans= . Make sure to use double quotes around the whole string. The %arg1% can be used for specific text that is added at runtime, such as the new name of a subtool (as in the example zscript included in the ZFileUtils zip).

Localize text

Function to Localize a given text, tag or UI path

text is in/out:
– as an input, it is used to search for the localized item
– as an output, it is replaced by the localized string

text can refer to a tag, a UI path or be any untranslated text:
– a tag: if it’s formated “#[tagname]”
– a path: if it’s a valid path to a UI item
– any text: if it’s not a tag nor a UI path, then it’s considered as an untranslated text

Localize Title

Function to Localize a given title

text is in/out:
– as an input, it is used to search for the localized item
– as an output, it is replaced by the localized string

text can refer to a tag, a UI path or be any untranslated title:
– a tag: if it’s formated “#[tagname]”
– a path: if it’s a valid path to a UI item
– a title: if it’s not a tag nor a UI path, then it’s considered as an untranslated title

Localize info

Function to Localize a given info

text is in/out:
– as an input, it is used to search for the localized item
– as an output, it is replaced by the localized string

text can refer to a tag, a UI path or be any untranslated info:
– a tag: if it’s formated “#[tagname]”
– a path: if it’s a valid path to a UI item
– a info: if it’s not a tag nor a UI path, then it’s considered as an untranslated info

Localize description

Function to Localize a given description

text is in/out:
– as an input, it is used to search for the localized item
– as an output, it is replaced by the localized string

text can refer to a tag, a UI path or be any untranslated descr:
– a tag: if it’s formated “#[tagname]”
– a path: if it’s a valid path to a UI item
– a descr: if it’s not a tag nor a UI path, then it’s considered as an untranslated description

All rights reserved, Pixologic and the Pixologic logo, ZBrush, and the ZBrush logo, Sculptris, and the Sculptris logo are registered trademarks of Pixologic, Inc.
Various patents pending. All other trademarks are the property of their respective owners.