Adding languages

Instructions for adding languages (complete all steps for you changes to be merged)...

When adding a new language, you will need to update both the sample database tables for that language and the language strings for the user interface.

Database Tables: Using Excel, open the ".\data\OrdersData.xls" file.

1. On the Sector/Industry tabs, add a new column with the suffix "_XX" where XX = is the IETF language code for the language you are adding. Provide the translation for each row. Make sure that the XX is in upper case, e.g., "Sector_EN".
2. On the Product/Company tabs, copy the "en" rows for each of the IDs and paste them to the end of the table. Translate the Company/Product column values. The language row should be in lower case, e.g., "en".
3. On the Language tab, add a new row for the language that you just added. The language should be in lower case, e.g., "en".

If you are providing a new language, REGION, and/or Variant (tenant/dept), do the following: 1. on the UI_Strings tab, copy the "StringID, StringValue, and BCP47" data for the "default" BCP47 rows. 2. paste those values to the bottom of the table. 3. for REGION translations, remove any strings that will be inherited from the language BCP47. 4. for Variant (tenant/deptartment) translations, remove any strings that will be inherited from the language-REGION BCP47. 5. Provide the translation for the remaining StringValue columns and update the BCP47 value based on the IETF language-region standard (language, OR language-REGION, OR language-REGION-Variant).

Resource Files: JSON If you are providing a new language file (e.g, en, fr, etc...)...

1. Duplicate the "MLjson_default.json" file and edit in your favorite text editor.
2. Rename the file with the lower case 2 digit language identifier. e.g., "MLjson_ku.json" for Kurdish
3. Update the metadata section by appending your name, date, and language identifier.
4. For all name:value pairs, modify the second value (after the :, and inside the quotes) for each of the language strings.
5. Validate that the document is a well formed json file, without extra quotes, colons, comma, etc... (see validator link below)
6. Save the file.

Resources:

• JSON Validator: https://jsonlint.com
• XML Validator: https://www.w3schools.com/XML/xml_validator.asp