Read this guide if you'd like to know
Matomo is available in over 50 languages and comes with many translations. The core itself provides some basic translations for words like "Visitor" and "Help". They are stored in the directory /lang. In addition, each plugin can provide its own translations for wordings that are used in this plugin. They are located in /plugins/*/lang. In those directories you'll find one JSON file for each language. Each language file consists in turn of tokens that belong to a group.
{
"MyPlugin":{
"BlogPost": "Blog post",
"MyToken": "My translation",
"InteractionRate": "Interaction Rate",
"MyParagraphWithALink": "This translated text %1$s uses %2$s parameters."
}
}
A group usually represents the name of a plugin, in this case "MyPlugin". Within this group, all the tokens are listed on the left side and the related translations on the right side.
Translated text entries are allowed to contain sprintf parameters, for example, "This translated text is uses a %s parameter" or "This translated text %1$s uses %2$s parameters.". Every translate function will accept extra parameters that get passed to sprintf with the text.
As you will later see to actually translate a word or a sentence you'll need to know the corresponding translation key. This key is built by combining a group and a token separated by an underscore. You can for instance use the key MyPlugin_BlogPost to get a translation of "Blog post". Defining a new key is as easy as adding a new entry to the "MyPlugin" group.
To replace a key with translated text, Matomo will look into the JSON file for the current language. If no entry can be found, Matomo will use the english translation by default. Therefore, you should always provide a default translation in English for all keys in the file en.json (ie, /plugins/MyPlugin/lang/en.json).
As mentioned Matomo comes with quite a lot of translations. You can and should reuse them but you are supposed to be aware that a translation key might be removed or renamed in the future. It is also possible that a translation key was added in a recent version and therefore is not available in older versions of Matomo. We do not currently announce any of such changes. Still, 99% of the translation keys do not change and it is therefore usually a good idea to reuse existing translations. Especially when you or your company would otherwise not be able to provide them. To find any existing translation keys go to Settings => Translation search in your Matomo installation. The menu item will only appear if the development mode is enabled.
To translate text in PHP, use the Piwik::translate() function. Simply pass any existing translation key and you will get the translated text in the language of the current user in return. The English translation will be returned in case none for the current language exists. For example:
$translatedText = Matomo::translate('MyPlugin_BlogPost');
or
$translatedText = Matomo::translate('MyPlugin_MyParagraphWithALink', '<a href="http:://piwik.org">', '</a>');
// where the key "MyPlugin_MyParagraphWithALink" could look like this:
// "My paragraph has a %1$slink%2$s."
To translate text in Twig templates, use the translate filter. For example,
{{ 'MyPlugin_BlogPost'|translate }}
or
{{ 'MyPlugin_MyParagraphWithALink'|translate('<a href="https://piwik.org">', '</a>') }}
Translating text in the browser is a bit more complicated than on the server. The browser doesn't have access to the translations, and we don't want to send every translation file to every user just so a couple lines of text can be translated.
Matomo solves this problem by allowing plugins to define which translation keys should be available in the browser. It can then send only those translations in the current language to the browser.
To make a translation key available on the client side, use the Translate.getClientSideTranslationKeys event (read more about Events):
// In MyPlugin.php
public function registerEvents()
{
return array(
'Translate.getClientSideTranslationKeys' => 'getClientSideTranslationKeys'
);
}
public function getClientSideTranslationKeys(&$translationKeys)
{
$translationKeys[] = 'MyPlugin_BlogPost';
}
To use these translations in JavaScript, use the global _pk_translate() JavaScript function:
var translatedText = _pk_translate('MyPlugin_BlogPost');
Did you know you can contribute translations to Matomo? In case you want to improve an existing translation, translate a missing one or add a new language go to Matomo Translations and sign up for an account.
As long as you are developing an open source plugin hosted on Github, you may get in touch with us ([translations@matomo.org](mailto:translations@matomo.org?subject=Getting my Matomo plugin translated in other languages)) in order to get your plugin translated by the Matomo translators community.
You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.
While doing the initial setup for your plugin, we will import your english translation file (en.json) in your Github plugin repository, and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in your en.json translation file, the updated English strings will automatically be imported in Transifex.
As soon as we have set up your plugin within our Matomo project on Transifex and there are new translations available, you will be able to update your plugin translations using the Matomo console. You will need a locally installed Matomo with development mode enabled, and your plugin installed. To update the translations go to the Matomo directory on your development box and execute the following command:
./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}
Follow these guidelines when creating your own translation keys:
lcfirst and ucfirst.Use numbered placeholders if more than one is required in your text.
Using numbered placeholders, such as %1$s, %2$s, etc. instead of %s makes it possible for translators to switch the order. That might be necessary to translate it to certain languages properly.
Reduce redundancy in your translated text. If the same text appears in multiple translated text entries, try to move the translated text out by using sprintf parameters. For example, if you have text entries like:
"You cannot use commas."
and "You cannot use underscores."
Try to split them up into something like:
"You cannot use %s."
"commas"
and "underscores".
This guideline is more important for contributions to Matomo Core than for new plugins.