If a node is packaged as a proper module, it can include a message catalog in order to provide translated content in the editor and runtime.
For each node identified in the module’s package.json
, a corresponding set of
message catalogs and help files can be included alongside the node’s .js
file.
Given a node identified as:
"name": "my-node-module",
"node-red": {
"myNode": "myNode/my-node.js"
}
The following message catalogs may exist:
myNode/locales/__language__/my-node.json
myNode/locales/__language__/my-node.html
The locales
directory must be in the same directory as the node’s .js
file.
The __language__
part of the path identifies the language the corresponding files
provide. By default, Node-RED uses en-US
.
The message catalog is a JSON file containing any pieces of text that the node may display in the editor or log in the runtime.
For example:
{
"myNode" : {
"message1": "This is my first message",
"message2": "This is my second message"
}
}
The catalog is loaded under a namespace specific to the node. For the node defined
above, this catalog would be available under the my-node-module/myNode
namespace.
The core nodes use the node-red
namespace.
The help file provides translated versions of the node’s help text that gets displayed within the Info sidebar tab of the editor.
In both the runtime and editor, functions are provided for nodes to look-up messages from the catalogs. These are pre-scoped to the nodes own namespace so it isn’t necessary to include the namespace in the message identifier.
The runtime part of a node can access messages using the RED._()
function. For
example:
If a node sends status messages to the editor, it should set the
text
of the status as the message identifier.
There are a number of commonly used status messages in the core node-red catalog. These can be used by including the namespace in the message identified:
Any HTML element provided in the node template can specify a data-i18n
attribute
to provide the message identify to use. For example:
By default, the text content of an element is replace by the message identified.
It is also possible to set attributes of the element, such as the placeholder
of an <input>
:
It is possible to combine these to specify multiple substitutions. For example, to set both the title attribute and the displayed text:
As well as the data-i18n
attribute for html elements, all node definition
functions (for example, oneditprepare
) can use this._()
to retrieve messages.
Node-RED: Low-code programming for event-driven applications.
Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy