Splunk® Enterprise

Developing Views and Apps for Splunk Web

Download manual as PDF

Download topic as PDF

UI internationalization

Internationalize the Splunk Web user interface.

  • Translate text generated by Python code, JavaScript code, views, menus and Mako templates.
  • Set language/locale specific alternatives for static resources such as images, CSS, other media.
  • Create new languages or locales.
  • Format times, dates and other numerical strings.


Splunk software translation

Splunk software uses the language settings for the browser where you are accessing Splunk Web. You can change the browser language settings to see the user interface in another language.

Locale strings indicate the language and location that Splunk software uses to translate the user interface. Typically, a locale string consists of two lowercase letters and two uppercase letters linked by an underscore. For example, en_US means American English while en_GB means British English.

Splunk software first tries to find an exact match for the full locale string but falls back to the language specifier if settings are not available for the full locale. For example, translations for fr answer to requests for fr_CA and fr_FR (French, Canada and France respectively).

In addition to language, translation also addresses the formatting of dates, times, numbers, and other localized settings.


Configuration

Splunk software uses the gettext internationalization and localization (i18n) system.

Steps

  1. Create a directory for the locale. For example, to create the fictional locale mz, create the following directory.
    $SPLUNK_HOME/lib/python2.7/site-packages/splunk/appserver/mrsparkle/locale/mz_MZ/LC_MESSAGES/
  2. Load the following messages.pot file into your PO editor.
    $SPLUNK_HOME/lib/python2.7/site-packages/splunk/appserver/mrsparkle/locale/messages.pot
  3. Use the PO editor to translate any strings that you want to localize. Save the file as messages.po in the directory you created in the previous step. The PO editor also saves a messages.mo file, which is the machine readable version of the PO file.
  4. Restart the Splunk instance. No other configuration file edits are required. Splunk software detects the new language files when it restarts.

Localization files

The Splunk platform stores localization information at the following location.

$SPLUNK_HOME/lib/python<version>/site-packages/splunk/appserver/mrsparkle/locale

This directory contains the following items.

  • messages.pot: Holds the strings to translate. You can use a PO editor to edit these files.
  • <locale_string>: Directory containing localization files for the locale specified by <locale_string> (for example, ja_JP).
  • <locale_string>/LC_MESSAGES/messages.po: Contains the source strings specified for localization in messages.pot. Using a PO editor, provide the translations for these strings.
  • <locale_string>/LC_MESSAGES/messages.mo: Machine readable version of messages.po. Splunk software uses this file to find translated strings. The PO editor creates the file for you when it creates the messages.po file.

Localize dates and numbers

You can format numbers and dates to the standards of a locale without translating any text. Create a directory for the locale whose numbers and dates you want to format. Copy the contents of the en_US directory to the target locale directory.

Example
Enable localization of numbers and dates for the de_CH locale (German – Switzerland).

Create the following target directory for the de_CH locale.

$SPLUNK_HOME/lib/python2.7/site-packages/splunk/appserver/mrsparkle/locale/de_CH

Copy the contents of the following directory.

$SPLUNK_HOME/lib/python2.7/site-packages/splunk/appserver/mrsparkle/locale/en_US 

Copy the contents from the en_US directory into the de_CH directory.

Translate Apps

You can use gettext to translate apps. Most apps must be translated in their own locale subdirectory.

Apps that ship with the Splunk platform are automatically extracted and their text is included in the core messages.pot file. You do not need to handle them separately.

To extract the strings from an installed app and make the strings ready for translation in a PO editor, run the following extraction command on the command line.

> splunk extract i18n -app <app_name>

This creates a locale/ subdirectory in the app root directory and populates it with a messages.pot file.

Follow the steps above to translate the strings within the app. When using views from a different app, the new messages.pot file contains the strings for these views.

Locale-specific resources

The Splunk platform stores static resources such as images, CSS files, and other media as subdirectories at the following location.

$SPLUNK_HOME/share/splunk/search_mrsparkle/exposed/

When serving these resources, Splunk software checks to see whether a localized version of the resource is available before falling back to the default resource. For example, if your locale is set to fr_FR, Splunk software searches for the logo image file in the following order.

  • exposed/img/skins/default/logo-mrsparkle-fr_FR.gif
  • exposed/img/skins/default/logo-mrsparkle-fr.gif
  • exposed/img/skins/default/logo-mrsparkle.gif

Splunk software follows the same path to load HTML templates (including any views) that define each page in the UI. This can be useful for languages that require a modified layout that CSS alone cannot accommodate (right to left text for example).

PREVIOUS
Customize dashboard styling and behavior
  NEXT
Developer resources

This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 7.0.0


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters