Localisation

The UNITADE plugin works with localization without third-party libraries and supports (at the time of writing) all languages ​​supported by the Obsidian application. Do not confuse the localization of the interface and content, UNITADE does not affect your data and the files you work in in any way.

The localization itself is similar in principle to the i18n library, a popular tool for localizing JavaScript/TypeScript projects, with only a small exception - the plugin receives language codes (like US or PO) from Obsidian.

Note

Localization is a static class, so if an unsupported language appears, the plugin will return an error about the lack of localization: this is done so that the user can directly report the lack of "support" for the language and its support will be added, also, within the Obsidian platform, dynamic support for languages ​would be difficult to access.

The localization module is initialized when the plugin is launched (important) and only when it is launched, so to change the language in UNITADE, you need to restart Obsidian (new versions of the application are automatically restarted after changing the language).

More details about supported languages, translation codes and translation contributors can be found in the localisations context:
"Localisations context"

If you are interested in how to help with translation, there is separate documentation:

• Contribution policy
• Code of conduct for UNITADE
• Commit convention (markdown fork)