Create Custom String Literals
You can add new or customize existing string literals to change the default language values and corresponding translated values. You have a choice of two methods to accomplish this. The method you use depends on your implementation.
Method 1: Use the SuiteCommerce Configuration Record
This information refers to SuiteCommerce or the Vinson release of SuiteCommerce Advanced or later.
Use the SuiteCommerce Configuration record to specify new string literals that translate at runtime. NetSuite recommends this method when making small changes to translated content.
To configure properties in NetSuite:
-
Select the domain to configure at Commerce > Websites > Configuration.
-
In the SuiteCommerce Configuration record, navigate to the Multi-Domain tab and the Translations subtab.
-
Add custom strings in the available table as needed. See Translations Subtab for details.
-
Save the Configuration record.
Method 2: Extend the Application
This method is required for sites implementing the Kilimanjaro release of SCA and earlier. However, you can also use this method for any Commerce web store implementation when making multiple changes, such that using Method 1 becomes cumbersome.
You can extend the application to change the string literals in the code and update the name-value pairs in the existing SC.Translation arrays.
If using this method on a SuiteCommerce site or a site implementing the Aconcagua release of SCA or later, you must introduce these changes as an extension. See Localize Text in an Extension.
You can also add new string literals that translate at runtime. When extending an application, ensure that new string literals you intend to localize are wrapped in the _.translate() function and that the corresponding language files are updated. If you have a small amount of customization to do, you can manually add the newly translated name-value pairs to the existing SC.Translations arrays for each language. However, if your web store includes many new string literals, NetSuite recommends scripting this process. Each time you compile your website code, all string literals wrapped in the _.translate() function should be processed to generate the appropriate name-value pairs in each language file.
These language files must use UTF-8 character encoding to ensure proper display of international characters.