130 e-Business Globalization Solution Design Guide
Figure 16-13 Content translated from English to German by the WebSphere Translation Server with
UDF
Functional competence of machine-translated pages
As we mentioned in 15.5, “Machine translation” on page 107, the IBM WebSphere Translation
Server in our working example is accessed via a translation servlet. This servlet retrieves
data from the source Web page in English and sends it to the WebSphere Translation Server,
which then translates and returns it to the translation servlet. This servlet assembles all
translated data to form a new Web page displayed on the user's browser. Because the
WebSphere Translation Server only translates Web content and does not pass parameters
from one page to another, we need to add additional scripts in the translation servlet to pass
these parameters.
Functional competence testing of machine-translated pages can be viewed as a combination
of linguistic and functional testing. It is used to ensure that:
򐂰 The linguistic service is complete. In other words, within Our Global Travel Shanghai
Demo Web site, any Web page linked from a machine-translated page will also be
translated by the WebSphere Translation Server.
򐂰 The linguistic services do not interfere with the business functions that the project must
provide.
򐂰 No business function is lost or broken on machine-translated pages.
16.5 Browser testing
Browser testing involves tasks users execute within a browser. Since people in different
locales can have different browser preferences, testing multilingual applications covers more
Chapter 16. Testing 131
browser activities than testing monolingual ones. The following are some of the more
common concerns for browser testing:
򐂰 Browser-dependent user operations. For example, what will happen if the Back, Forward,
or Reset buttons are selected during the transaction cycle?
򐂰 Cookie-related activities, such as what will happen if the user enables or disables the
cookie settings.
򐂰 Vendor-specific performance. For example, whether the application can survive under
both Internet Explorer and Netscape Navigator.
򐂰 Artwork-related problems. For example, different fonts might display different glyphs
against the same code entry, so that the Web page should be designed in such a way that
the content in all supported languages can be displayed neatly and professionally.
Our working example requires that both IE and Netscape be supported. Though there are few
differences between these two browsers, those that exist can still adversely affect the
application to a certain extent. For example, when the user locale is ar_EG, Internet Explorer
can display numbers in Hindi while Netscape cannot. For this reason, Arabic numerals are
used when the user locale is ar_EG so that both IE and Netscape can display numbers in the
proper way. In this case, browser testing can help developers get a better understanding of
browsers and thus make the application fit into the display capabilities of both supported
browsers.
After browser testing, we see that Our Global Travel Shanghai Demo Web site can be
displayed with the best quality on Microsoft Internet Explorer 5.5 or higher and Netscape 6.2
or higher, both using a Windows 2000 Server.
Browser testing should also check the artwork. For instance, in our working example, the
original column width of some tables is just enough to contain the data in English in one line,
but not to contain that in languages whose average word length is longer than that of English.
During browser testing, German and Spanish testers found that some tables looked sloppy
because they were not wide enough.
Figure 16-14 An example of a sloppy table
As a result, the artwork designer re-designed these tables so that they can now neatly
accommodate Web content in all supported languages.

Get e-business Globalization Solution Design Guide: Getting Started now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.