Difference between revisions of "Internationalization/feasibility"

(String types and their possible extraction difficulties)
Line 8: Line 8:
  
 
==String types and their possible extraction difficulties==
 
==String types and their possible extraction difficulties==
 +
 +
===Constant String===
 +
Workbench_name: <font color="Blue">STRING is</font> <font color="Green">"EiffelStudio"</font>
  
 
==Important Classes==
 
==Important Classes==

Revision as of 02:09, 1 May 2006

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

Constant String

Workbench_name: STRING is "EiffelStudio"

Important Classes

  • INTERFACE_NAMES: Include all the strings of the ES interface (buttons, labels, shortcuts...)
  • TEXT_FORMATTER: Text formatter for all text output formatting
  • 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"
  • ERROR: Error object sent by the compiler to the workbench. Ancestor class of all error classes (WARNING, SYNTAX_ERROR, INTERRUPT_ERROR, LACE_ERROR,EIFFEL_ERROR...)
  • WIDE_CHARACTER: Unicode characters, with comparison operations [base]