59 (71)
Copyright © Nokia Mobile Phones 2000. All rights reserved.
14. LOCALISATION
Place all the material to be localised in a separate resource file. Identify clearly the strings to be localised.
14.1 Do not hard-code
Make sure that code does not contain hard-coded character constants, numeric constants, screen positions, file
names, or path names that presume a particular language. Code should also contain support for locale-specific
hardware.
Pay careful attention to the differences between various languages and cultures:
• Calendar differences
• Not everybody uses the Gregorian calendar
• There are variations within the same calendar systems (e.g. the day the week begins)
• Date formats
• Time formats
• Address formats
• Phone number formats
• Numbers
• Thousands separator
• Decimal separator
• Currency
• Weights and measures
• Conventions in use of uppercase and lowercase letters
• Comparing and sorting
• Keyboards and other hardware
• Double- and multi-byte enabling
• List separators
14.2 Graphics and audio
Do not hard-code graphics or audio, but aim for a global or, at least, an international design.
Check that your metaphors work in all the required languages. Check that your icons and sounds are culturally
acceptable. Note that different cultures have different taboos; for example human body parts may have unwelcome
connotations in many cultures. Avoid including text in graphics (it might have to be localised).
Notice differences between tones:
• The concept of scale differs across cultures.
• Some tones can give offence to the user.
• Not all tones are suitable for every environment. A loud volume level in Tuupovaara may not seem so loud in
New York City.
14.3 Provide room for text expansion
Do not optimise any user interface elements for the English text lengths. English is a ‘short’ language.
To Next Page
Loading...
