Translations Management for SuiteCom...

TL;DR Opening

This article explains how to manage translations for SuiteCommerce websites by adding or updating string translations using JSON arrays. Effective localization enhances user experience across different languages.

How Can You Manage Translations?

In SuiteCommerce, you can manage translations by utilizing an array that allows you to add new string translations or update existing ones. This method is particularly useful for making small adjustments to your site's translated content. For more comprehensive changes, you will want to refer to the detailed procedures in the Translation Process.

Structure of the Translation Array

Each translation array consists of the following key properties:

Field Name	Type	Description
Key	string	The string to be translated.
Language	string	The localized version for each locale.

Identifiers

Some identifiers in the translation process include:

extraTranslations
extraTranslations.key
extraTranslations.cs_CZ (Czech Republic)
extraTranslations.da_DK (Danish)
extraTranslations.de_DE (German)
extraTranslations.en_AU (English - Australia)
extraTranslations.en_CA (English - Canada)
extraTranslations.en_GB (English - United Kingdom)
extraTranslations.en_US (English - US)
extraTranslations.es_AR (Spanish - Argentina)
extraTranslations.es_ES (Spanish - Spain)
...

This list continues for languages such as Finnish, French, Italian, Japanese, Korean, and many others, covering various locales around the globe.

User Interface Location

To manage translations within SuiteCommerce, navigate to:

Multi-Domain > Translations

JSON Configuration File

The configuration for translations can be found in the Translations.json file, which contains the necessary structure for managing localized strings.

Important Considerations

When localizing your site's content, remember that elements such as NetSuite error messages, dates, and prices are automatically managed by the NetSuite backend and cannot be customized.
Be cautious that if a string literal wrapped in the _.translate() function does not have a corresponding name-value pair in the SC.Translations array for the active language, it will remain unchanged.

Key Takeaways

Use translation arrays for efficient multilingual support in SuiteCommerce.
Each translation must have a corresponding key and localized string.
Improperly paired string literals will not be substituted on the site, impacting user localization experience.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

How do I manage translations for SuiteCommerce websites?

You manage translations by using JSON arrays in SuiteCommerce, allowing for the addition or update of string translations to support multilingual content.

What is the structure of the translation array in SuiteCommerce?

Each translation array consists of a 'Key' for the string to be translated and 'Language' fields representing localized versions for each locale.

Where are translations configured in SuiteCommerce?

Translations in SuiteCommerce are configured in the 'Translations.json' file, which contains the structure necessary for managing localized strings.

What happens if a string literal wrapped in the _.translate() function doesn't have a corresponding translation in SC.Translations?

If a string literal wrapped in the _.translate() function lacks a corresponding entry in the SC.Translations array for the active language, it will remain unchanged.

Translations Management for SuiteCommerce Websites