Browse Prior Art Database

A method and system to automatically resolve message truncation in Web page

IP.com Disclosure Number: IPCOM000241347D
Publication Date: 2015-Apr-18
Document File: 9 page(s) / 438K

Publishing Venue

The IP.com Prior Art Database

Abstract

The disclosure is to automatically detect all the truncation issues in a Web application for all the languages, then generate an issue report and provide recommended solutions for developers to solve the issues quickly.

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

Page 01 of 9

A method and system to automatically resolve message truncation in Web page

In product development process, GVT/TVT are testing methods to validate globalization support. GVT validates globalization enablement, whereas TVT validates translation correctness. One key difference between the two is that GVT is performed by a tester who does not speak the national language(s), but TVT has to be performed by a tester who also qualifies as a translator for the language. TVT testers are required to be in country so that they can keep up with the evolution of the language. Because of this, today TVT is performed by a dedicated translation team and is a costly process in terms of funding, effort, and time.

GVT is performed before TVT starts. A poorly performed GVT would have development team busy addressing GVT defects in TVT timeframe and blocking TVT progress. There have been some good work done to improve the efficiency of GVT, in order to help keep TVT focused on translation validation as much as possible. One example is the pseudo translation tool. The tool identifies hard-coded text, concatenated text, and non-ASCII text display issues.

After leveraging the pseudo translation tool in GVT, there are usually two types of remaining issues reported in TVT: (1) translation correctness issue, (2) UI layout issue when displayed with the translated text. The first issue is the focus for TVT. TVT testers correct the translated text during TVT sessions by updating message files. No code change is involved. The second issue, however, typically requires code changes and is fixed by the development team by re-adjusting UI layout. The pseudo translation tool cannot detect the second issue because the tool provides mock translated text which does not represent real translation.

One of the most common UI layout issue is message text truncation. This is caused by different languages having different word lengths. For example, some text are shown well in English, but they are truncated in French or German which has longer words. The first screen shot is an example of text truncation in width, and the second one is an example in height.

1



Page 02 of 9

2



Page 03 of 9

Today we rely on TVT tester to view each layout and catch truncation issues for a language, then the developer would reproduce the issue and fix it. The typical root cause of truncation issue is that the width or height of the text node is set not enough.

The problems with the current approach are:

3



Page 04 of 9

1. Too much manual effort to detect all the truncation issues. It takes someone who speaks the language (eg. a TVT tester) to test with each language and compare with English version to detect.

2. Developers need to repeat the testers' work to reproduce the issue and fix.

3. The same message truncation problem might need several cycles to fix. For example, after fixing a truncation in one language, it could still be truncated in another language.

The disclosure is to find the poten...