Internationalization/feasibility

From EiffelStudio: an EiffelSoftware project
Jump to navigation Jump to search

Summary

Our task is to find out the possible main difficulties that will be encoutered during both design and implementation of the i18n framework.

Main focuses are:

  • state of the Unicode implementation
  • strings usage in Vision2
  • runtime generated/composed strings with variables

String types and their possible extraction difficulties

Important Classes

  • INTERFACE_NAMES: include all the strings of the ES interface (buttons, labels, shortcuts...)
  • STRING_GENERAL: "Common ancestors to all STRING classes." [base]
    • STRING: [base]
      • UC_STRING: Unicode strings [gobo]
        • UC_UTF8_STRING: Unicode strings with UTF-8 encoding
    • STRING_32: [base]
  • UC_CHARACTER: Unicode characters [gobo]
  • KS_STRING: Portable interface for class STRING [Gobo]
  • cluster: "gobo.kernel.unicode"
  • WIDE_CHARACTER: Unicode characters, with comparison operations [base]