Configure public language labels

Language labels tell visitors what each selector option means. They are presentation values layered over a fixed locale identity.

Configure them under:

Settings → POM Translate → Languages setup → Base setup

Choose between catalog and custom labels

POM Translate’s catalog provides:

• the language name in its own language;
• a local country or regional name when applicable;
• the English language name;
• an English country or regional name;
• the locale code and country code.

Language switcher markup can combine these values. A custom label is useful when the site needs a shorter or editorially preferred name, such as:

• English;
• Español;
• Português do Brasil;
• Français (Canada).

Do not use a custom label to hide a material regional distinction that affects content, legal terms, currency, or fulfillment.

Set the main-language label

1. Confirm Settings → General → Site Language is correct.
2. Open Settings → POM Translate → Languages setup → Base setup.
3. Enter plain text in Custom label for the main language.
4. Save the settings.
5. Reload the screen and confirm the value persisted.

The main custom label takes precedence over any accidental additional-row label for the same locale.

Set an additional-language label

1. Find the locale under Additional languages.
2. Enter its text in Custom language label.
3. Keep the selected Language unchanged.
4. Save and reload.
5. Inspect every active selector type.

Each label remains associated with that repeater locale. Reordering the language moves the locale and its label together.

Make the switcher display the custom value

Custom labels are available to the switcher markup engine through:

{%custom_label%}

Open Settings → POM Translate → Languages setup → Language switcher and check the markup used by nav-menu, shortcode, and floating selectors.

If the template uses {%local_label%}, {%label_english%}, or other catalog merge tags instead, changing the custom label will not replace those values. Add {%custom_label%} to the intended markup or choose a catalog label deliberately.

The three selector types can use different markup, so verify each one that is enabled.

Understand label fallback

When another POM Translate screen or integration asks for one readable locale name, the plugin resolves it in this order:

1. custom label;
2. catalog local label;
3. catalog English label;
4. raw locale code.

Switcher markup is more explicit because it renders the merge tags selected by the site owner.

Labels do not change language behavior

A label edit does not alter:

• the source or target locale;
• locale ordering;
• URL prefixes or translated slugs;
• browser-language matching;
• lang, hreflang, or Open Graph locale values;
• stored translations;
• flags and country metadata;
• redirect fallback.

Changing English to International does not turn en_US into another English variant.

Write accessible labels

Use wording that:

• names the language rather than the country alone;
• distinguishes regional variants when both are configured;
• is understandable without relying only on a flag;
• remains concise in dropdown and mobile layouts;
• uses the language’s own writing system where appropriate.

Flags represent places, not languages. Keep a readable text merge tag in selector markup even when an image or emoji is also shown.

Verify the final presentation

For each selector:

1. open the source route and record the visible language names;
2. open every target route;
3. confirm the same locale keeps the same label;
4. verify the current item is identified correctly;
5. inspect keyboard focus and screen-reader text;
6. check dropdown width and mobile wrapping;
7. confirm regional variants remain distinguishable;
8. clear page and CDN caches after changing shared selector output.

Read Order languages when the labels are correct but their sequence is not.