Documentation > Splunk > Admin Manual > User language and locale

Admin Manual

 


Welcome
What to do first
Start Splunk
Meet Splunk Web and Splunk Apps
Before you configure
Add data and configure inputs
Indexing and event processing
Timestamps
Add and manage users
Manage indexes
Define alerts
Set up backups and retention policies
Configure data security
Set up forwarding and receiving
Deploy to other Splunk instances
Set up distributed search
Manage search jobs
Use Splunk's command line interface (CLI)
Configuration file reference
Troubleshooting

User language and locale

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

User language and locale

Splunk automatically detects every time a user logs in and uses whatever language that user's browser is set to. To switch languages, change the browser's locale settings.

Splunk detects locale strings. A locale string contains two components: a language specifier and a localization specifier. This is usually presented as two lowercase letters and two uppercase letters linked by an underscore. For example, en_US means US English or en_GB for British English. When looking for a suitable translation, Splunk first tries to find an exact match for the whole locale, but will fallback to just the language specifier the entire setting is not available. For example, translations for 'fr' answer to requests for fr_CA and fr_FR. The user's locale also affects how dates, times, numbers etc are formatted as different countries have differing standards on how these entities are formatted.

Refer to "How translation works" in the Developer Manual for more information about localizing Splunk.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/4.0.3/Admin/Userlanguageandlocale"

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 View the Article History for its revisions.


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

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.