Localization

Golden Rule

Only ever modify _locales/en/messages.json.

All other locale files (de, fr, it, es, zh_Hans, zh_Hant, pl, ru, pt-br, sv, el, cs, hr, ja, nb_NO) are managed by translators through Weblate. Never edit them manually.

Message File Format

Each entry in _locales/en/messages.json follows the standard WebExtension i18n format:

"key_name": {
    "message": "The English text",
    "description": "Context for translators explaining where/how this string is used"
}

The description field is important — it helps Weblate translators understand the context.

Using Strings in Code

In JavaScript

import { i18n } from './mzta-i18n.js';
const text = i18n('key_name');
// or directly:
const text = browser.i18n.getMessage('key_name');

In HTML

<span data-i18n="key_name"></span>
<!-- or via manifest/attribute references: -->
__MSG_key_name__

In manifest.json

"description": "__MSG_extensionDescription__"

Naming Conventions

Prefix	Usage
`menu_*`	Context menu and popup menu labels
`prompt_*`	Built-in prompt names
`placeholder_*`	Placeholder display names
`options_*`	Settings page labels
`pages_*`	Feature page labels
`error_*`	Error messages
`info_*`	Informational messages
`btn_*`	Button labels

Adding a New String

Open _locales/en/messages.json
Add the new key in alphabetical order within the file (or near related keys)
Include both message and description fields
Use the string in code via browser.i18n.getMessage('key_name') or __MSG_key_name__

Example:

"my_new_feature_label": {
    "message": "My New Feature",
    "description": "Label for the new feature button in the options page"
}

Supported Languages (16)

Code	Language
`en`	English (source)
`de`	German
`es`	Spanish
`fr`	French
`it`	Italian
`pl`	Polish
`ru`	Russian
`pt-br`	Brazilian Portuguese
`sv`	Swedish
`el`	Greek
`cs`	Czech
`hr`	Croatian
`ja`	Japanese
`nb_NO`	Norwegian Bokmål
`zh_Hans`	Chinese Simplified
`zh_Hant`	Chinese Traditional

2.3 KiB Raw Blame History