..

..
..
..
..
MICROS Systems Inc.

Knowledge Sharing Document

. . . . . . . . . .
Internationalization Testing

Approvals
Product Management
QA Management
Created
by: N. Suranga De Silva

Document Date: 10/11/13

Revised:

The information contained herein reflects Micros Systems Inc’s intended direction with respect to product strategy. This paper does not
bind Micros Systems Inc., to any contractual obligations. "Micros Systems Inc., endeavors to ensure that the information in this document is
correct and fairly stated, but does not accept liability for any error or omission. Furthermore, this document is not part of any contract or
license save insofar as may be expressly agreed in writing and duly signed with authorized signatures".
IT Consulting ● Technology Implementation ● DW/BI ● BPM ● Application Outsourcing ● Software Testing ● Partner Product Services
 VIRTUSA
MICROS
P R O P O S AL
L

Contents
1 General Overview Internationalization.........................................3

2 Related TP IDs.......................................................................4

3 EMC Configurations for Internationalization..................................6

4 OPS Configuration related to Internationalization...........................10

5 Languages setup for the Property level........................................13

6 Workstation language Change....................................................14

7 Set Language for Employee.......................................................15

8 Page Design – Button Names related language Changes.....................16

9 Order Device language change:..................................................17

10 “Language Translation” Icon on the main Menu.............................18

11 Adding Multi language related Button on the page design..................19

12 Other Related Areas:...............................................................21

 VIRTUSA
MICROS
P R O P O S AL
L

1 General Overview Internationalization

Internationalization means of adapting product to different languages, regional
differences and the process of designing product so that, it can be adapted to various
languages and regions by just changing some parameters without any engineering
changes.

Sample changes done in Internationalization:

 German:

 Arabic:
 VIRTUSA
MICROS
P R O P O S AL
L

 Sample Arabic translation on DB reload:

2 Related TP IDs

 Followings are the User Stories related to the Internationalization as of

10/11/13:
8424 Sbux client printing/check detail/touchscreen/rear display
internationalization

28252 Provide indication of Override in EMC | Menu Item Maintenance

21986 FR | EMC | Restrict Access to Menu Items by Range / Property

14562 Hosting Cost Reduction Testing Overview

27898 GMS | Guest Information Chit Printing

 Related Task List for the Internationalization as of 10/11/13:

10757 Make installFileBuilder picking up the latest installation Script and
Internationalization Script for Core Customer and update CM Cal
Package to download one new file CMTranslationBase.sql
9836 Phase II Reporting Speed - Profile FYI Reporting Engine on WS5/WS4
LX

 Related Bugs List for the Internationalization as of 10/11/13:

26030 Journal | Internationalization : Journal is always displayed in English
Language even when the printed check is in different Language

25799 Journal : Table name in Journal is displayed using the employee

Language instead of WS Language
 VIRTUSA
MICROS
P R O P O S AL
L

25168 Language| TextFiles : When Text File is exported and same file is
imported again then the Fonts and content are completely wrong
23306 Table Name does not work for Language 2 with Employee Language set
to Language 2
9199 Internationalization language module locale id is set in EMC but not in
the database after upgrade
8981 Internationalization : Configuration for IP Printer from OPS should always
take a DOT irrespective of the Locale configured

8980 Internationalization : EMC Exception; Select F8 in Employee Maintenance

module
7607 Internationalization messages that appear on the client must be
translate-able
4719 SCR#3650 CM/Ops Verify all code is in place
internationalization/integration between CM and Simphony

40425 simph 2x | simph ops on iOS takes several minutes to load

8762 CM Differences between the Sbux CM schema and CM Lite schema must
be addressed
4431 SCR#5680 Internationalization: Date Format of the bottom Left Date for
Custom Report
4305 SCR#5764 Internationalization PMC Add Employee does not work if the
employee performing the task has a different langid from the employee
being added
4192 SCR#5521 Internationalization : After a new language, need to restart the
entire application
4181 SCR#5650 Internationalization:Changing Screen Langugae is not
consistent for Dates
3767 SCR#5494 Ops Language 2 strings are used after the value is deleted

3659 SCR#5762 Internationalization Changes to locale module require a full

dbdownload to take effect
8447 Custom Reports Sbux Department Report some elements are inherited
from the employee, not the property

 Related Test Plans List for the Internationalization as of 10/11/13:

8697 Client (Sbux) 'internationalization' tests

 Related Test Case List for the Internationalization as of 10/11/13:

8439 Sbux Client internationalization behavior: Language 2 employee
reporting

8437 Sbux Client internationalization behavior: Language 2 workstation with

language 1 employee
8436 Sbux Client internationalization behavior: Language 2 workstation with
language 2 employee
 VIRTUSA
MICROS
P R O P O S AL
L

8431 Sbux Client internationalization behavior: Language 1 workstation with

language 2 employee
8430 Sbux Client internationalization behavior: Language 1 workstation with
language 1 employee
8428 Sbux Client internationalization setup

3 EMC Configurations for Internationalization

There are 2 options to do Internationalization testing when it comes to EMC and OPS.

1. Test with the real language characters and file formats.

2. Test with simulated language file and language related formats.

Note: - This document will describe the option 2 on the QA perspective. If QA using
the Option 1 please skip the Step 1 below.

1. Create the New Language “EmcText.xml” file by using the below converter.

txt file translator.rar

I. Extract the above attached translator

II. Place the “EmcTxt.xml” in the same folder
III. Double click on the “GenerateTranslatetionFiles” app
IV. Select and provide the details accordingly as below screen
V. Click on “Run” button will create a new translated xml file based on the
given Text Filename Postfix/ Prefix (Postfix and Prefix characters will be
used to identify changes in the internationalisation).
 VIRTUSA
MICROS
P R O P O S AL
L

2. Log out/ Exit from the EMC

3. Back up the Existing EmcText.xml file under Micros/ Simphony2/EmcClient
4. Get the updated language file and place it in Micros/ Simphony2/EmcClient (If
QA dosent have any other language files what we do is update the existing
English text file with Post/ Pre fix and create new text file and put it under
Micros/ Simphony2/EmcClient)

Sample EmcTextNew file –

EmcTextNew.xml

 Existing file – EmcText.xml

 VIRTUSA
MICROS
P R O P O S AL
L

5. Place the New updated Language file – New Language file – EmcTextNew.xml

6. Run “EMCTextUpdater” in the same EmcClient folder.

 VIRTUSA
MICROS
P R O P O S AL
L

7. Updater Log can be found under the same folder.

 VIRTUSA
MICROS
P R O P O S AL
L

8. Then Re-Login to the EMC and verify the changes in the context. Updated
context can be found in EMC.
Note:- The Pre/ Post fix text will be appended to all the context areas.

4 OPS Configuration related to Internationalization

4.1 Languages setup for the Enterprise level

1. Create the below 2 files translated for OPS testing. (Probably can prefix or
postfix values and create new text files)

 OPStxt.xml
 PosCoreText.xml

Note: - if QA have the actual language files Skip the step 1. Else, use the same
translator to change the text files with post and prefix as used in the EMC

2. Navigate to Enterprise> Language and add new language e.g. German

 VIRTUSA
MICROS
P R O P O S AL
L

3. Navigate to the new text files tab and add “OPStxt” and “PosCoreText” as new
text file configuration records.

4. Click on the edit link of the Opstext file record and “select Import from a File”
link
 VIRTUSA
MICROS
P R O P O S AL
L

5. Select the newly translated OpsText (file changed based on the language
changes) file from the saved folder and click on ok.
It will update the context with the changed language accordingly.
 VIRTUSA
MICROS
P R O P O S AL
L

6. Select the newly translated PosCoreText (file changed based on the language
changes) file from the saved folder and click on ok.
It will update the context with the changed language as above.

7. Save the changes in the main menu.

Note: - The above changes will effect to Messages, CSH etc…

5 Languages setup for the Property level

1. Navigate to the “Property Parameters “ under “Setup” tab in property level.

2. Select the 2nd language as what created above under language settings. E. g.
German
 VIRTUSA
MICROS
P R O P O S AL
L

3. Save the changes.

Note: - System allows supporting 4 different languages for “Property” level

Restart the Workstation

6 Workstation language Change

1. Navigate to the Property> Setup> Workstation

 VIRTUSA
MICROS
P R O P O S AL
L

2. Select the exacts WS and change the Language as follows:

3. Log in to the OPS and verify the changes on the text. Language changes are
updated for the context related areas:

Note: - below is used with a simulated language file as Pre/ Postfix as “#G#” to
represent “German”
 VIRTUSA
MICROS
P R O P O S AL
L

7 Set Language for Employee

1. Navigate to Enterprise > Configuration> Personal> Employee maintenance.

2. Search and select the exact employee record to do the language change.
3. Double click on the selected employee record.
4. Under General Tab select the required language for the employee

5. Save the changes.

 VIRTUSA
MICROS
P R O P O S AL
L

Note: - This selection for the employee will overwrite all the language settings in the
enterprise or the Property level.

6. Once the employee logs in to OPS he can see the selected language changes
while property or the enterprise being on other language.

8 Page Design – Button Names related language Changes.

1. Navigate to the page design of the Enterprise level and select a page.

2. Select a button of the page design and click on “ab” icon.

3. It will open up a page where you can assign the other language names for all
the buttons in the page.
4. Manually assign names for the button names on the desired page.
 VIRTUSA
MICROS
P R O P O S AL
L

Note: - you can assign same way by selecting all the pages and manually entering the
names of the buttons on selected language in each page.

5. Save the changes in EMC

6. Log in to OPS and do a DB reload, Changed button names will be reflected in
the pages.

9 Order Device language change:

1. Navigate to the RVC > Setup> Hardware/ Interfaces

2. Click on the Order device
 VIRTUSA
MICROS
P R O P O S AL
L

3. Set the required language to all the order devices.

10 “Language Translation” Icon on the main Menu

We can do the changes on language for the areas like Tender media by using the
“Language Translation” Icon on the main Menu

1. Navigate to Tender media and select the individual record and go to form view.
2. Select the “Name” field and click on the “Language translation” Icon on the
main menu.
3. It will allow assigning different language parameters to the selected item.
 VIRTUSA
MICROS
P R O P O S AL
L

4. Manually need to do assignment for all the Tender media items.

Note: - This is the same way we need to do most of the areas like:
 Service Charge
 Discounts
 Menu Items
 Employee names
 Descriptor’s etc…

11 Adding Multi language related Button on the page design.

OPS supports to add multi language related buttons to be placed on the OPS pages.

1. Navigate to Enterprise >Page Design

2. Select the page where the buttons to be placed.
 VIRTUSA
MICROS
P R O P O S AL
L

 Followings are the functionality description of the each button configuration :

Based on the OPS requirement, can place the Buttons and configure the OPS.

1. Screen Language 1 - This function causes Ops to display the descriptors for the
1st language defined in the system.

2. Screen Language 2 - This function causes Ops to display the descriptors for the
2nd language defined in the system.

3. Screen Language 3 - This function causes Ops to display the descriptors for the
3rd language defined in the system.

4. Screen Language 3 - This function causes Ops to display the descriptors for the
4th language defined in the system.

5. Print Language 1 - This functions causes Ops to send the descriptors for the 1st
language defined in the system to the printer.

6. Print Language 2 - This functions causes Ops to send the descriptors for the 2nd
language defined in the system to the printer.

7. Print Language 3 - This functions causes Ops to send the descriptors for the 3rd
language defined in the system to the printer.

8. Print Language 4 - This functions causes Ops to send the descriptors for the
4th language defined in the system to the printer.

9. Disable Language Translation - Two functions exist in order to troubleshoot

databases in an unfamiliar language or to troubleshoot mislabeled keys.
"Disable Language Translation" will show a button's function in its English-
configured functionality. For example, if the command is "Transaction Cancel",
 VIRTUSA
MICROS
P R O P O S AL
L

then no matter how the button is labeled it will be displayed as [Transaction

Cancel]. If the button contains a 'number' (for example, a menu item contains a
menu item number) then the number will be displayed: [Menu Item:#135]. If
an index exists (usually in conjunction with a number) then it will be displayed
prefixed with an 'i': [Custom Menu Level:#2:i3]. If the command contains
prefixed text the text will be displayed with an asterisk: [Command:*sometext].
If the command contains arguments the text 'args' will be displayed. [Run
Extensibility Application:args]. One can reenable normal text with the button
"Enable Language Translation". If it is desired to always have this functionality
always enabled set the web.config.txt setting "Debug.DoNotTranslate" to
"true". One may or may not want to consider the risk of putting these buttons
on a production database.

10. Enable Language Translation - See Disable Language Translation

11. Screen Language List - This function causes Ops to display a list of available
languages to be displayed. The user can pick one of those languages and then
Ops will switch to it.

12. Print Language List - This function causes Ops to display a list of available
languages to be printed. The user can pick one of those languages and then
Ops will switch to it.

12 Other Related Areas:

1. Following changes under Language changes under Enterprise can be use for
some Asian and Arabic related changes.
 Right to left reading
 IME
 Asian Characters
 VIRTUSA
MICROS
P R O P O S AL
L

 Currency Changes:
 VIRTUSA
MICROS
P R O P O S AL
L

 Currency parameters Enterprise: