Working with a multilingual workspace

Multiple languages are available as part of the Advanced and Ultimate plans. Your workspace's languages are set when your account is created; to add or change them, contact Huwise.

If your workspace supports more than one language, several parts of Huwise can adapt to whichever language a visitor or administrator is using.

This spans three distinct layers:

• The interface itself

• How your portal is presented

• How your data and metadata behave

Each layer works differently and is configured in a different place, so this page orients you and points you to the right article for each.

This is the language your portal's navigation and your back office are displayed in, which is separate from any translation of your actual data.

By default, visitors see your portal in their browser's language, and you can share a link in a specific language using the ?flg=XX parameter.

See Languages supported by Huwise for the full list of supported languages, the plans they require, and where to switch languages in the portal and back office.

Beyond the interface itself, you can customize how your portal looks and behaves differently for each language — your header and footer, code-editor pages, basemap labels, and, for datasets, which schema fields are shown for which language.

See How to customize my portal according to the current language for more information.

Two different mechanisms let your data adapt to a reader's language, and it's easy to confuse them:

• Translating a field gives a single field a different value per language, for example a dataset's title or description.

• Displaying a field by language shows or hides an entire field depending on language, without translating it. This is useful when your dataset already has a separate column per language for the same information.

Both are covered, side by side, in Translating and adapting an asset's metadata and schema.

Note that not everything in Huwise can vary by language. The business glossary is a notable exception: a glossary term has a single name and description, used regardless of the portal's language.

Also, if you're using the legacy experience, see Legacy: Translating a dataset instead.