View the original community article here
Last tested: Nov 25, 2019
- Step 1: Verify that a
locale
user attribute exists, a manifest file exists in the project, and that manifest file has a localization_settings parameter. - Step 2: Verify that every field/lookml object to be localized has a label, group_label, or description. Localization currently only works on the values in those parameters.
- Step 3: Verify there is both a
<default_locale>.strings
file (usuallyen.strings
) and a<target_locale>.strings
file. Important: both files need to contain the strings we want to localize.
For example, if we want to localize id
to es id
, there needs to be an entry for "id" = "es id"
in es_ES.strings, AND an entry for "id" = "id"
in en.strings. If there is not a value in both, then nothing will localize.
- An important note: the strings in both the .strings and labels are case sensitive.
This content is subject to limited support.