Translation Process for SuiteCommerce Localization

The translation process in SuiteCommerce enables developers to localize text for websites based on user-selected languages. This process ensures that string literals wrapped in the _.translate() function are accurately replaced with corresponding language-specific strings, enhancing the user experience by providing content in a user's preferred language.

How Does the Translation Process Work?

The translation process consists of several key steps:

1. Language Setup: When a specific language is configured for a website, the SuiteScript Server Page (SSP) initially checks if the configured language is correctly set up in NetSuite.

2. String Literal Translation: The application uses _.translate() in JavaScript files to identify string literals that require localization. Each of these strings corresponds with name-value pairs defined in the SC.Translations array within the respective JSON language files.

3. Retrieving Translations: JSON language files are organized in the Languages subfolder for each application module, typically located at Modules > suitecommerce > ShoppingApplication@x.x.x > Languages. These files store the translated values specific to the active language.

4. Content Display: Translations are sent back to the _.translate() function from the SC.Translations array, ensuring that users see the content in their selected language.

Important Considerations

• If a string literal does not have a matching name-value pair in the SC.Translations array for the active language, it will not be replaced during the translation process.
• Localization extends beyond customizable elements, as certain aspects like error messages and date formats are automatically localized by the NetSuite backend, providing a seamless experience for users across different regions.

Example of Using _.translate()

Here’s a simple example illustrating the use of the _.translate() function:

validation: {
    country: { required: true, msg: _('Country is required').translate() }
}

In this instance, if the website is set to Spanish, the string Country is required would display as Se requiere país based on the corresponding entries in the SC.Translations array.

Related Topics

• Pass String Literals
• Set Up NetSuite for Localized Content
• Create Custom String Literals
• Configure Hosts for Sites with Multiple Languages

Key Takeaways:

• The translation process utilizes the _.translate() function to replace string literals with localized content.
• Localization files are structured within the Languages subfolder of application modules.
• If a string literal lacks a corresponding translation, it will remain unchanged.

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