My test lead has asked me to test an English application (desktop/standalone) whether it runs properly on OS used in different countries. The application is NOT internationalized and just uses ASCII english. The test requirement is that a chineese user can also see and use it in english. It has buttons, file-browse dialog and a small text box. Thanks.
I don't suspect this is an interview or exam question, I suspect that not enough people understand internationalization issues well enough. This is not uncommon.
Since not a lot of companies have resources to localize (adapt the software and primarily the user interface) to a particular tartget market or language version, then it should be standard policy that an English language version of an application run on any localized language version OS. This has been a defacto policy at MS for years. (However, we don't necessarily support the reverse; a localized application on an English OS).
The first question I have to ask is why does the application support ASCII only? Unicode is pretty much the standard encoding these days and I don't know of any programming languages that don't support it other than Ruby (although I heard that Ruby does have a way to support Unicode now, but I am not sure).
A common UI issue you will find is that the default font size for East Asian language version is 1 pt. larger than on English and other western language versions. Clipping and truncation is quite common unti dev's learn good UI design and layout practices.
If you decide to support Unicode let me know as I have some tools that can help.
You may also want to check to see how the installer handles installing into a directory that contains localized characters....2 byte and cyrillic chars have historically caused us problems on occasion.
If you're wanting to replicate the customer environment find out what keyboards they used and if non-English keyboards are use you might want to purchase them for key countries in which the product will be sold.
If you have an app that accepts importing of files you may also want to see how it handles files with localized characters.
Reserve a few months every so often and preview retirement throughout your career. You won't regret that a 35 year career was reduced to 34 years to take vacations measured in months in order to remember what a stress and care-free life is all about.
Books and hard work will get you anywhere you want to go.
Hi to all... There are plenty complication with testing a English application on non-English platform. When you are testing your application you need to consider following sectors (depending on your application)
1)- is your application Unicode supported
2)- during installation can you manage to install your application in the folder which contains [non English] characters "Try Russian and Japanese characters"
2.1) during installation enter Unicode character in company name field
3)- if your application communicates with database you need to test if the supplied application DB is Unicode supported
4)- if your application interact with registry or services it is vital to test this sector
5) if your application is web based then use non-English browser
6) if you are testing web based application then fire some Unicode (Russian and Japanese) character in entry fields.
You can do many things and its huge area to cover.
Installing a Eng app on a localized (non-English) platform to a folder that contains cyrillic, or ideographic or kana characters is a cool test, but if it fails the resolution will probably be won't fix. (We tested this scenario all the time, but in cases where it failed (pre-Unicode) it was never formally supported.)
Also, the program files folder on East Asian language platforms is Program Files; it is not translated into a linguistic counterpart as it is in European langauge versions.
If the application is Unicode, Indic scripted languages such as Devanagari or Kannada or Telugu are more interesting since they are characters that are only found in Unicode encoding (i.e. there is no ANSI equivalent). Also there are surrogate pair characters such as the American scripts of Cherokee and Deeret as well as ancient scripts of Phoenician or the cypriot syllabary. (As mentioned in other posts you might look at the Babel tool to help you generate Unicode test data.
And, Ash is absolutely correct when he says "You can do many things and its [a] huge area to cover."