... | ... | @@ -96,7 +96,7 @@ The state of the application is held in a set of object structures under the con |
|
|
Even if the application's main engine is a massive block of code, the user interface is divided into a number of parts, called partials in Ractive.js lingo. Partials feed on the context in which they are invoked, such as an `input` node as the example above.
|
|
|
|
|
|
### Internationalisation
|
|
|
Internationalisation (i18n) is provided with the use of partials named by the message keys, e.g. `{{>pleaseWait}}` which renders ... "Please wait..." when running with English language and "Vent litt..." when running in the Norwegian, which is the default language. The translations resides in the resource bundle files `client/src/i18n/en.js` and `client/src/i18n/no_nb.js` respectively. To select a particular language, e.g. English, add `language=en` as a url parameter.
|
|
|
Internationalisation (i18n) is provided with the use of partials named by the message keys, e.g. `{{>pleaseWait}}` which renders ... "Please wait..." when running with English language and "Vent litt..." when running in the Norwegian, which is the default language. The translations resides in the resource bundle files `client/src/i18n/en.js` and `client/src/i18n/no_nb.js` respectively. To select a particular language, e.g. English, add `language=en` as a url parameter when opening the cataloguing interface.
|
|
|
|
|
|
Since i18n texts are in fact Ractive partials, they may include any markup and use other partials just like bits parts of the front end, even refer to other language keys.
|
|
|
|
... | ... | |