IcuTemplateOptions

Required text describing how the message will be used.

Translators will use this information to help them understand and translate the message.

Associates placeholder names with example values.

closure-compiler uses this as the contents of the <ex> tag in the XMB file it generates or defaults to - for historical reasons.

• Must be an object literal.
• Ignored at runtime.
• Keys are placeholder names.
• Values are string literals containing example placeholder values. (e.g. "George McFly" for a name placeholder)

Optional text used to differentiate messages with identical original text but different meanings.

This field should usually be left undefined. It should only be used when there exist 2 or more messages that have identical original text but are used in very different ways, so that one translation won't work for both.

For example, maybe "close" needs to be translated in one place as "to close something" but in another as "these things are close to each other".

In such a case, you would specify clarifying text in the "meaning" field. It is different from the "description" field in that "meaning" is used when computing the unique message identifier, but "description" is not. Although this field may be shown to translators, its primary function is just to serve as a point of difference to disambiguate 2 otherwise identical messages.

Associates placeholder names with strings showing how their values are obtained.

This field is intended for use in automatically generated JS code. Human-written code should use meaningful placeholder names instead.

closure-compiler uses this as the contents of the <ph> tag in the XMB file it generates or defaults to - for historical reasons.

• Must be an object literal.
• Ignored at runtime.
• Keys are placeholder names.
• Values are string literals indicating how the value is obtained.
• Typically this is a snippet of source code.