SYSPRO Languages and Translation

Process

Follow these steps for each workstation that requires SYSPRO to run in French:

1. Ensure that the Lang_FR.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : FR - French
   ; font-prop: {Default}
   ; font-mono: {Default}
   ; xml-encod: Windows-1252

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   French_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as France.

      Changing this setting requires your system to be restarted for the change to take effect.

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as FR.

     This creates an IMPLNG=FR entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=FR at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in German:

1. Ensure that the Lang_DE.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : DE - German
   ; font-prop: {Default}
   ; font-mono: {Default}
   ; xml-encod: Windows-1252

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   German_Phonebook_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Germany.

      Changing this setting requires your system to be restarted for the change to take effect.

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as DE.

     This creates an IMPLNG=DE entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=DE at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Spanish:

1. Ensure that the Lang_ES.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : ES - Spanish
   ; font-prop: {Default}
   ; font-mono: {Default}
   ; xml-encod: Windows-1252

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Modern_Spanish_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Spain.

      Changing this setting requires your system to be restarted for the change to take effect.

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as ES.

     This creates an IMPLNG=ES entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=ES at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Simplified Chinese:

1. Ensure that the Lang_ZH.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : ZH - Chinese
   ; font-prop: SimSun Regular
   ; font-mono: SimSun Regular
   ; xml-encod: GB2312

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Chinese_Simplified_Pinyin_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as China.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as ZH.

     This creates an IMPLNG=ZH entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=ZH at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

5. Enable the use of a double-byte character set (DBCS):

   1. Open the Setup Options program and navigate to the General System Setup section (Setup Options > System Setup > General).

   2. Enable the Use double byte character set (DBCS) setup option.

   This facility ensures that characters are rendered correctly when using SYSPRO Reporting Services.

Process

Follow these steps for each workstation that requires SYSPRO to run in Russian:

1. Ensure that the Lang_RU.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : RU - Russian
   ; font-prop: Arial
   ; font-mono: Courier New
   ; xml-encod: Windows-1251

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Cyrillic_General_100_BIN

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Russia.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as RU.

     This creates an IMPLNG=RU entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=RU at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Thai:

1. Ensure that the Lang_TH.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : TH - Thai
   ; font-prop: Thaiprop
   ; font-mono: ThaiMono
   ; xml-encod: Windows-874

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Thai_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Thailand.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as TH.

     This creates an IMPLNG=TH entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=TH at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

5. Activate SYSPRO's Special language support for each applicable operator:

   This option affects the display of text in the Admin Notepad Editor (Rich Text).

   1. Open the Operator Maintenance program (SYSPRO Ribbon bar > Setup > Operators) and enter or search for the applicable operator code.

   2. Navigate to the Options tab.

   3. Define the Special language support option as Thai.

      This sets the operator's font to Thaimono in the Admin Notepad Editor (Rich Text) program.

      If you are using Thai and don't select this option, then the font is set to Courier new and Thai characters are not displayed correctly.

Process

Follow these steps for each workstation that requires SYSPRO to run in Vietnamese:

1. Ensure that the Lang_VI.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : VI - Vietnamese
   ; font-prop: VNI-Times
   ; font-mono: VPS Courier
   ; xml-encod: Windows-1258

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Vietnamese_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Vietnam.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as VI.

     This creates an IMPLNG=VI entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=VI at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Greek:

1. Ensure that the Lang_EL.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : EL - Greek
   ; font-prop: Arial
   ; font-mono: Consolas
   ; xml-encod: Windows-1253

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Greek_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Greece.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as EL.

     This creates an IMPLNG=EL entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=EL at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Hebrew:

1. Ensure that the Lang_IW.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : IW - Hebrew
   ; font-prop: MS Sans Serif
   ; font-mono: Miriam Fixed
   ; xml-encod: Windows-1255

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Hebrew_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Israel.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as IW.

     This creates an IMPLNG=IW entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=IW at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Dutch:

1. Ensure that the Lang_NL.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : NL - Dutch
   ; font-prop: {Default}
   ; font-mono: {Default}
   ; xml-encod: Windows-1252

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Latin1_General_100_CS_AS

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Netherlands.

      Changing this setting requires your system to be restarted for the change to take effect.

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as NL.

     This creates an IMPLNG=NL entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=NL at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Slovakian:

1. Ensure that the Lang_SK.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : SK - Slovakian
   ; font-prop: {default}
   ; font-mono: {default}
   ; xml-encod: Windows-1250

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Slovak_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Slovakia.

      Changing this setting requires your system to be restarted for the change to take effect.

   3. To ensure that the correct characters reflect when capturing data, ensure that your Microsoft Windows settings cater for the input language required (i.e. foreign language keyboard).

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as SK.

     This creates an IMPLNG=SK entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=SK at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

Process

Follow these steps for each workstation that requires SYSPRO to run in Slovenian:

1. Ensure that the Lang_SL.TXT dictionary exists in your \Base folder and that the dictionary header contains the correct information:

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : SL - Slovenian
   ; font-prop: {default}
   ; font-mono: {default}
   ; xml-encod: Windows-1250

   View the XML encoding and code pages section for header entry options.

2. Configure your SQL Server collation in Microsoft SQL Server:

   • When adding a new database:

     During the configuration of your new database, select the Options tab to indicate a suitable Collation.

   • When using an existing database:

     You can verify the current collation of your existing database by checking the General tab within the database's Properties.

   For example:

   Slovenian_100_BIN2

3. Define the required country against your System Locale in Microsoft Windows:

   1. From your Windows Control Panel, open the application called Region (or Regional Settings depending on your version of Windows).

   2. Ensure that your location is set as Slovenia.

      Changing this setting requires your system to be restarted for the change to take effect.

4. Activate the language you require within SYSPRO:

   You can define the language variable using the Setup Options program within SYSPRO or the command line prompt of your SYSPRO shortcut:

   • Setup Options:

     1. Navigate to the Language field (Setup Options > System Setup > General).

     2. Specify the language code to use as SL.

     This creates an IMPLNG=SL entry in the IMPACT.INI file, configuring the language code as the system-wide default.

   • Command Line:

     1. Append /lang=SL at the end of the current command line.

     This causes the specific instance of SYSPRO to use the defined language code.

     This is useful if you want to have two or more SYSPRO shortcuts, each with a different language code.

1. Create a file on the application server in the \Base folder named:

   Lang_EN_Syspro_Core.TXT

   • This file can be any size (even empty).

2. Log into SYSPRO and run as normal.

   • Ideally you should use a TEST company to ensure that you do not inadvertently change any settings or data whilst performing the following steps.

   • As you run each program, all new captions encountered will be written to the newly created English phrase file. However, if a phrase appears multiple times, only one occurrence will be output to the file.

   • Run each program and perform each function that your end-users will be using. In other words, use the software just as they would in the live environment.

3. Log out of SYSPRO to stop recording new English phrases.

Once you have finished recording the English phrases, you are then ready to start creating the foreign language dictionary.

1. Verify that the English phrases have been captured.

   • The English phrase file is in plain text, so you can use any text editor to verify that the file has been generated.

   • The file can be found on your application server in the \Base\Settings folder, named:

     Lang_EN_new.TXT

2. When you are satisfied that the new phrases have been recorded, switch off the special recording mode by deleting the file in the \Base folder named:

   Lang_EN_Syspro_Core.TXT

   Ensure you are deleting the correct file. If you prefer, you can rename the file (e.g. Lang_EN_Syspro_Core_Saved.TXT.

3. Determine the two-character language code for the required language.

   • We recommend that you select your language code from the ISO-693-1 standard list of two-character language codes.

   • You can find a local copy of the languages and their two-character codes on your application server in the \Base\Store folder, in a file named:

     IMPLNG.IMP

   • We will use the language code PT (i.e. Portuguese) in our example.

4. Copy the list of English phrases you have just generated to a new folder.

   • The file containing the newly created phrases can be found on your application server in the \Base\Settings folder, named:

     Lang_EN_new.TXT

   • Once copied, immediately edit the file using a plain text editor (such as Notepad) and append the following line at the end of the file (but replace yyyy-mm-dd with the current date):

     Copy

     ; ---- End of new phrases – dated yyyy-mm-dd

     Adding this comment will assist if you decide to add more phrases in the future.

     Lines beginning with a semi-colon (;) are treated as comments and ignored by the language translation engine.

5. Copy the file containing the new phrases to a file name that will be used for the new dictionary:

   Lang_PT.TXT

   (Where PT is the two-character language code representing your new language)

6. Edit the new language dictionary Lang_PT.TXT and add the foreign language phrase below each English phrase.

   Don't change or delete the English phrases or the translation will not work. Each English phrase should immediately be followed by the foreign language equivalent.

Once you have added the foreign language phrases you are then ready to verify your newly created foreign language dictionary.

Each new English phrase consists of three lines in the file:

• The first line starts with a semi-colon (;) and is a comment.

  • The special recording mode outputs a comment indicating the program name that was running when the new phrase was first detected, the dates and time when the line was added and the operator code that was running SYSPRO.

  • This information can help pinpoint what caused this phrase to be added.

  • You may remove these comment lines once the translation has completed, as it will reduce the size of the dictionary and in some cases, make the translations easier to read.

• The second line starts with a colon (:) and indicates the English phrase.

  • The English phrase is output with the original case and will contain variables such as %1, %2, etc. if variable data is found.

• The third line starts with a greater-than sign (>) and is a placeholder for the foreign language phrase.

  • This is where your translated text should be captured.

See the following fragment example from a new dictionary:

; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Password
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:User name
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Company
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Company password
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Forgot password?
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:View users
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Exit SYSPRO
>
; Program: IMPACT Date: 2020/12/01 13:52:32 User: RUSS
:Program protected as described in Help About SYSPRO
>
; Program: IMPACT Date: 2020/12/01 13:52:33 User: RUSS
:Connecting to database '%1'

These steps indicate how to verify that your new language dictionary works as expected:

1. Copy your new dictionary to the application server \Base folder – for example:

   Lang_PT.TXT

2. Configure SYSPRO to use your new dictionary.

   • We recommend that you copy the existing shortcut that you use to run SYSPRO and append a new parameter to the end of the current shortcut parameters:

     /Lang=PT

   • Ensure that there is a space before the / character and no other spaces after the / character.

   • You can now use the original shortcut to run SYSPRO in English and the new one to run SYSPRO in Portuguese.

   • Ensure to rename the newly created shortcut so that it’s clear that the new one is Portuguese.

3. Log into SYSPRO using the Portuguese shortcut.

   You should immediately notice that phrases that previously displayed in English now display in the foreign language using the new language dictionary.

4. To verify the translation is performing accurately at a glance, we recommend that you (as a minimum) ensure that the phrases on the main SYSPRO login dialog are translated.

   The captions highlighted as follows should appear in your new language:

   

   This includes the following phrases:

   • User name

   • Password

   • Company

   • Company password

   • Forgot password?

   • Exit SYSPRO

   • Program protected as described in Help About SYSPRO

   The caption on the Login button can't be changed as this is a current limitation of the login dialog.

5. Verify the rest of the software is working in the selected language.

   Remember that only programs and functions that you used when recording the new phrases will appear in the dictionary and therefore only these phrases will have been translated.

6. Optional

   If you require additional phrases to be translated, perform a modified process of repeating the original steps:

   1. Log out of SYSPRO.

   2. Copy your saved file containing the new English phrases (the one where you appended your comment with the date) back to the application server \Base\Settings folder:

      Lang_EN_new.TXT

      • Overwrite the previous file if is still in the folder.

      • Reminder: This is the English phrase file without any new translations. It contains a comment at the bottom indicating where you had last finished translating.

   3. Recreate the file used to start recapturing phrases again in the \Base folder:

      Lang_EN_Syspro_Core.TXT

      If you previously renamed this file – simply rename if back again.

   4. Run SYSPRO using the original (English) shortcut.

   5. Run additional programs and/or additional features so that all the phrases to be translated are displayed.

      This will append any new phrases encountered to the new English phrase file.

   6. Stop the recording mode by removing or renaming the indicator file in the \Base folder:

      Lang_EN_Syspro_Core.TXT

   7. Recopy the new phrase file in the \Base\Settings folder named Lang_EN_new.TXT to your saved folder.

   8. Edit the copied file and append a new comment indicating this is the end of the newly captured phrases with the current date.

   9. Copy and paste the new English phrases added since the last time you had the phrases translated into the dictionary Lang_PT.TXT.

   10. Edit the new dictionary and insert the foreign phrases against each new phrase.

   11. Copy the dictionary back to the application server in the \Base folder:

       Lang_PT.TXT

   12. Retest the dictionary by running SYSPRO again using the Portuguese shortcut.

You are now ready to save and distribute the new dictionary to your operators.

1. We recommended that you apply a header to your newly created language dictionary to help with self-documenting the dictionary.

   Copy and paste the following few lines of text to the beginning of the dictionary (Where PT - Portuguese must be replaced by your selected language):

   Copy

   ; SYSPRO translation file
   ; =======================
   ; Language : PT - Portuguese
   ;
   ; Pairs of lines starting
   ; ':' English text and
   ; '>' Translated text
   ;
   ; Last update : 2020/12/01 14:20
   ;

2. Once you are satisfied with your custom dictionary in the \Base folder named Lang_PT.TXT, you should save the file and copy it to your live system application \Base folder.

In a client-server environment, when someone logs into SYSPRO using the /Lang=PT command line property, the Language dictionary named Lang_PT.TXT will be transferred to the client’s \Base folder – ensuring that the user experiences SYSPRO in Portuguese.

Remember to save (i.e. backup) the newly created dictionary and the one containing the list of new English phrases for future reference. These files will be important if you wish to maintain the dictionary in future.

• Languages that are written right-to-left (e.g. Arabic) are excluded.

• Languages that are written top-to-bottom (e.g. Japanese) are treated as left-to-right.

• Regardless of your selection at the Ship address per line option in the Order Header pane of the Sales Order Entry program, the language code for sales orders is applied at order header level and not at detail line level (i.e. the facility to ship individual sales order lines to different addresses for a specific customer does not apply to multi-language document printing).

• Ensure that the document font you choose supports the printing of any Unicode characters that you may be using.

• When you enable the Multi-language for document printing option, any existing narrations (i.e. narrations saved in your database with spaces against the language field) are then labeled as Global Notes.

• The global narrations print by default when printing documents if you don't select the Print Foreign Text option.

1. Configure the facility:

   1. Open the Setup Options program and navigate to the General System Setup form (Setup Options > System Setup > General).

   2. Enable the Multi-language for document printing setup option.

   3. Indicate the languages you require against the Available languages field.

2. Capture foreign language text:

   Within the Stock Code Maintenance program, capture text in the required languages against the stock code Description, Long description and Notes.

   Before you capture notes in a foreign language, ensure that these notes exist in the default system language (i.e. English).

3. Link language codes to recipients and addresses:

   1. Assign a default language code to use for your suppliers and customers within the Suppliers and Customers programs.

   2. Assign a default language code to each address code as required:

      • Against multiple ship-to addresses within the Multiple Ship to Addresses program.

      • Against alternate delivery addresses within the PO Multiple Delivery Address Maintenance.

   3. Assign a default language code to use against the warehouse in the Warehouse Maintenance program.

      For a Supply chain transfer, the language code against the receiving warehouse is used to determine the language in which the stock description, long description and notes are printed.

4. Select the language code during transaction processing:

   At order header level, select the language code that you want to use for the shipping or delivery address. This retrieves the stock code text in the associated language which will be printed on your documents.

   If the language code against the address is blank then the language code against the customer or supplier is used.

5. Print the documentation:

   When printing documents online or in batch mode, you can enable the Print translated text option to print the stock description, long description and notes in the relevant language. Otherwise the system defaults to printing the information in the system default language.

   • For requisitions, if the Restrict order to single warehouse setup option is enabled (Setup Options > Configuration > Distribution > Purchase Orders) then the language assigned to the warehouse determines the language in which the stock code description, long description and notes are printed.

   • For order documents, the language assigned to the shipping/delivery address determines the language in which the stock code description, long description and notes are printed.

   • For blanket purchase orders, the language assigned to the supplier for the contract is used to determine the language in which the stock code description, long description and notes are printed.

   • For quotations, the language assigned to the customer is used to determine the language in which the stock code description, long description and notes are printed.

A mnemonic is a term used to define or specify a computing function (i.e. an abbreviation for an operation). Mnemonics are used in computing to provide users with a means to quickly access a function, service or process, bypassing the actual, lengthier method used to perform or achieve it.

You can view available mnemonics in a program by holding down the Alt key. The mnemonics (if available) will then display as an underline within each applicable function.

SYSPRO's language translation takes mnemonics into consideration for all languages that use the Latin alphabet. Therefore any applicable or available mnemonics will reflect once your system has been translated. If there is no matching mnemonic character in the foreign language phrase, then no mnemonic will reflect as available.

Not all items within SYSPRO are translatable, therefore the following table highlights the areas where limitations occur:

The majority of issues relating to foreign language support are user interface related, however the following are additional factors to consider:

• Support personnel

  An important part of selling and supporting SYSPRO in a foreign language is to ensure that you have sufficient personnel that are capable of supporting SYSPRO in that foreign language.

• Language variants and/or dialects

  It is important to ascertain whether the territory has different variants or dialects of a single language and whether this may cause a significant challenge.

• Documentation

  Any requirements for foreign language documentation and/or training should be considered as part of the project.

Its not possible to provide a comprehensive list of all conceivable user interface areas that should be verified before supporting a foreign language, however a basic list of suggested areas to research, consider and test are as follows:

1. Font requirements

   Some investigation into font requirements may be required, as certain languages require very specific fonts.

   For example:

   Vietnamese can only display correctly if a font like VNI-Times is used.

   You may also need to use various customization features in SYSPRO or Microsoft Windows to ensure that an appropriate font is configured, as this will ensure that various standard Microsoft Windows dialog boxes (and other products) are displayed in the correct language.

   The following two font types are required within each language dictionary:

   • Font-prop

     A proportional font used in most of the SYSPRO user interface.

   • Font-mono

     A mono-spaced font used, for example, in the Inventory Notes.

2. XML Encoding

   Depending on the language, you may be required to investigate and determine if a specific XML encoding is required for any XML strings. This ensures that data renders correctly, exactly as it was captured.

   By default SYSPRO uses the code page Windows-1252, however Russian (for example) requires the code page Windows-1251 for data captured in Russian to be appropriately rendered.

3. User interface elements

   The following checklist should be used to verify each user interface element in SYSPRO and its components, however this is not an exhaustive list and you should make every effort to fully translate and verify that all user-interface elements render correctly:

   SYSPRO Core UI Elements:

   • Window titles

   • Menu bars

   • Push buttons

   • Entry fields

   • Status bars

   • Customized panes:

     • Headings

     • Menu items

   • Entry & display forms:

     • Captions

     • Entry fields

     • Tooltips

     • Group headings

   • Dialog box titles

   • Toolbars

   • Radio buttons

   • Multi-line entry fields

   • Tree views

   • Browser control (excluding browser contents)

   • Listviews:

     • Headings

     • Contents

   • Message Boxes

   • Tooltips

   • Tab controls

   • Check boxes

   • Shortcut bar

   • Captions (text labels)

   • Calendar control:

     • Captions

     • Tooltips

   Microsoft Windows:

   • Message boxes

   • Font Setup dialog

   • Print Setup dialog

   • Run time print dialog

   • Page Setup dialog

   • Color Setup dialog

   SYSPRO Reporting Services – Report translation:

   • Report headers

   • Report footers

   • Column headings

   • Report headings

   • Report title

   • Total and subtotal captions

   Even though textual data is not translated, you should ensure that data elements (e.g. stock description or customer name) are displayed in the correct font and typeface.

   For example:

   If you enter a customer name using a foreign language, you should ensure that the customer name is printed correctly on a report.

   SYSPRO Reporting Services – Menu system:

   • Window titles

   • Message Boxes

   • Toolbars

   • Push buttons

   • Tab controls

   • Multi-line entry fields

   • Captions

   • Customized panes:

     • Headings

     • Menu items

   • Form designer:

     • Tree views

     • Drag and drop interface

     • Property forms

   • Dialog box titles

   • Menu bars

   • Tooltips

   • Radio buttons

   • Entry fields

   • Check boxes

   • Tree views

   • Listviews:

     • Headings

     • Contents

   • Run time form entry:

     • Captions

     • Report options

   The SYSPRO part of the reporting user interface is handled by the SYSPRO language translation technology, however the underlying technology used for SRS-based reports is Crystal. Therefore, certain dialogs that are used when designing reports originate from Crystal and may require an appropriate Windows Regional Setting.

   SYSPRO Office Integration:

   • Window titles

   • Menu bars

   • Push buttons

   • Entry fields

   • Captions

   • Listviews:

     • Headings

     • Contents

   • Dialog box titles

   • Toolbars

   • Radio buttons

   • Status bars

   • Tree views

   • Customized panes:

     • Headings

     • Menu items

   • Message Boxes

   • Tooltips

   • Tab controls

   • Check boxes

   • Outlook email dialog: Contact information region

   • Property forms:

     • Captions

     • Entry fields

     • Group headings

Before committing to develop a new foreign language dictionary, there are a number of cost elements to consider as part of the decision making process, each of which may be significant:

• Initial costs

  The cost of generating a foreign language dictionary is directly related to the number of unique words and phrases to be translated.

  We recommend using a reputable translation company that has experience in business and technical translations, and that doesn't use automated translations.

  When requesting a quotation you are typically required to provide the word count as they charge a cost per word. In addition, they often have additional charges for special instructions, such as keeping the translated phrases to approximately the same length as (or shorter than) the original phrase.

  This is an important consideration, as text which is significantly longer than the original phrase could cause display errors in SYSPRO.

  In addition, you would most likely have to provide the translators with a list of technical words, jargon, abbreviations and acronyms, along with an explanation in English as to what each of them mean.

  For example:

  • AP = Accounts Payable

  • ATP = Available To Promise

  The SYSPRO development team can supply an example of the instructions that we use for our standard supported translations.

• Maintenance costs

  The cost of generating an initial foreign language dictionary is often the only cost that most people consider, however once the initial translation has been performed, ongoing maintenance must be factored in and this comes at an additional price.

  SYSPRO is a continuously evolving product and is developing at a rapid pace. Therefore, the list of new words and phrases require translation on a periodic basis.

  There is no hard-and-fast rule that dictates how much translation is required from time-to-time, as it depends on the amount of development work, and in which area of the product it is being performed (i.e. in some cases a new module is developed which requires a larger ongoing translation than normal; in other cases a simple enhancement could result in only minimal ongoing translation costs).

  We suggest that if you are considering the translation of a new foreign language, contact the SYSPRO development team to get an approximation as to the amount of ongoing maintenance that has been required in the recent past.

• Verification of the Language Dictionary

  You should consider initial and ongoing verification of SYSPRO in the foreign language. Therefore, after each update to the language dictionary and/or each new version of SYSPRO that is installed, you should perform thorough testing to ensure that the system is working as expected.

An important issue to consider when researching a new language for use in SYSPRO, is the ability to capture data in a foreign language that then reflects in subsequent queries and/or printed documents, exactly as it was captured (e.g. codes, descriptions and notes).

• Part of supporting SYSPRO in a foreign language requires you to verify that all the characters in the language character set are displayed correctly in the various programs. This includes display and entry forms, listviews, grids, messages, etc.

• You should also ensure that the same characters are correctly printed when using the SYSPRO Reporting Services reports and other relevant documents (such as AR statements or Invoices).

SYSPRO software in no way attempts to translate the text that forms part of your data (i.e. if you enter a description or note, the text is not translated from one language to another, but rather is stored and displayed exactly as it was entered).

The ability to enter textual data and have it stored correctly depends on a number of technologies. Therefore, if you require the ability to enter and store foreign text data that then renders correctly, you should consider the following tips regarding SQL Server based data storage:

• SYSPRO companies use Microsoft SQL Server for their data storage mechanism, therefore the vast majority of alphanumeric strings entered in SYSPRO will be stored in the database as a datatype char or varchar.

  The collation defined against the database will determine the valid characters that can be entered and stored in each column.

• SYSPRO reserves a maximum amount of storage for each alphanumeric column, so you should ascertain that this maximum storage is appropriate.

  For example:

  The stock description column is 50 characters: varchar (50).

• SYSPRO databases must have a case-sensitive collation configured.

  There are two broad types of collations that are case-sensitive:

  • Binary collations (where the collation name contains BIN or BIN2)

  • Case sensitive collations (where the collation name contains CS)

  For the best level of performance, a _BIN2 collation should be used (e.g. Latin1_General_BIN2) as this supports many western languages. However, most case-sensitive collations can be used.

  SYSPRO must not be used with a case-insensitive collation (i.e. the collation name selected must not contain _CI).