Internationalisation - zaproxy/zap-hud GitHub Wiki

The HUD is completely internationalised, and PRs that introduce hardcoded display strings will be asked to change :)

For i18n we use https://github.com/kazupon/vue-i18n

There should be plenty of examples in both HTML and JS code, such as:

  • <tab :name="$t('message.history_tool')">
  • <th style="width: 125px"> {{ $t('message.history_http_message_field_time') }} </th>
  • var LABEL = I18n.t("scope_tool");

The i18n'ed messages are loaded from the hud/i18n.js file, which is automatically generated when building the add-on using the UIMessages.properties files. The file is generated with the task generateI18nJsFile into build/genHudFiles/i18nJs/hud/i18n.js.

This is so that we can use our standard ZAP i18n process for i18n'ing the strings using https://crowdin.com/project/owasp-zap

If you want to check to see if the HUD is completely i18n'ed then you need to change the property reviewMode to true of the Gradle task generateI18nJsFile to regenerate the i18n.js file with all of the strings converted to uppercase.

⚠️ **GitHub.com Fallback** ⚠️