-
Notifications
You must be signed in to change notification settings - Fork 3
Adding Variants
newmans99 edited this page Aug 28, 2017
·
4 revisions
If you are providing a new Variant translation (e.g., en-GB-Tenant234, fr-CA-Tenant234, en-GB-Finance, en-GB-HR...), start with the existing language-REGION translation (e.g., en-GB, fr-CA), if one does not exist, please follow the instructions for adding a new REGION first.
You need to make the same language string modifications in three different locations. First the database (excel) table; Second, in a JSON file; and Finally, in a RESX file.
- Using Excel, open the ".\data\OrdersData.xls" file.
- On the UI_Strings tab, copy the "StringID, StringValue, and BCP47" data from the desired primary language-REGION (e.g., fr-CA) BCP47 rows.
- Paste those values to the bottom of the table.
- Remove all rows that will be the same as the parent language-REGION (these values will automatically be inherited from the parent language-REGION).
- Provide the translation for all remaining StringValue columns and update the BCP47 value based on the IETF language-REGION-Variant standard (e.g., fr-CA-Tenant890, fr-CA-Tenant436, or fr-CA-Finance, fr-CA-HR).
- Duplicate the primary language language file (e.g., ".\strings\MLjson_fr-CA.json") and edit in your favorite text editor.
- Name the file with the lower case 2 digit language identifier, upper case REGION identifier, and mixed case Variant identifier. e.g., "MLjson_fr-CA-Tenant890.json" for the French Canadian Tenant890 user.
- Update the metadata section by appending your name, date, and language identifier.
- Remove all name:value pairs that will be the same as the parent language-REGION (these values will automatically be inherited from the primary language-REGION).
- For remaining name:value pairs, modify the second value (after the :, and inside the quotes) for each of the language strings.
- Validate that the document is a well formed json file, without extra quotes, colons, comma, etc... (see validator link below)
- Save the file.
- Duplicate the primary language language file (e.g., ".\strings\MLresx_fr-CA.resx") and edit in your favorite text editor.
- Name the file with the lower case 2 digit language identifier, upper case REGION identifier, and mixed case Variant identifier. e.g., "MLresx_fr-CA-Tenant890.resx" for the French Canadian Tenant890 user.
- Update the metadata section by appending your name, date, and language identifier.
- Remove all name:value pairs that will be the same as the parent language-REGION (these values will automatically be inherited from the primary language-REGION).
- For remaining name:value pairs, modify the value for each of the language strings.
- Validate that the document is a well formed XML file, without extra quotes, colons, comma, etc... (see validator link below)
- Save the file.
You can now add additional Variants by repeating the steps above, or if you are done adding Variants you can proceed to adding test users or straight to Test & Submit.
- JSON Validator: https://jsonlint.com
- XML Validator: https://www.w3schools.com/XML/xml_validator.asp