Chapter 5 Internationalization Assessment Matrix
Revision information
Matrix version: 1.0, April 2001
This checklist is in the form of a matrix that enables you to assess the internationalization status of
a
product. Across the x-axis are the categories known as interfaces. Down the y-axis
are the categories known as objects and methods.
Each available box in the matrix should be populated with one of the following color-coded values:
- Compliant - Product fulfills all the requirements defined for this
interface/object combination.
- Partially compliant - Product fulfills some of the requirements
defined
for this interface/object combination. An accompanying explanation in text form should appear after the matrix.
- Non-compliant - Product does not fulfill any of the requirements
defined
for this interface/object combination. Plans for future inclusion should be provided in a roadmap.
- Not applicable - Product does not provide the functionality of this interface/object
combination.
|
|
|
User Interfaces
|
Program Interfaces
|
|
|
|
Command
line
|
Character
|
Graphical
|
Application
Protocols
|
Storage and
Interchange
|
Application
Programming
|
|
1. Translatable product components
|
|
1.1 Translation negotiations, defaults, and selection
|
Partially compliant (6) |
Not applicable |
Partially compliant (1) |
Partially compliant (7) |
Partially compliant (8) |
Compliant |
|
1.2 Textual objects
|
| 1.2.1 Fixed textual objects |
Partially compliant (20) |
Not applicable |
Partially compliant (21) |
Compliant |
Compliant |
Compliant |
| 1.2.2 Messages |
Compliant |
Not applicable |
Compliant |
Partially compliant (9) |
Partially compliant (10) |
Partially compliant (11) |
| 1.2.3 Help systems and documentation |
Not applicable |
Not applicable |
Non-compliant |
Not applicable |
Partially compliant (22) |
Not applicable |
|
1.3 Non-textual objects
|
| 1.3.1 Icons, images, and colors |
Not applicable |
Not applicable |
Non-compliant |
Not applicable |
Not applicable |
Not applicable |
| 1.3.2 GUI objects |
Not applicable |
Not applicable |
Compliant |
Not applicable |
Not applicable |
Not applicable |
| 1.3.3 Sounds |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
| 1.3.4 Other |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
|
2. Cultural formatting and processing
|
|
2.1 Culture negotiations, defaults, and selection
|
Partially compliant (18) |
Not applicable |
Partially compliant (2) |
Compliant |
Compliant |
Compliant |
|
2.2 Abstract objects
|
| 2.2.1 Time, date, and calendar |
Non-compliant |
Not applicable |
Partially compliant (3) |
Compliant |
Compliant |
Compliant |
| 2.2.2 Numeric, monetary, and metric |
Compliant |
Not applicable |
Compliant |
Not applicable |
Not applicable |
Not applicable |
|
2.3 Structured text
|
| 2.3.1 Ordered lists (collation) |
Not applicable |
Not applicable |
Partially compliant (14) |
Not applicable |
Partially compliant (17) |
Not applicable |
| 2.3.2 Personal names, honorifics, and titles |
Compliant |
Not applicable |
Compliant |
Not applicable |
Non-compliant |
Not applicable |
| 2.3.3 Addresses |
Compliant |
Not applicable |
Partially compliant (19) |
Not applicable |
Not applicable |
Not applicable |
| 2.3.4 Other formatting and layout |
Compliant |
Not applicable |
Compliant |
Not applicable |
Not applicable |
Not applicable |
|
2.4 Language processing
|
| 2.4.1 Lexical and grammatical |
Compliant |
Not applicable |
Partially compliant (15) |
Partially compliant (12) |
Not applicable |
Not applicable |
| 2.4.2 Phonology and sound-to-text |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
|
3. Text Foundation and Writing Systems
|
|
3.1 Writing system negotiations, defaults, and selection
|
Non-compliant |
Not applicable |
Partially compliant (4) |
Compliant |
Compliant |
Compliant |
|
3.2 Plain text representation
|
| 3.2.1 Characters (semantics and codespaces) |
Compliant |
Not applicable |
Compliant |
Partially compliant (13) |
Partially compliant (16) |
Not applicable |
| 3.2.2 Strings (encoding methods and transcoding) |
Compliant |
Not applicable |
Compliant |
Not applicable |
Compliant |
Not applicable |
|
3.3 I/O and interchange
|
| 3.3.1 Transfer encoding (8-bit clean) |
Not applicable |
Not applicable |
Not applicable |
Compliant |
Compliant |
Not applicable |
| 3.3.2 Device input (keyboard and input methods) |
Not applicable |
Not applicable |
Partially compliant (5) |
Not applicable |
Not applicable |
Not applicable |
| 3.3.3 Device output (font management, rendering, and output methods) |
Not applicable |
Not applicable |
Compliant |
Not applicable |
Not applicable |
Not applicable |
Explanations for partially compliant areas and notes:
- Translation negotiations in Manager Console are limited by a combination URL, l10n, and file placement
organization. It is somewhat complex for the user to choose a language based on the framework provided.
Administrator
is
totally dependent on central Administrator negotiations.
- Culture negotiations in Manager Console are limited by a combination URL, l10n, and file placement
organization. It is somewhat complex for the user to choose a culture based on the framework provided.
Administrator
is
totally dependent on central Administrator negotiations.
- In order to accommodate calendars in Manager Console other than the Gregorian calendar, customer or
l10n
team
must be able to extensively program in JavaScript. Also, time zone is not determined, GMT is
used but not obvious to user.
- Writing system negotiations in Manager Console are not handled properly. This is a limitation of the
central
Manager Console product. Administrator is totally dependent on central Administrator negotiations.
- Some calls to the Input Method are being made, but implementation
may be incomplete.
- Message Store command line does not determine language of
user. Admin command line goes by the server language. MTA command line is not compliant.
- POP protocol does not allow for language negotiation. Authentication does not determine language. IMAP
is
compliant, as is MTA.
- No language determination for logging (no viewer).
- POP messages not yet externalized, but may be fixed by 5.0
release. MTA is limited by SMTP.
- Log messages hard-coded - depending on whether we put a viewer
mechanism in place at some point, this could become compliant.
- Authentication log messages hard-coded.
- IMAP search, missing some minor charsets.
- Authentication allows UTF-8 passwords but not userids (not
a requirement yet in the industry).
- Administrator is totally dependent on central Directory sorting.
Manager Console is non-compliant.
- Administrator is totally dependent on central Directory search.
Manager Console is non-compliant.
- Character set conversions are weak in the Unicode area for
the MTA. Message store is compliant.
- MTA is constrained by standards, will offer a non-standard
sort option in future release.
- Admin CLI goes by the server time zone.
- Cannot handle postal code before city or region name in the
GUI.
- Admin CLI is not compliant. Message store and MTA are
compliant.
- Manager Console is non-compliant. Administrator is
compliant.
- Online help is stored in a proprietary format - unknown whether
this format can handle all charsets.
Important dependencies:
A. In many cases, the code is relying on Java to handle charset determination and conversion, locale
determination, character parsing, and string parsing, without calling specific methods to accomplish each
step.
B. Manager Console, Administrator, and Admin CLI rely heavily on the central Manager Console, Admin
Console,
and Database servers. The tasks these centralized servers are expected to perform are translation, culture, and
writing
system negotiations, charset conversions, search, and sort.
Location of product roadmap for providing future i18n functionality: None created.
|
|
Print-friendly Version
