Browse Prior Art Database

Unique Resource ID for Translation Verification Test (TVT)

IP.com Disclosure Number: IPCOM000033940D
Original Publication Date: 2005-Jan-06
Included in the Prior Art Database: 2005-Jan-06
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Abstract

Abscract: PII(Program Integrated Information) is a string message displayed in GUI. The PII strings are externalized from a program itself to text files for translation. TVT(Translation Verification Test) testers and program development team test translation of PII(Program Integrated Information). We invented string resource ID for TVT. This string resource ID is shown in front of each string PII. TVT testers can find the location of a target string in resource files with the help of this resource ID. This disclosure explains the ID, how it is implemented, and its use in TVT. This ID is implemented independently of the target program, and is applicable to all programming languages that externalize string resources. The time to find the string location in external resources by TVT tester to fix translation errors becomes more than ten times shorter than before with the ID.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Unique Resource ID for Translation Verification Test (TVT)

Background:

For example, an application have the task bar with the selection of "Edit" when it is translated from English from other langugae. Ordinary TVT test system displays "Edit". Nobody knows where the string "Edit" is located in at what string file and what lines in its file. Usually "grep" function in OS or in Editors is used to locate the string in resource files. It requires much process time if the number of files are large. It cannot identify the location if multiple strings are joined and displayed in GUI. If multiple same strings exist in resource files, identifying the location of the corresponding displayed string resource is impossible.

New ID:

New ID is introduced to solve the problems. The ID's are inserted into the externalized string resources for the TVT system by a program. For example, the "(E1744.6)Edit" is displayed in GUI. This ID, (E1744.6), means that the "Edit" string locates at 6th line of the file numbered 1744. A Map is prepared by the program to indicate that file numbered 1744 is a file named windowTaskBarMenu.properties. The TVT tester can identify that this string comes from English resource by referring the prefix of 'E'. If ID is not shown in the TVT system with ID, it implies that the source string does not come from external string files. In most of the cases, it is a hard coded string that is located in a program itself, not in external string resource.

How the ID's are implemented: New string resource files are created by a program for a TVT system from original string resource. The ID's are inserted in the new string resource by the program. The new string resource files replace original string resource files when a TVT is done. No change is made to original string resource and no modification is done to the target developing software at all.

As an example, there is an application that has a task bar, "File", "Edit", "View", "Option" as an translation into English from other language such as French. French external string resource files were translated into English string resource files. The translated resource file, sampleResourceL.properties, has the following contents with incorrect translation, View_er.

keyA=File keyB=Edit keyC=View_er keyD=Option

The sampleResourceL.properties is the 12th fi...