Internationalization

Revision as of 07:19, 25 April 2006 by Carlo (Talk | contribs) (→‎M2: May ???: postponed a milestone, introduced new M2)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

1 Overview
2 Milestones
- 2.1 M2: May 5
- 2.2 M3: May ???
3 Team

Overview

"Many [people] would simply love seeing their computer screen showing a lot less of English, and far more of their own language." -- gettext doc

Our aim is not only to provide a framework to ease the translation of Eiffel-written applications, allowing the user to chose his/her preferred language at runtime, but also to let the developer access informations and formats based on users' locale.

Milestones

M2: May 5

feasibility (look at string classes (unicode and not) and how strings are used in eStudio (creation, composition))
file format (compare existing file formats for dictionaries)
tools evaluation (list and compare existing translation tools)

M3: May ???

design:
- file formats (files holding translated strings)
- code parser (extract strings to be translated from source code)
- globality (how to implement, the object should be shared between all modules)
compile a list of basic features to provide (e.g. date/time format, system locale)
collaborate with the Vision2_and_Unicode team