|
|
Yes
|
No
|
NA
|
|
|
|
1
|
Is there any need for displaying predefined data and objects for different languages? (eg: labels, button text, images, title etc..)
|
|
|
|
|
|
|
2
|
Are the resource files being provided by the customer?
|
|
|
|
|
|
|
3
|
Does the calendar controls display the Gregorian calendar always, irrespective of the language in which it is shown? (e.g.: Some customers would want an Arabic calendar for Arabic culture)
.NET Framework DateTime structure(members such as the DateTime.Day property, the DateTime.Month property, the DateTime.Year property, and the DateTime.AddDays method) is based on the Gregorian calendar. This is not changed by any change in culture settings.
To handle native calendar types, the .NET Framework provides the Calendar class as well as the following Calendar implementations: GregorianCalendar, HebrewCalendar, HijriCalendar, JapaneseCalendar, JulianCalendar, KoreanCalendar, TaiwanCalendar, and ThaiBuddhistCalendar. Other things you can use include are the CultureInfo class, which has a CultureInfo.Calendar property that specifies a culture's default calendar. The CultureInfo.OptionalCalendars property specifies the optional calendars supported by a culture.
|
|
|
|
|
|
|
4
|
Has the time format been identified?
It can be either a 12 hour or 24 hour clock. The characters used to separate hours, minutes and seconds a\may be different for different cultures.
|
|
|
|
|
|
|
5
|
Are date/time values captured as local time zone values?
It may be a requirement to store the UTC equivalent of date-time values from entered from different cultures. Use the DateTime.ToUniversalTime method to convert a local DateTime to its UTC equivalent. To parse a date/time string and convert it to a UTC DateTime, use the DateTimeStyles enumeration AdjustToUniversal value with either the DateTime.Parse or DateTime.ParseExact method.
|
|
|
|
|
|
|
6
|
Is there any requirements for alternate sort orders?
Some cultures support more than one sort order. For example, the culture "zh-CN" (Chinese in China) supports a sort by pronunciation (default) and a sort by stroke count.
To specify the alternate sort order, create a CultureInfo object using the LCID for the alternate sort order. Then, obtain a CompareInfo object to use in string comparisons from CultureInfo.CompareInfo. As an alternative, you can create a CompareInfo object directly by using the CompareInfo.GetCompareInfo method (Int32), specifying the LCID for the alternate sort order.
|
|
|
|
|
|
|
7
|
Has the paper size been identified for each culture?
The paper sizes in the United States and Canada (such as letter, legal, and so on) do not satisfy the needs of all users in the world market. For example, most countries in Europe and Asia use a slightly larger standard known as "A4" (297 x 210 mm) that is slightly longer and narrower than the U.S. letter size (279 x 216 mm). Thus if your application needs to print, you should allow the default paper size to be configurable.
|
|
|
|
|
|
|
8
|
Has the Unit of measurement been identified for each culture?
There are different units of measurement for things like Length, Weight, Area, Volume, Temperature, Paper size, Angle notation, etc. There can be different requirements where conversion from one unit to another is required. For example, in one scenario, the end users may be allowed to view/enter data in their local unit of measurement; but it will be stored in a common UOM.
|
|
|
|
|
|
|
9
|
How is the data entered and stored into the system? Is it in local language?
For storing multi-lingual data, use uni-code data types.
|
|
|
|
|
|
|
10
|
Are the numbers and figures entered into the system always in English digits?
E.g.: Languages like Hindi have its own number system.
|
|
|
|
|
|
|
11
|
Do the users need localized thousand separators and decimal separators for the numbers and figures displayed on the system?
E.g.: In Polish, the thousand separator is a space and the decimal separator is a comma. The number “2,500.70” is written in Poland as “2 500,70”
|
|
|
|
|
|
|
12
|
For editable numeric fields, are the users allowed to enter thousand separators for the numbers and figures entered on the system?
E.g.: In Polish, the thousand separator is a space and the decimal separator is a comma. The number “2,500.70” is written in Poland as “2 500,70”. If the user is allowed to enter the thousand separators, appropriate validations needs to be considered.
|
|
|
|
|
|
|
13
|
Are the dates displayed and entered in the system in local format?
|
|
|
|
|
|
|
14
|
Are the reports to be printed in local language?
|
|
|
|
|
|
|
15
|
Are all the regional cultures/languages identified which are to be supported by the application?
|
|
|
|
|
|
|
16
|
Is there any special culture where the layout/orientation of the resource is different from other cultures? (E.g.: Arabic language).
|
|
|
|
|
|
|
17
|
Is the system testing of all cultures/languages (except the base language) being done by the customer ?
(Have to consider the availability of human resources for all the required languages and the effort.)
|
|
|
|
|
|
|
18
|
Is there any need for custom cultures? (e.g.: English for India)
|
|
|
|
|
|
|
19
|
Is there integration with other applications where multilingual could be a challenge?
|
|
|
|
|
|