Chapter 15 string localization and message Dictionary (1)

Chapter 15 String localization and message dictionary （ One ）

This article outlines string localization , And describes how to export 、 Import and manage message dictionaries .

String localization

When localizing the text of an application , Will create a list of text strings for a language , Then when the application locale is different , Establish a convention to replace the translated versions of these messages in another language .

Support the following process of localizing strings ：

1. Developers include localizable strings in their code （ stay REST Applications or business intelligence models ）.

This mechanism varies , But the most common mechanism is $$$Text macro . Instead of hard coded text strings , Developers include $$$Text Instances of macros , Provide the following values for macro parameters ：

• Default string
• The domain to which this string belongs （ When grouping strings into fields , Localization is easier to manage ）
• The language code of the default string

write "Hello world"

Replace with

write $$$TEXT("Hello world","sampledomain","en-us")

2. When compiling code , The compiler will be in the message dictionary as $$$Text Each unique instance of the macro generates entries .

The message dictionary is global , Therefore, you can easily view it in the management portal （ for example ）. There are some class methods that can help with common tasks .

3. After development , The publishing engineer exports the message Dictionary of this domain or all domains .

The result is one or more XML Message file , It contains the text string of the original language .

4. The release engineer sends these documents to the translator , Request translation version .

5. Translators use whatever they like XML Create tools to deal with XML Message file . essentially , They translate text from the original language into a new language , Without changing the surrounding XML.

6. The converter returns a new XML Message file , The file has the same structure and ：

• identification <MsgFile> New language attribute of element RFC1766 value .
• Contains translated text in the recognized language .

7. The release engineer will translate XML The message file is imported into the same namespace as the exported original file .

The translation and the original coexist in the news dictionary .

8. At run time , The application selects the text to be displayed according to the browser's default language .

Message Dictionary

The message dictionary is a global, Include by domain name 、 Language name and message ID Organized text string ：

• The text of each message is at most 32K Character string . If the database enables long strings , Then the string may be longer , But the default maximum value is 32K. Messages may contain only text , It may also contain one or more elements %1、%2 And other specified parameters . When the application page needs , You can replace these parameters with text （ For example, the file name in the error message ） display messages .
• The domain name is an arbitrary string . It identifies a set of related text items , For example, all messages of a specific application or page . If you assign a domain to a group of messages , You can later perform specific actions on all messages with the same domain .

The domain name is case sensitive , It can contain upper and lower case characters . If the domain name uses % start , Think that all messages in this domain are system messages visible in all namespaces . otherwise , When creating messages , It is only visible in the namespace that defines it .

• The language name is consistent with RFC1766 All lowercase language marks . It consists of one or more parts ： Main language labels （ for example en or ja） Optionally followed by a hyphen (-) And secondary language tags （en-gb or ja-jp`）.
• news ID Is an arbitrary string ; It uniquely identifies a message . news ID It only needs to be unique in the domain . You can assign a message ID Or allow the compiler to assign a , It depends on the convention used to create the message . news ID Case sensitive , It can contain upper and lower case characters .

Message dictionary storage

Each user-defined namespace stores its message dictionary under the name ^IRIS.Msg Subscript global . ^IRIS.Msg The subscript order in is domain 、 Language and messages ID.

To view the namespace ^IRIS.Msg

1. Start the management portal .
2. Switch to the namespace of interest .
3. single click System Explorer > Globals.
4. stay IRIS.Msg In line , Click view .

for example

DHC-APP>zw ^IRIS.Msg
^IRIS.Msg("Ensemble")="zh-cn"
^IRIS.Msg("Ensemble","zh-cn",27956811)="Business Rules"
^IRIS.Msg("Ensemble","zh-cn",46484733)="Create New Message Routing Rule"
^IRIS.Msg("Ensemble","zh-cn",52267811)="Business Rule Log"
^IRIS.Msg("Ensemble","zh-cn",56439219)="Edit the configuration of this production."
^IRIS.Msg("Ensemble","zh-cn",59992850)="Edit, Start or Stop an Ensemble Production."
^IRIS.Msg("Ensemble","zh-cn",60154202)="The following PubSub Domain Names are currently defined. PubSub domain names are used to group PubSub subscribers and their associated subscriptions."
^IRIS.Msg("Ensemble","zh-cn",65030300)="Edit Role definition:"
^IRIS.Msg("Ensemble","zh-cn",74372598)="Create New Subscriber"
^IRIS.Msg("Ensemble","zh-cn",103132939)="Defined Data Transformations:"
^IRIS.Msg("Ensemble","zh-cn",140775628)="Suspended"
...

DHC-APP>zw ^CacheMsg
^CacheMsg("Ensemble")="zh-cn"
^CacheMsg("Ensemble","zh-cn",27956811)="Business Rules"
^CacheMsg("Ensemble","zh-cn",39977858)="Select a Business Process"
^CacheMsg("Ensemble","zh-cn",46484733)="Create New Message Routing Rule"
^CacheMsg("Ensemble","zh-cn",52267811)="Business Rule Log"
^CacheMsg("Ensemble","zh-cn",56439219)="Edit the configuration of this production."
^CacheMsg("Ensemble","zh-cn",59992850)="Edit, Start or Stop an Ensemble Production."