Difference between revisions of "Internationalization"

m (new account for Hong)
(removed old milestones, added status)
 
(2 intermediate revisions by the same user not shown)
Line 26: Line 26:
 
=== Specific goals of the semester project ===
 
=== Specific goals of the semester project ===
  
−
''to be completed''
+
The new i18n library should provide translation as well as date, time, value and currency formatting.
 +
It should run on at least windows (with and without .NET) and linux.
  
−
=Milestones=
+
=Status=
  
−
''add milestones of semesterproject''
+
As of 16 October 2006 we have all features working and almost all tested.
−
 
+
Some difficulty exists with the windows installation procedure. The linux version works without problems.
−
==Mx: ??? ==
+
−
* Write a summary of how [[Internationalization/posix_locale|POSIX locale]] information is stored
+
−
* Write a summary of how [[Internationalization/nls_locale|NLS (Windows) locale]] infomation is stored
+
−
* Write a summary of how [[Internationalization/dotnet_locale|.NET locale]] information is stored
+
−
* Write a small summary of date and time classes in EiffelBase
+
−
* Examine the .ts file format, notably plural form handling
+
−
* Examine the .xliff file format, notably plural form handling (we did some of this already)
+
−
* Enter classes & features into EiffelStudio so we have a starting point and a BON diagram
+
−
* Sit down and think about the current class names. Some of them need improving.
+
−
 
+
−
==M5: July ?? ==
+
−
* Refactoring of whole library
+
−
* Use our library for EiffelStudio
+
−
* Clean up Wiki and improve Developer manual
+
−
* Add support for other aspects of localisation - dates, number format etc. ''(possibly we can defer this a bit)''
+
−
** Compile a [[Internationalization/l10n_features | list of basic features]] to provide (e.g. date/time format, system locale) ''(deferred from M3)''
+
  
 
= Documentation =
 
= Documentation =
  
−
* [[Internationalization/user_manual|User manual]]: how to use the i18n library
+
* [[Internationalization/User_guide|User guide]]: how to use the i18n library
−
* [[Internationalization/developer_manual|Developer manual]]: developer manual for the i18n library
+
* [[Internationalization/Developer_guide|Developer guide]]: developer manual for the i18n library
 
* [[Internationalization/obstacles|Obstacles]]: setbacks we have encountered
 
* [[Internationalization/obstacles|Obstacles]]: setbacks we have encountered
  

Latest revision as of 17:07, 17 October 2006

Our Eiffel Tower of Babylon

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 information and formats based on users' locale.

Brief history

Orginally the internationalisation (i18n) project was started as a required project for an ETH Software Architecture course. The result was less then perfect; pages referring to this first version have been given an 'SA' prefix. Some members of this SA project team decided to rewrite the library as a semester project. Pages on the wiki not prefixed with 'SA' are either applicable to both or to the semester project.

What is internationalisation?

The first thing that comes to mind is translation. But internationalisation isn't restricted to enabling translation: it includes making it possible to localise notations (time, date, numbers), measures, paper size, and much more.

What should we achieve?

  • Applications should be able to load localized strings at runtime and be provided with localized format strings (e.g date format).
  • Developers can use tools that automagically extract strings from source code and can try to get them translated in a file to distribute along with the application.
  • Users will still be unhappy and get depressed but in their own language, which we can all agree is a significant step forward.

Specific goals of the semester project

The new i18n library should provide translation as well as date, time, value and currency formatting. It should run on at least windows (with and without .NET) and linux.

Status

As of 16 October 2006 we have all features working and almost all tested. Some difficulty exists with the windows installation procedure. The linux version works without problems.

Documentation

Relevant Links

Introduction to i18n

What other people have done

internationalisation with QT

howto for internationalisation of KDE programs

another KDE howto (doesn't Gnome do any internationalisation?)

Team

Everyone interested in this project is welcome to join our mailinglist es-i18n@origo.ethz.ch

Semester project


Old SA project team

Retrieved from "https://dev.eiffel.com/index.php?title=Internationalization&oldid=5271"