EiffelStudio: an EiffelSoftware project - User contributions [en]

Internationalization/translation

2006-11-23T07:24:54Z

Carlo: removed (now broken) link to translation site

[[Category:Internationalization]]

EiffelStudio contains many sectorial terms, which may have a corresponding expression in other languages but their meaning may not be clear enough to the end user.

This page is intended for discussion on terms difficult to translate.

= Translation =
== A ==
Ancestor
it: Antenato
fr: Ancêtre
zh_CN: 父类

Anchor

assignees

Assigners

== B ==
== C ==
Callers
it: chiamanti
fr: ''Appeleur'' is a possiblity but it sounds ugly and is possibly not common usage
zh_CN: 调用方

Cluster Legend
== D ==
== E ==
Execution Profile Generation
zh_CN:

== F ==
Finalize
it: finalizza -> finalized == finalizzato
Freeze
== G ==
== H ==
Heir
it: Erede => Heirs: eredi
zh_CN: 后裔
== I ==
Indexing clause
zh_CN:

== J ==
== K ==
== L ==
== M ==
Midpoint
zh_CN:

Metric
zh_CN:

== N ==
== O ==
Overrides
zh_CN:

== P ==
Parent
it: genitore
zh_CN: 父类

Put Handle Left
zh_CN:

Profile
zh_CN: 评测

Pick and Drop
zh_CN:

== Q ==
== R ==
== S ==
Step Out

split area
zh_CN:

Suppliers
it: fornitori

== T ==
Toggle visibility
it: Mostra/nascondi ''[used]''
== U ==
== V ==
== W ==
Watch
it: osserva
zh_CN: 观察

Wizard
it: Procedura guidata ''[used]'', wizard ''[used in menu]''
zh_CN: 向导
== X ==
== Y ==
== Z ==
== Following words are left unchanged ==
* it: file, inheritance, overflow, stack, feature, routine, cluster, deferred, client, supplier, signature

EiffelStudio Internationalization

2006-11-09T12:04:58Z

Carlo: typo

[[Category:EiffelStudio]]
[[Category:Internationalization]]
== Overview ==
Since i18n have been mostly implemented in Eiffel, Eiffel Studio is coming into the new era of [[internationalization]]. The goal of i18n integration is to provide multiple language support in Eiffel Studio and let users switch languages of the interface easily at runtime.

== Steps to integrate i18n ==
=== Non-editor part ===
The first step concentrates on the interface of Eiffel Studio. All buttons, labels, tool tips and grids that are directly used by Eiffel Studio project.
# Collect all static interface strings in the system., including some context depend strings.
## This is not necessary, but doing this give us better management and code quality. Only INTERFACE_NAMES knows i18n.
## Change all types in INTERFACE_NAMES to be STRING_GENERAL. Caller should be adapted correspondingly.
## Rewrite bodies of those strings using i18n translation routines, STRING_32 instances are actually produced.
# Build language menus to switch language.
## Make interface classes locale observers so that all tools know when interface names should be reread.
# Solve the problems in vision2.
## In Chinese, menu chars are conventionally parenthesized and under scored following the menu text.
## Handle "&" as both char and wchar for menu items.
## Fix "tab" issue for menu items.
# Integrate i18n .po generation tool. It has been done in i18n branch.
# using .po generation tool integrated ec to compile an ec in which interface names have been adapted.
# Use .po generation tool to generate .pot file. The .po generation tool generally extracts strings that are taken as parameters of `translated' and `translated_plural' and produce .pot file.
# Duplicate .pot file to .po files with names of locale ids. Each .po file represents a locale. i18n library read .mo files with correct names of id. Though .po files are not necessary to have names of locale id, .mo files are one-to-one produced from .po files. So using locale ids as names of .po files is reasonable.
# Translators using .po editor open .po files and translate interface names to all kinds of languages.
# Generate .mo files using .mo generation script.

=== Editor part ===
# This step might be more complicated. And will be done later after the first step. Probably after 6.0 release. This step concentrates on extending the editor library to accept wide characters. Internationalization of any output directed to the editor is done in the step. Many existing tools might be affected, search tool, formatting tools etc.
# Encoding conversion facility is needed.

== File structure ==
All files are stored in %EIFFEL_SRC%\Delivery\studio\lang

%EIFFEL_SRC%\Delivery\studio\lang\script
<pre>
Place where scripts for generating .mo files are put. The scripts are invoked when building a delivery.
</pre>
%EIFFEL_SRC%\Delivery\studio\lang\mo_files
<pre>
Place to put .mo files. Those files are actually used at runtime.
Only .mo files need to be included in a delivery.
</pre>
%EIFFEL_SRC%\Delivery\studio\lang\po_files
<pre>
Place to put .pot file and .po files.
</pre>

== Maintenance ==
* .pot file is PO template file which is generated by .po generation tool that will be integrated in Eiffel Studio. In my point, .pot file is simply untranslated file with only source entries and blank target entries.
* .po files are the files translators actually work on. Whenever translators get a new version of .pot file, they should merge .pot file and the .po file they are working on. When merging, tools like [http://www.poedit.org poEdit] give lists of new strings and obsolete strings. And in the full list new strings and fuzzy strings are marked in different colors by poEdit.
* Fuzzy strings are applied when merging. msgmerge of [http://www.gnu.org/software/gettext Gettext] make slightly changed strings fuzzy. When the checking of fuzzy strings is done, translators should remove fuzzy marks.
* Obsolete strings are commented out at the end of .po files when merging. Those comments can be removed at anytime if we wish.
* When the translation or modification is done, translators only need to commit .po file(s) that they are working on.
* New .po file can be added directly in %EIFFEL_SRC%\Delivery\studio\lang\po_files. Eiffel Studio should have the ability to detect at runtime what languages are available.

Internationalization

2006-07-01T16:39:31Z

Carlo: /* M3: June 13 */ changed wiki-link

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/l10n_features|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June 28 ==
* internationalization of EiffelStudio: surround strings with our functions
* [[Internationalization/translation|translation]] of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system
* create a function to detect current environment language and settings (aka [[Internationalization/locale|locale]])

==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)''

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programs with translation facilities.

= Documentation =

* [[Internationalization/requirements_specification|Requirements specification]]
* [[Internationalization/developer_manual|Developer manual]]
* [[Internationalization/obstacles|Obstacles]]: why can't achieve all of our goals

= l10n: completed and on the work =

{| border="0" cellspacing="3" cellpadding="5" align="center"
!'''Language'''
!'''Status'''
|-
|Arabic
|Active
|-
|Chinese
|Active
|-
|Italian
|Active
|-
|Rhaeto-Romanic
|Active - Ready for use
|}

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-07-01T16:37:57Z

Carlo: /* M5: July ?? */ deferred from M3

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June 28 ==
* internationalization of EiffelStudio: surround strings with our functions
* [[Internationalization/translation|translation]] of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system
* create a function to detect current environment language and settings (aka [[Internationalization/locale|locale]])

==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)''

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programs with translation facilities.

= Documentation =

* [[Internationalization/requirements_specification|Requirements specification]]
* [[Internationalization/developer_manual|Developer manual]]
* [[Internationalization/obstacles|Obstacles]]: why can't achieve all of our goals

= l10n: completed and on the work =

{| border="0" cellspacing="3" cellpadding="5" align="center"
!'''Language'''
!'''Status'''
|-
|Arabic
|Active
|-
|Chinese
|Active
|-
|Italian
|Active
|-
|Rhaeto-Romanic
|Active - Ready for use
|}

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization/obstacles

2006-06-29T14:30:58Z

Carlo: added function arguments and case conversion problems in eStudio

Problems we encountered during implementation

* Unicode (UTF-8) support was not fully implemented (e.g. for gtk)
* Facilities to write and read STRING_32 to/from files were not present

Difficulties to complete the translation of EiffelStudio:
* Many strings are hard-coded anywhere inside EiffelStudio, making the translation difficult
* All the functions taking strings as arguments expect a STRING, where they should expect a STRING_GENERAL, and they return a STRING which may not be applicable in every case. A STRING_32 can also represent the same content of a STRING_8, thus it should be preferred.
* It seems that to_uppercase and to_lowercase procedures are not defined for STRING_32 and are used in teh studio, these should have been implemented by the vision project and may be buggy.

Internationalization/obstacles

2006-06-27T23:15:27Z

Carlo:

Internationalization

2006-06-27T23:02:14Z

Carlo: /* M4: June ??? */

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June 28 ==
* internationalization of EiffelStudio: surround strings with our functions
* [[Internationalization/translation|translation]] of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system
* create a function to detect current environment language and settings (aka [[Internationalization/locale|locale]])

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programs with translation facilities.

= Documentation =

* [[Internationalization/requirements_specification|Requirements specification]]
* [[Internationalization/developer_manual|Developer manual]]
* [[Internationalization/obstacles|Obstacles]]: why can't achieve all of our goals

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Talk:Internationalization/locale

2006-06-22T21:40:28Z

Carlo: formatting

At present we are using [http://en.wikipedia.org/wiki/ISO_639 ISO 639-1] to identify the languages.
[http://www.unicode.org/onlinedat/languages.html Here] is a list of correspondences between different coding conventions.

In GNU informations on current locale are stored in [http://man.splitbrain.org/locale(1) LC_* environment variables]. [http://man.splitbrain.org/locale(5) This] may explain how a locale is defined.

(these notes should be added to the article) --[[User:Carlo|Carlo]] 00:30, 19 June 2006 (CEST)

Feel free to add them to the article.

About the conversion that we need to do: do we have to build an entire structure and copy all of these win codes and corresponding ISO codes or we simply add a couple of them (like english, italian, german, french and chinese)?

About the codes: I don't think it's sufficient to take only the language part... especially because there are languages that uses different scripts (info found on SortID for windows) and regional differences in the format (in the end we are not only translating eiffel... the objective is i18n and in this there are numeric formats and date formats too)

just to be clear:
"it" is not sufficient, we need "it_ch" to have complete information

--[[User:Cconti|Cconti]]

: My suggestion is to design a scalable structure, insert the codes and informations that we need now and let the opportunity to easily add other later on. (e.g. an hash_table of objects, each one representing a code with the related properties)

: Sure we need more than just the language code, but for now it's enough to extract it (split language/nation where both available, codesets). On Linux locale (source) data are found at /usr/share/i18n/locales/ but parsing such information is, at present, out of our concern. --[[User:Carlo|Carlo]] 23:23, 22 June 2006 (CEST)

Talk:Internationalization/locale

2006-06-22T21:23:18Z

Carlo:

At present we are using [http://en.wikipedia.org/wiki/ISO_639 ISO 639-1] to identify the languages.
[http://www.unicode.org/onlinedat/languages.html Here] is a list of correspondences between different coding conventions.

In GNU informations on current locale are stored in [http://man.splitbrain.org/locale(1) LC_* environment variables]. [http://man.splitbrain.org/locale(5) This] may explain how a locale is defined.

(these notes should be added to the article) --[[User:Carlo|Carlo]] 00:30, 19 June 2006 (CEST)

Feel free to add them to the article.

About the conversion that we need to do: do we have to build an entire structure and copy all of these win codes and corresponding ISO codes or we simply add a couple of them (like english, italian, german, french and chinese)?

About the codes: I don't think it's sufficient to take only the language part... especially because there are languages that uses different scripts (info found on SortID for windows) and regional differences in the format (in the end we are not only translating eiffel... the objective is i18n and in this there are numeric formats and date formats too)

just to be clear:
"it" is not sufficient, we need "it_ch" to have complete information

--[[User:Cconti|Cconti]]

My suggestion is to design a scalable structure, insert the codes and informations that we need now and let the opportunity to easily add other later on. (e.g. an hash_table of objects, each one representing a code with the related properties)

Sure we need more than just the language code, but for now it's enough to extract it (split language/nation where both available, codesets). On Linux locale (source) data are found at /usr/share/i18n/locales/ but parsing such information is, at present, out of our concern. --[[User:Carlo|Carlo]] 23:23, 22 June 2006 (CEST)

Talk:Internationalization/locale

2006-06-18T22:31:25Z

Carlo:

Talk:Internationalization/locale

2006-06-18T22:30:36Z

Carlo:

At present we are using [http://en.wikipedia.org/wiki/ISO_639 ISO 639] to identify the languages.
[http://www.unicode.org/onlinedat/languages.html Here] is a list of correspondences between different coding conventions.

In GNU informations on current locale are stored in [http://man.splitbrain.org/locale(1) LC_* environment variables]. [http://man.splitbrain.org/locale(5) This] may explain how a locale is defined.

(these notes should be added to the article) --[[User:Carlo|Carlo]] 00:30, 19 June 2006 (CEST)

User talk:Trosim

2006-06-17T10:20:56Z

Carlo: i18n user manual

Ciao Martino, come continuiamo con il mo_parser?[[User:Etienner|'''E''''''T''''''N''']] [[User talk:Etienner|'''talk''']]
:Direi che per prima cosa vale la pena decidere come vogliamo salvare il tutto in Eiffel; se possibile in modo incrementale, in seguito creiamo le classi che ci servono e poi il parser vero e proprio. Qualche osservazione/idea? [[User:Trosim|Trosim]]
::Yes, observation #1: English please :) observation #2: How we store the strings in memory is, I think, a seperate matter. The parser should of course know about it but I think you can at least get started on designing it with just the .mo format. [[User:Leo|Leo]] 18:20, 8 May 2006 (CEST)
:::*cough* observation #3: this is User_talk:Trosim and _not_ Talk:Internationalization/mo_parser. Carry on in italian then ;) [[User:Leo|Leo]] 18:22, 8 May 2006 (CEST)

== i18n user manual ==

In that case (your entry on our homepage) the manual is related to EiffelStudio, not to the library. Moreover the feature should be simple enough not to need a manual... A "translator manual" may be of better use --[[User:Carlo|Carlo]] 12:20, 17 June 2006 (CEST)

Internationalization

2006-06-16T22:44:12Z

Carlo: /* Documentation */ manual is for developers

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June ??? ==
* internationalization of EiffelStudio: surround strings with our functions
* [[Internationalization/translation|translation]] of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

= Documentation =

* [[Internationalization/requirements_specification|Requirements specification]]
* [[Internationalization/developer_manual|Developer manual]]
* [[Internationalization/obstacles|Obstacles]]: why can't achieve all of our goals

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Talk:Internationalization/translation function

2006-06-10T08:32:51Z

Carlo: Templates

== Globality ==
Content moved to [[Internationalization/class_structure|class structure]]. [[User:Trosim|Trosim]] 12:29, 24 May 2006 (CEST)

==Propose==

As I said, this is only a suggestion, I have syntactical and semantic criticism (tuple, tuple item types, names, plural form,...), too. But I made it to give our group a boost.
So '''please''' make some changes and/or criticize my solution!! [[User:Etienner|'''E''''''T''''''N''']] [[User talk:Etienner|'''talk''']] 09:00, 25 May 2006 (CEST)

Use STRING_32 instead of STRING for output. Use STRING_GENERAL whenever it is possible on input.
--[[User:Manus|manus]] 16:23, 25 May 2006 (CEST)

== Templates ==

A new class (I18N_TEMPLATE_FORMATTER) has been writte by Trosim, but it would be nice to use existing ones. It happens that ST_FORMATTER (part of Gobo) is explicitly excluded from the library, somebody knows the reason?

At present when translating a template you must already give the variables that must be substituted. In many situations it is useful to separate translation from variable substitution. This is what I'm working on.
--[[User:Carlo|Carlo]] 10:32, 10 June 2006 (CEST)

Internationalization/translation

2006-06-09T11:57:29Z

Carlo: add 'finalize', 'watch'

[[Category:Internationalization]]

The translation of EiffelStudio is going on [http://slhk.ath.cx/projects/estudio/ here].

EiffelStudio contains many sectorial terms, wich may have a corresponding expression in other languages but their meaning may not be clear enough to the end user.

This page is intended for discussion on terms difficult to translate.

----

Ancestor
* it: Antenato

Callers
* it: chiamanti

Finalize
* it: finalizza -> finalized == finalizzato

Parent

Put Handle Left

Step Out

Suppliers
* it: contribuenti

Toggle visibility
* it: Mostra/nascondi ''[used]''

Watch
* it: osserva

Wizard
* it: Procedura guidata ''[used]'', wizard ''[used in menu]''

----
Following words are left unchanged
* it: file, inheritance, overflow, stack, feature, routine

Internationalization/translation

2006-06-09T11:47:35Z

Carlo: description and first words

[[Category:Internationalization]]

The translation of EiffelStudio is going on [http://slhk.ath.cx/projects/estudio/ here].

EiffelStudio contains many sectorial terms, wich may have a corresponding expression in other languages but their meaning may not be clear enough to the end user.

This page is intended for discussion on terms difficult to translate.

----

Ancestor

Callers
* it: chiamanti

Parent

Put Handle Left

Step Out

Suppliers
* it: contribuenti

Toggle visibility
* it: Mostra/nascondi ''[used]''

Wizard
* it: Procedura guidata ''[used]'', wizard ''[used in menu]''

----
Following words are left unchanged
* it: file, inheritance, overflow, stack

Internationalization

2006-06-09T11:25:29Z

Carlo: /* M4: June ??? */ link to translation discussion

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June ??? ==
* internationalization of EiffelStudio: surround strings with our functions
* [[Internationalization/translation|translation]] of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-06-09T11:23:12Z

Carlo: /* M3: June 13 */ fix split

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June ??? ==
* internationalization of EiffelStudio: surround strings with our functions
* translation of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-06-08T10:37:11Z

Carlo: /* M4: June ??? */

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

==Who should do the achieving?==
It is clear that our [[User:Carlo|Glorious Leader]] should be credited with any achieving. However he will have to delegate things somewhat, as he is is not [http://en.wikipedia.org/wiki/Aleksei_Grigorievich_Stakhanov Stakhanov].
We can probably divide the project into the following parts, modulo preliminary research:

''This should be probably be completed after we have got past M1''

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June 13 ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .po file ''(Leo)'' ''[deferred]''
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

==M4: June ??? ==
* internationalization of EiffelStudio: surround strings with our functions
* translation of EiffelStudio in some languages, for demo purposes (Italian, German, Chinese, ...) (see [http://slhk.ath.cx/projects/estudio/ pootle])
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .pot file ''(Leo)''
* language selection: add an entry in the preferences system

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-06-07T19:29:02Z

Carlo: /* M3: June ??? */ reorganized

[[Category:Projects]]
[[Category:Internationalization]]
[[Image:ebabylon.png|right|frame| 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.

==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.

==Who should do the achieving?==
It is clear that our [[User:Carlo|Glorious Leader]] should be credited with any achieving. However he will have to delegate things somewhat, as he is is not [http://en.wikipedia.org/wiki/Aleksei_Grigorievich_Stakhanov Stakhanov].
We can probably divide the project into the following parts, modulo preliminary research:

''This should be probably be completed after we have got past M1''

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: June ??? ==
:At good point:
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)'' ''[done]''
* [[Internationalization/mo parser|mo parser]]: extract translated strings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

:What need work:
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .po file
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings ''(Martino)''
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
** find out how to use plurals (see [[Internationalization/plural_forms|plural forms]])
* Test unicode support in Vision2. [See test application in the [https://eiffelsoftware.origo.ethz.ch/svn/es/branches/soft-arch/Src/library/i18n/example/ SVN repository]]

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Internationalization/translation function

2006-06-01T14:37:17Z

Carlo: counting lists

[[Category:Projects]]
[[Category:Internationalization]]

==Introduction==

The problem for the translation is that we need a way to translate three different types of string:

* normal strings
<code>[eiffel,N] "A normal string"</code>
* composed string
<code>[eiffel,N] "A string composed by "+count.out+" strings, like this or "+a_string+"%N"</code>
* strings with plural form
<code>[eiffel,N]
if n=1 then
Result := "a string"
else
Result := "strings"
end
</code>

Another problem is that not all languages have the same rules for plural forms, see below and [[internationalization/plural_forms|here]] for more details.

==Possible solution==

I [[Talk:Internationalization/translation_function|'''propose''']] a solution, with four functions (I've got little fantasy for the function names):

<code>[eiffel,N]
i18n (a_string : STRING) : STRING
--Function for the translation of normal strings

i18n_pl (strings : TUPLE[STRING]; form : INTEGER) : STRING
--Function for the translation of normal strings
-- with plural form

i18n_comp (a_string : STRING; args : TUPLE) : STRING
--Function for the translation of composit strings

i18n_comp_pl (strings : TUPLE[STRING]; args : TUPLE; form : INTEGER) : STRING
--Function for the translation of composit
-- strings with plural forms
</code>

With this solution, the programmer should write composit strings as (or in a similar way) he would do it for the C ''printf'' function. The composit string above would be somthing like this:

<code>[eiffel,N] i18n_comp("A string composed by %a1 strings, like this or %a2%N", [count, a_string])
</code>

where ''%a1'' is the place where the first string in the argument tuple (here ''count'') has to go. I've [[Talk:Internationalization/translation_function|'''choosen''']] that the items in the argument tuple are of type ANY, to insert them in the string we have to apply the functon ''out'' to all items.

===An example===

A complete example of how it could work.

----
Piece of code without internationalization:

<code>[eiffel,N]

[...]
if n = 1
io.put_string("Remove file "+file_name.out+"?%N")
else
io.put_string ("Delete following files?"+list.out+" there are "
+list.count.out+"files%N")
end
[...]

</code>

----

Piece of code with internationalization:

<code>[eiffel,N]

[...]
io.put_string(i18n_comp_pl(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n))
[...]
</code>

the content of the PO file would be:

#: A comment
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

You might ask yourself, ''why a function for all the pluralforms''?

The number of plural forms differ between languages. This is somewhat surprising for those who only have experiences with Romanic and Germanic languages since here the number is the same (there are two).
But other language families have only one form or many forms. For example,

In Polish the translation of file is plik, and the plural forms are:

:2,3,4 pliki
:5-21 pliko'w
:22-24 pliki
:25-31 pliko'w
:and so on...

for more information about this topic go [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 here]

==Additional things==

A nice thing whe could do, when parsing the source code of a program to internationalize, is to recognize comments about the string.
For example:

<code>[eiffel,N]

[...]
io.put_string(i18n_comp_pl(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], list_count))
--A comment of the author
[...]
</code>

woud then look like this in the PO file:

#. A comment of the author
#. Function name, class name, file path
#. %a1 = file_name
#. %a2 = list
#. %a3 = list_count
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

Internationalization/translation function

2006-06-01T14:34:59Z

Carlo: /* Additional things */

[[Category:Projects]]
[[Category:Internationalization]]

==Introduction==

The problem for the translation is that we need a way to translate three different types of string:

* normal strings
<code>[eiffel,N] "A normal string"</code>
* composed string
<code>[eiffel,N] "A string composed by "+count.out+" strings, like this or "+a_string+"%N"</code>
* strings with plural form
<code>[eiffel,N]
if n=1 then
Result := "a string"
else
Result := "strings"
end
</code>

Another problem is that not all languages have the same rules for plural forms, see below and [[internationalization/plural_forms|here]] for more details.

==Possible solution==

I [[Talk:Internationalization/translation_function|'''propose''']] a solution, with four functions (I've got little fantasy for the function names):

<code>[eiffel,N]
i18n (a_string : STRING) : STRING
--Function for the translation of normal strings

i18n_pl (strings : TUPLE[STRING]; form : INTEGER) : STRING
--Function for the translation of normal strings
-- with plural form

i18n_comp (a_string : STRING; args : TUPLE) : STRING
--Function for the translation of composit strings

i18n_comp_pl (strings : TUPLE[STRING]; args : TUPLE; form : INTEGER) : STRING
--Function for the translation of composit
-- strings with plural forms
</code>

With this solution, the programmer should write composit strings as (or in a similar way) he would do it for the C ''printf'' function. The composit string above would be somthing like this:

<code>[eiffel,N] i18n_comp("A string composed by %a1 strings, like this or %a2%N", [count, a_string])
</code>

where ''%a1'' is the place where the first string in the argument tuple (here ''count'') has to go. I've [[Talk:Internationalization/translation_function|'''choosen''']] that the items in the argument tuple are of type ANY, to insert them in the string we have to apply the functon ''out'' to all items.

===An example===

A complete example of how it could work.

----
Piece of code without internationalization:

<code>[eiffel,N]

[...]
if n = 1
io.put_string("Remove file "+file_name.out+"?%N")
else
io.put_string ("Delete following files?"+list.out+" there are "
+list.count.out+"files%N")
end
[...]

</code>

----

Piece of code with internationalization:

<code>[eiffel,N]

[...]
io.put_string(i18n_comp_pl(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n))
[...]
</code>

the content of the PO file would be:

#: A comment
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

You might ask yourself, ''why a function for all the pluralforms''?

The number of plural forms differ between languages. This is somewhat surprising for those who only have experiences with Romanic and Germanic languages since here the number is the same (there are two).
But other language families have only one form or many forms. For example,

In Polish the translation of file is plik, and the plural forms are:

:2,3,4 pliki
:5-21 pliko'w
:22-24 pliki
:25-31 pliko'w
:and so on...

for more information about this topic go [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 here]

==Additional things==

A nice thing whe could do, when parsing the source code of a program to internationalize, is to recognize comments about the string.
For example:

<code>[eiffel,N]

[...]
io.put_string(i18n_comp_pl(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n))
--A comment of the author
[...]
</code>

woud then look like this in the PO file:

#. A comment of the author
#. Function name, class name, file path
#. %a1 = file_name
#. %a2 = list
#. %a3 = list_count
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

Internationalization/translation function

2006-06-01T14:34:29Z

Carlo: small but important detail

[[Category:Projects]]
[[Category:Internationalization]]

==Introduction==

The problem for the translation is that we need a way to translate three different types of string:

* normal strings
<code>[eiffel,N] "A normal string"</code>
* composed string
<code>[eiffel,N] "A string composed by "+count.out+" strings, like this or "+a_string+"%N"</code>
* strings with plural form
<code>[eiffel,N]
if n=1 then
Result := "a string"
else
Result := "strings"
end
</code>

Another problem is that not all languages have the same rules for plural forms, see below and [[internationalization/plural_forms|here]] for more details.

==Possible solution==

I [[Talk:Internationalization/translation_function|'''propose''']] a solution, with four functions (I've got little fantasy for the function names):

<code>[eiffel,N]
i18n (a_string : STRING) : STRING
--Function for the translation of normal strings

i18n_pl (strings : TUPLE[STRING]; form : INTEGER) : STRING
--Function for the translation of normal strings
-- with plural form

i18n_comp (a_string : STRING; args : TUPLE) : STRING
--Function for the translation of composit strings

i18n_comp_pl (strings : TUPLE[STRING]; args : TUPLE; form : INTEGER) : STRING
--Function for the translation of composit
-- strings with plural forms
</code>

With this solution, the programmer should write composit strings as (or in a similar way) he would do it for the C ''printf'' function. The composit string above would be somthing like this:

<code>[eiffel,N] i18n_comp("A string composed by %a1 strings, like this or %a2%N", [count, a_string])
</code>

where ''%a1'' is the place where the first string in the argument tuple (here ''count'') has to go. I've [[Talk:Internationalization/translation_function|'''choosen''']] that the items in the argument tuple are of type ANY, to insert them in the string we have to apply the functon ''out'' to all items.

===An example===

A complete example of how it could work.

----
Piece of code without internationalization:

<code>[eiffel,N]

[...]
if n = 1
io.put_string("Remove file "+file_name.out+"?%N")
else
io.put_string ("Delete following files?"+list.out+" there are "
+list.count.out+"files%N")
end
[...]

</code>

----

Piece of code with internationalization:

<code>[eiffel,N]

[...]
io.put_string(i18n_comp_pl(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n))
[...]
</code>

the content of the PO file would be:

#: A comment
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

You might ask yourself, ''why a function for all the pluralforms''?

The number of plural forms differ between languages. This is somewhat surprising for those who only have experiences with Romanic and Germanic languages since here the number is the same (there are two).
But other language families have only one form or many forms. For example,

In Polish the translation of file is plik, and the plural forms are:

:2,3,4 pliki
:5-21 pliko'w
:22-24 pliki
:25-31 pliko'w
:and so on...

for more information about this topic go [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 here]

==Additional things==

A nice thing whe could do, when parsing the source code of a program to internationalize, is to recognize comments about the string.
For example:

<code>[eiffel,N]

[...]
io.put_string(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n)
--A comment of the author
[...]
</code>

woud then look like this in the PO file:

#. A comment of the author
#. Function name, class name, file path
#. %a1 = file_name
#. %a2 = list
#. %a3 = list_count
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

Internationalization/translation function

2006-06-01T14:32:00Z

Carlo: /* Introduction */

[[Category:Projects]]
[[Category:Internationalization]]

==Introduction==

The problem for the translation is that we need a way to translate three different types of string:

* normal strings
<code>[eiffel,N] "A normal string"</code>
* composed string
<code>[eiffel,N] "A string composed by "+count.out+" strings, like this or "+a_string+"%N"</code>
* strings with plural form
<code>[eiffel,N]
if n=1 then
Result := "a string"
else
Result := "strings"
end
</code>

Another problem is that not all languages have the same rules for plural forms, see below and [[internationalization/plural_forms|here]] for more details.

==Possible solution==

I [[Talk:Internationalization/translation_function|'''propose''']] a solution, with four functions (I've got little fantasy for the function names):

<code>[eiffel,N]
i18n (a_string : STRING) : STRING
--Function for the translation of normal strings

i18n_pl (strings : TUPLE[STRING]; form : INTEGER) : STRING
--Function for the translation of normal strings
-- with plural form

i18n_comp (a_string : STRING; args : TUPLE) : STRING
--Function for the translation of composit strings

i18n_comp_pl (strings : TUPLE[STRING]; args : TUPLE; form : INTEGER) : STRING
--Function for the translation of composit
-- strings with plural forms
</code>

With this solution, the programmer should write composit strings as (or in a similar way) he would do it for the C ''printf'' function. The composit string above would be somthing like this:

<code>[eiffel,N] i18n_comp("A string composed by %a1 strings, like this or %a2%N", [count, a_string])
</code>

where ''%a1'' is the place where the first string in the argument tuple (here ''count'') has to go. I've [[Talk:Internationalization/translation_function|'''choosen''']] that the items in the argument tuple are of type ANY, to insert them in the string we have to apply the functon ''out'' to all items.

===An example===

A complete example of how it could work.

----
Piece of code without internationalization:

<code>[eiffel,N]

[...]
if n = 1
io.put_string("Remove file "+file_name.out+"?%N")
else
io.put_string ("Delete following files?"+list.out+" there are "
+list.count.out+"files%N")
end
[...]

</code>

----

Piece of code with internationalization:

<code>[eiffel,N]

[...]
io.put_string(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n)
[...]
</code>

the content of the PO file would be:

#: A comment
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

You might ask yourself, ''why a function for all the pluralforms''?

The number of plural forms differ between languages. This is somewhat surprising for those who only have experiences with Romanic and Germanic languages since here the number is the same (there are two).
But other language families have only one form or many forms. For example,

In Polish the translation of file is plik, and the plural forms are:

:2,3,4 pliki
:5-21 pliko'w
:22-24 pliki
:25-31 pliko'w
:and so on...

for more information about this topic go [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 here]

==Additional things==

A nice thing whe could do, when parsing the source code of a program to internationalize, is to recognize comments about the string.
For example:

<code>[eiffel,N]

[...]
io.put_string(["Remove file %a1?%N",
"Delete following files? %a2 there are %a3 files%N"],
[file_name, list, list_count], n)
--A comment of the author
[...]
</code>

woud then look like this in the PO file:

#. A comment of the author
#. Function name, class name, file path
#. %a1 = file_name
#. %a2 = list
#. %a3 = list_count
msgid "Remove file %a1?%N"
msgid_plural "Delete following files? %a2 there are %a3 files%N"
msgstr[0] "Rimuovere il file %a1?"
msgstr[1] "Cancellare i seguenti file? %a2 ce ne sono %a3%N"

Internationalization

2006-05-24T19:27:17Z

Carlo: /* M3: May ??? */ cleanup

[[Category:Projects]]
[[Image:ebabylon.png|right|frame| 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.

==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.

==Who should do the achieving?==
It is clear that our [[User:Carlo|Glorious Leader]] should be credited with any achieving. However he will have to delegate things somewhat, as he is is not [http://en.wikipedia.org/wiki/Aleksei_Grigorievich_Stakhanov Stakhanov].
We can probably divide the project into the following parts, modulo preliminary research:

''This should be probably be completed after we have got past M1''

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: April ??? ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated stings from .mo files ''([[User:etienner|Etienne]], [[User:Trosim|Martino]])''
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .po file
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings
** find a solution with templates
** globality: how to implement, the object should be shared between all modules (see [[Internationalization/class_structure|class structure]])
* collaborate with the [[Vision2_and_Unicode]] team
* Test unicode support in Vision2 ''(Ivano)''
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Talk:Internationalization/mo parser

2006-05-07T16:32:12Z

Carlo:

This page has been originally created by [[User:Trosim|Trosim]] as [[Internationalization/code parser]]
and then moved here by [[User:Carlo|me]] for consistency between title and content. --[[User:Carlo|Carlo]] 18:32, 7 May 2006 (CEST)

Internationalization/code parser

2006-05-07T16:23:10Z

Carlo: moved page to mo parser, content didn't match title

page moved to [[Internationalization/mo parser|mo parser]] because content didn't match title. --[[User:Carlo|Carlo]] 18:23, 7 May 2006 (CEST)

Internationalization/mo parser

2006-05-07T16:18:15Z

Carlo: moved from code parser

== Summary ==
That's what this part of the project should achieve:
* reading and parsing of MO files containing the strings and their translations
* organize the object collection in an incremental way: don't load the whole file if it's not needed
* give a simple interface to the localization class, so that the strings can be printed out without too much efforts

== Reading and parsing ==

=== Parser structure ===

I'll propose the class structure of the parser, later.

=== MO file structure ===

As reported from the [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC136 gettext manual].

byte
+------------------------------------------+
0 | magic number = 0x950412de |
| |
4 | file format revision = 0 |
| |
8 | number of strings | == N
| |
12 | offset of table with original strings | == O
| |
16 | offset of table with translation strings | == T
| |
20 | size of hashing table | == S
| |
24 | offset of hashing table | == H
| |
. .
. (possibly more entries later) .
. .
| |
O | length & offset 0th string ----------------.
O + 8 | length & offset 1st string ------------------.
... ... | |
O + ((N-1)*8) | length & offset (N-1)th string | | |
| | | |
T | length & offset 0th translation ---------------.
T + 8 | length & offset 1st translation -----------------.
... ... | | | |
T + ((N-1)*8) | length & offset (N-1)th translation | | | | |
| | | | | |
H | start hash table | | | | |
... ... | | | |
H + S * 4 | end hash table | | | | |
| | | | | |
| NUL terminated 0th string <----------------' | | |
| | | | |
| NUL terminated 1st string <------------------' | |
| | | |
... ... | |
| | | |
| NUL terminated 0th translation <---------------' |
| | |
| NUL terminated 1st translation <-----------------'
| |
... ...
| |
+------------------------------------------+

Internationalization

2006-05-07T16:10:11Z

Carlo: /* M3: May ??? */ updated

[[Category:Projects]]
[[Image:ebabylon.png|right|frame| 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.

==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.

==Who should do the achieving?==
It is clear that our [[User:Carlo|Glorious Leader]] should be credited with any achieving. However he will have to delegate things somewhat, as he is is not [http://en.wikipedia.org/wiki/Aleksei_Grigorievich_Stakhanov Stakhanov].
We can probably divide the project into the following parts, modulo preliminary research:

''This should be probably be completed after we have got past M1''

=Milestones=

==M2: May 5 ==
* [[Internationalization/feasibility|feasibility]]: look at string classes (unicode and not) and how strings are used in EiffelStudio (creation, composition) ''(Ivano, Carlo, Leo, Hong)''
* [[Internationalization/file_format|file format]]: compare existing file formats for dictionaries ''(Etienne, Andreas)''
* [[Internationalization/tool_evaluation|tool evaluation]]: list and compare existing translation tools ''(Christian, Martino)''

==M3: May ??? ==
* write an initial .po to start translating and have a .mo for testing ''(Leo, Carlo)''
* [[Internationalization/mo parser|mo parser]]: extract translated stings from .mo files ''([[User:etienner|Etienne]], Martino?)''
* [[Internationalization/code_parser|code parser]]: extract strings to be translated from source code and generate .po file
* [[Internationalization/translation function|translation function]]: map hard-coded strings to translated strings
** find a solution with templates
** globality: how to implement, the object should be shared between all modules
** collaborate with the [[Vision2_and_Unicode]] team
*Test unicode support in Vision2 ''(Ivano)''
* compile a [[Internationalization/features list|list of basic features]] to provide (e.g. date/time format, system locale) ''[deferred]''

= Possible future developments =

* collaborate with the [[ESWizard]] team. Create wizards for programms with translation facilities.

=Relevant Links=
[http://www.debian.org/doc/manuals/intro-i18n/ Introduction to i18n]

==What other people have done==
[http://doc.trolltech.com/4.1/i18n.html internationalisation with QT]

[http://oss.erdfunkstelle.de/kde-i18n/tiki-index.php?page=miniHowtoGui howto for internationalisation of KDE programs ]

[http://l10n.kde.org/docs/translation-howto/ another KDE howto (doesn't Gnome do any internationalisation?)]

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* [[User:kiwi| Ivano Somaini]]
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* [[User:cconti | Christian Conti]]
* [[User:Trosim |Martino Trosi]]
* [[User:Schoelle| Bernd Schoeller]]

Talk:Internationalization

2006-05-04T23:15:32Z

Carlo: /* Useful link */

What is the difference between PO and MO files?
--[[User:Manus|manus]] 21:35, 4 May 2006 (CEST)
:PO (Portable Object) is the human readable format, with keywords and all the white-spaces; MO (Machine object) are intended to be read by computers and have no formatting. [[User:Trosim|Trosim]] 21:49, 4 May 2006 (CEST)

Cooles Logo
''Bernd''

=Useful link=

[http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC191 Here] is the approach of GNU for internationalization.

[http://xnap-commons.sourceforge.net/gettext-commons/tutorial.html Gettext and Java]

[http://www.eiffelzone.com/esd/eutils/index.html a project for SmartEiffel that has a class for Printf-like STRING formatting with positional indexes]

About object globality see ''OO Software Construction 2nd edition'', B. Meyer; chap. 18 ''Global objects and constants''

Talk:Internationalization/file format

2006-05-02T20:57:02Z

Carlo: /* Voting */ fix total

= Format proposals =

About our today's talk on file formats, you can read the [[http://en.wikipedia.org/wiki/Xml XML page on Wikipedia]]

=Parallel Wikis=

I think that the wiki for the project should be only one, we are allowed to put test versions or proposals... ''(Martino)''

I agree. We should probably stick to one wiki because it will get confusing otherwise - sorry, Carlo.
[[User:Leo|Leo]] 01:52, 27 April 2006 (CEST)

=Comments=

So, as you can see I found few positive aspects for XML and few negative for PO. I don't want to advertise the PO format, so if you know/find aspects that I haven't mentioned, don't hesitate to add them! [[User:Etienner|Etienner]] 17:09, 28 April 2006 (CEST)

==Partiality, unicode and readability==

It seems like these judgments are a bit "partial", but that's normal... maybe someone sustaining XML should put his opinion...
and about readability: I don't think it's really a big problem... if it is, it can be solved by writing a simple "translator" to "human readable"
Unicode: isn't it a big advantage that XML fully supports unicode? [[User:Cconti|Cconti]]

:I know, the judgments are partial, but this is the great advantage of wiki pages combined with the comunity that uses them: the more it is modified, the more pages get unpartial...
:For the human readability, you are right.
:Unicode IS a big advantage, but [http://en.wikipedia.org/wiki/UTF-8 UTF-8] is a unicode encoding, and it appears as last entry in the [[Internationalization/file_format#Supported_character_encodings|list]]. [[User:Etienner|'''Etienne''']] [[User talk:Etienner|'''talk''']]

::My opinion on the whole thing: We do not really need to build hierarchies, which is what XML would be good at.
::On the other hand, we have an XML parser in Eiffel already, and despite there being gettext under a free license it is probably far better to avoid new external dependancies.
::If cats could talk they would chose XML-described catfood. In this case.
:::Because if cats could talk, they could read the ingredients of catfood, too. But not if they are XML-described... :-) [[User:Etienner|'''E''''''T''''''N''']] [[User talk:Etienner|'''talk''']]

==Licensing==

We will have to write our own .po parser because ISE will want copyright assignent (or at the least BSD licensing) & we can't just use gettext because there is probably no way to make this an optional addon. [[User:Leo|Leo]] 19:29, 28 April 2006 (CEST)

:I'm not an expert on licensing stuff so I'v copied from the gettext manual and pasted it here.

:Some people wonder if using GNU gettext necessarily brings their package under the protective wing of the GNU General Public License or the GNU Library General Public License, when they do not want to make their program free, or want other kinds of freedom. The simplest answer is "normally not".
:The GNU gettext library, i.e. the contents of libintl, is covered by the GNU Library General Public License. The rest of the GNU gettext package is covered by the GNU General Public License.
:The mere marking of localizable strings in a package, or conditional inclusion of a few lines for initialization, is not really including GPL'ed or LGPL'ed code. However, since the localization routines in libintl are under the LGPL, the LGPL needs to be considered. It gives the right to distribute the complete unmodified source of libintl evehttp://eiffelsoftware.origo.ethz.ch/index.php?title=Talk:Internationalization/file_format&action=editn with non-free programs. It also gives the right to use libintl as a shared library, even for non-free programs. But it gives the right to use libintl as a static library or to incorporate libintl into another library only to free software. [[User:Etienner|Etienner]] 19:49, 28 April 2006 (CEST)

::There exists a [http://developer.postgresql.org/~petere/bsd-gettext/ BSD-licensed gettext implementation] from the NetBSD project. --[[User:Thom|Thom]] 10:09, 29 April 2006 (CEST)

:::Thanks. I'll have a look at it. [[User:Leo|Leo]] 15:15, 29 April 2006 (CEST)

==Voting==

I think there are now enough information for a voting on the file format...

{| BORDER="0" CELLPADDING="3" CELLSPACING="0" ID="Table3"
|- ALIGN="center" bgcolor="#e0e0e0"
! Person!! XML !! PO !! New!!
|- ALIGN="center"
| [[User:Etienner|Etienne]] || || X || ||
|- ALIGN="center"
| [[User:Vpiff|Vpiff]] || || X || ||
|- ALIGN="center"
| [[User:Murbi|Murbi]] || || X || ||
|- ALIGN="center"
| [[User:Lücs|Lücs]] || || X || ||
|- ALIGN="center"
| [[User:Carlo|Carlo]] || || X || ||







|- ALIGN="center" bgcolor="#e0e0e0"
!Total !! 0 !! 5 !! 0!!
|}

Despite the votation the file format will still be discussed (with argumentations) at the next meeting. --[[User:Carlo|Carlo]] 22:43, 2 May 2006 (CEST)

Talk:Internationalization/file format

2006-05-02T20:45:50Z

Carlo: /* Voting */

= Format proposals =

About our today's talk on file formats, you can read the [[http://en.wikipedia.org/wiki/Xml XML page on Wikipedia]]

=Parallel Wikis=

I think that the wiki for the project should be only one, we are allowed to put test versions or proposals... ''(Martino)''

I agree. We should probably stick to one wiki because it will get confusing otherwise - sorry, Carlo.
[[User:Leo|Leo]] 01:52, 27 April 2006 (CEST)

=Comments=

So, as you can see I found few positive aspects for XML and few negative for PO. I don't want to advertise the PO format, so if you know/find aspects that I haven't mentioned, don't hesitate to add them! [[User:Etienner|Etienner]] 17:09, 28 April 2006 (CEST)

==Partiality, unicode and readability==

It seems like these judgments are a bit "partial", but that's normal... maybe someone sustaining XML should put his opinion...
and about readability: I don't think it's really a big problem... if it is, it can be solved by writing a simple "translator" to "human readable"
Unicode: isn't it a big advantage that XML fully supports unicode? [[User:Cconti|Cconti]]

:I know, the judgments are partial, but this is the great advantage of wiki pages combined with the comunity that uses them: the more it is modified, the more pages get unpartial...
:For the human readability, you are right.
:Unicode IS a big advantage, but [http://en.wikipedia.org/wiki/UTF-8 UTF-8] is a unicode encoding, and it appears as last entry in the [[Internationalization/file_format#Supported_character_encodings|list]]. [[User:Etienner|'''Etienne''']] [[User talk:Etienner|'''talk''']]

::My opinion on the whole thing: We do not really need to build hierarchies, which is what XML would be good at.
::On the other hand, we have an XML parser in Eiffel already, and despite there being gettext under a free license it is probably far better to avoid new external dependancies.
::If cats could talk they would chose XML-described catfood. In this case.
:::Because if cats could talk, they could read the ingredients of catfood, too. But not if they are XML-described... :-) [[User:Etienner|'''E''''''T''''''N''']] [[User talk:Etienner|'''talk''']]

==Licensing==

We will have to write our own .po parser because ISE will want copyright assignent (or at the least BSD licensing) & we can't just use gettext because there is probably no way to make this an optional addon. [[User:Leo|Leo]] 19:29, 28 April 2006 (CEST)

:I'm not an expert on licensing stuff so I'v copied from the gettext manual and pasted it here.

:Some people wonder if using GNU gettext necessarily brings their package under the protective wing of the GNU General Public License or the GNU Library General Public License, when they do not want to make their program free, or want other kinds of freedom. The simplest answer is "normally not".
:The GNU gettext library, i.e. the contents of libintl, is covered by the GNU Library General Public License. The rest of the GNU gettext package is covered by the GNU General Public License.
:The mere marking of localizable strings in a package, or conditional inclusion of a few lines for initialization, is not really including GPL'ed or LGPL'ed code. However, since the localization routines in libintl are under the LGPL, the LGPL needs to be considered. It gives the right to distribute the complete unmodified source of libintl evehttp://eiffelsoftware.origo.ethz.ch/index.php?title=Talk:Internationalization/file_format&action=editn with non-free programs. It also gives the right to use libintl as a shared library, even for non-free programs. But it gives the right to use libintl as a static library or to incorporate libintl into another library only to free software. [[User:Etienner|Etienner]] 19:49, 28 April 2006 (CEST)

::There exists a [http://developer.postgresql.org/~petere/bsd-gettext/ BSD-licensed gettext implementation] from the NetBSD project. --[[User:Thom|Thom]] 10:09, 29 April 2006 (CEST)

:::Thanks. I'll have a look at it. [[User:Leo|Leo]] 15:15, 29 April 2006 (CEST)

==Voting==

I think there are now enough information for a voting on the file format...

{| BORDER="0" CELLPADDING="3" CELLSPACING="0" ID="Table3"
|- ALIGN="center" bgcolor="#e0e0e0"
! Person!! XML !! PO !! New!!
|- ALIGN="center"
| [[User:Etienner|Etienne]] || || X || ||
|- ALIGN="center"
| [[User:Vpiff|Vpiff]] || || X || ||
|- ALIGN="center"
| [[User:Murbi|Murbi]] || || X || ||
|- ALIGN="center"
| [[User:Lücs|Lücs]] || || X || ||
|- ALIGN="center"
| [[User:Carlo|Carlo]] || || X || ||







|- ALIGN="center" bgcolor="#e0e0e0"
!Total !! 0 !! 4 !! 0!!
|}

Despite the votation the file format will still be discussed (with argumentations) at the next meeting. --[[User:Carlo|Carlo]] 22:43, 2 May 2006 (CEST)

Talk:Internationalization/file format

2006-05-02T20:43:03Z

Carlo: /* Voting */

= Format proposals =

About our today's talk on file formats, you can read the [[http://en.wikipedia.org/wiki/Xml XML page on Wikipedia]]

=Parallel Wikis=

I think that the wiki for the project should be only one, we are allowed to put test versions or proposals... ''(Martino)''

I agree. We should probably stick to one wiki because it will get confusing otherwise - sorry, Carlo.
[[User:Leo|Leo]] 01:52, 27 April 2006 (CEST)

=Comments=

So, as you can see I found few positive aspects for XML and few negative for PO. I don't want to advertise the PO format, so if you know/find aspects that I haven't mentioned, don't hesitate to add them! [[User:Etienner|Etienner]] 17:09, 28 April 2006 (CEST)

==Partiality, unicode and readability==

It seems like these judgments are a bit "partial", but that's normal... maybe someone sustaining XML should put his opinion...
and about readability: I don't think it's really a big problem... if it is, it can be solved by writing a simple "translator" to "human readable"
Unicode: isn't it a big advantage that XML fully supports unicode? [[User:Cconti|Cconti]]

:I know, the judgments are partial, but this is the great advantage of wiki pages combined with the comunity that uses them: the more it is modified, the more pages get unpartial...
:For the human readability, you are right.
:Unicode IS a big advantage, but [http://en.wikipedia.org/wiki/UTF-8 UTF-8] is a unicode encoding, and it appears as last entry in the [[Internationalization/file_format#Supported_character_encodings|list]]. [[User:Etienner|'''Etienne''']] [[User talk:Etienner|'''talk''']]

::My opinion on the whole thing: We do not really need to build hierarchies, which is what XML would be good at.
::On the other hand, we have an XML parser in Eiffel already, and despite there being gettext under a free license it is probably far better to avoid new external dependancies.
::If cats could talk they would chose XML-described catfood. In this case.
:::Because if cats could talk, they could read the ingredients of catfood, too. But not if they are XML-described... :-) [[User:Etienner|'''E''''''T''''''N''']] [[User talk:Etienner|'''talk''']]

==Licensing==

We will have to write our own .po parser because ISE will want copyright assignent (or at the least BSD licensing) & we can't just use gettext because there is probably no way to make this an optional addon. [[User:Leo|Leo]] 19:29, 28 April 2006 (CEST)

:I'm not an expert on licensing stuff so I'v copied from the gettext manual and pasted it here.

:Some people wonder if using GNU gettext necessarily brings their package under the protective wing of the GNU General Public License or the GNU Library General Public License, when they do not want to make their program free, or want other kinds of freedom. The simplest answer is "normally not".
:The GNU gettext library, i.e. the contents of libintl, is covered by the GNU Library General Public License. The rest of the GNU gettext package is covered by the GNU General Public License.
:The mere marking of localizable strings in a package, or conditional inclusion of a few lines for initialization, is not really including GPL'ed or LGPL'ed code. However, since the localization routines in libintl are under the LGPL, the LGPL needs to be considered. It gives the right to distribute the complete unmodified source of libintl evehttp://eiffelsoftware.origo.ethz.ch/index.php?title=Talk:Internationalization/file_format&action=editn with non-free programs. It also gives the right to use libintl as a shared library, even for non-free programs. But it gives the right to use libintl as a static library or to incorporate libintl into another library only to free software. [[User:Etienner|Etienner]] 19:49, 28 April 2006 (CEST)

::There exists a [http://developer.postgresql.org/~petere/bsd-gettext/ BSD-licensed gettext implementation] from the NetBSD project. --[[User:Thom|Thom]] 10:09, 29 April 2006 (CEST)

:::Thanks. I'll have a look at it. [[User:Leo|Leo]] 15:15, 29 April 2006 (CEST)

==Voting==

I think there are now enough information for a voting on the file format...

{| BORDER="0" CELLPADDING="3" CELLSPACING="0" ID="Table3"
|- ALIGN="center" bgcolor="#e0e0e0"
! Person!! XML !! PO !! New!!
|- ALIGN="center"
| [[User:Etienner|Etienne]] || || X || ||
|- ALIGN="center"
| [[User:Vpiff|Vpiff]] || || X || ||
|- ALIGN="center"
| [[User:Murbi|Murbi]] || || X || ||
|- ALIGN="center"
| [[User:Lücs|Lücs]] || || X || ||







|- ALIGN="center" bgcolor="#e0e0e0"
!Total !! 0 !! 4 !! 0!!
|}

Despite the votation the file format will still be discussed (with argumentations) at the next meeting. --[[User:Carlo|Carlo]] 22:43, 2 May 2006 (CEST)

Talk:Internationalization/tool evaluation

2006-05-02T09:16:26Z

Carlo: /* Some translation tools */ forgot signature

If you have suggestions on the tool to be used contact us!

Every experience will help us a lot.

Ok, here are my thoughts: there are two sets of tools needed.
* Translation tools - they will let you edit a file containg strings/templates in a friendly manner.
* Extraction tools - they will let you pull all strings to be localised from the source code. Such a tool will possibly need to be Eiffel-specific, and we will probably have to do this ourselves.

I think it is only worth discussing the first category. Once we find a handy tool we can write a filter for it's file format to/from our own and use it for any "demo" localisations we produce.
Ideally we should be able to export to a variety of popular formats. How does Windows do it? What are the preferred tools for localisation in the Microsoft world? [[User:Leo|Leo]] 02:11, 27 April 2006 (CEST)

It would be nice to see how the VisualStudio handle this. --[[User:Carlo|Carlo]] 08:20, 27 April 2006 (CEST)

== Some translation tools ==

The short list is here [http://say.uaz.ch/wiki/tiki-index.php?page=translation+tools] --[[User:Carlo|Carlo]] 11:16, 2 May 2006 (CEST)

Talk:Internationalization/tool evaluation

2006-05-02T09:15:37Z

Carlo: Some translation tools

Internationalization/feasibility

2006-05-01T11:35:51Z

Carlo: /* Important Classes */ categoryzed

==Summary==
Our task is to find out the possible main difficulties that will be encoutered during both design and implementation of the [[internationalization|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 difficulties==

===Constant String===
Workbench_name: STRING is "EiffelStudio"

====Difficulties====
====Possible Solution====

===String with label specific syntax===
m_to_lower: STRING is "Set to &Lowercase%TCtrl+Shift+U"

====Difficulties====
* Bad readability for the traducer
* Shortcuts conflict
====Possible Solution====

===Composed String===
m_About:STRING is
once
Result:"&About" + Workbench_name + "..."
end

====Difficulties====
====Possible Solution====

==Important Classes==

====Defining and formatting Strings====

* INTERFACE_NAMES: Include all the strings of the ES interface (buttons, labels, shortcuts...)
* TEXT_FORMATTER: Text formatter for all text output formatting
* 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...)

====Implementations====

* 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]

Internationalization/feasibility

2006-04-30T23:27:03Z

Carlo: /* Important Classes */

Talk:Internationalization/feasibility

2006-04-29T20:36:17Z

Carlo:

==Unicode support==
A report on the current support for Unicode in Gobo has been requested (see [http://origo.ethz.ch/pipermail/es-vision/2006-April/000002.html here]) but may not come in time for us to profit.
It seems like there are two efforts to support Unicode, one for Gobo and one for EiffelVision, that are still sort of independent from oneanother. --[[User:Carlo|Carlo]] 22:36, 29 April 2006 (CEST)

Internationalization/feasibility

2006-04-29T20:16:16Z

Carlo: summary draft

==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

Talk:Internationalization/tool evaluation

2006-04-27T06:20:42Z

Carlo:

Internationalization

2006-04-25T16:20:19Z

Carlo: format

[[Category:Projects]]

=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))
* [http://say.uaz.ch/wiki/tiki-index.php?page=compare+xml+po 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

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Frank Fellmann]]
* Ivano Somaini
* [[User:murbi|Andreas Murbach]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:hong |Hong Zhang]]
* Christian Conti
* Martino Trosi
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-04-25T16:19:02Z

Carlo: /* M2: May ??? */ postponed a milestone, introduced new M2

Internationalization

2006-04-24T22:53:20Z

Carlo: /* Overview */

[[Category:Projects]]

=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 ??? ==
* 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

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* Ivano Somaini
* Andreas Hans Murbach
* [[User:etienner|Etienne Reichenbach]]
* Hong Zhang
* Christian Conti
* Martino Trosi
* [[User:Schoelle| Bernd Schoeller]]

Internationalization

2006-04-21T18:02:18Z

Carlo: /* M2: May ??? */

[[Category:Projects]]

=Overview=

''To be added''

=Milestones=

==M1: April 25th==
* set up mailinglist es-i18n@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: 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

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* Ivano Somaini
* Andreas Hans Murbach
* [[User:etienner|Etienne Reichenbach]]
* Hong Zhang
* Christian Conti
* Martino Trosi
* [[User:Schoelle| Bernd Schoeller]]

Vision2 and Unicode

2006-04-21T17:28:11Z

Carlo: /* Team */

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Readings=

==Unicode==
* http://de.wikipedia.org/wiki/Unicode
* http://www.unicode.org/
** http://www.unicode.org/standard/WhatIsUnicode.html
** http://www.unicode.org/standard/standard.html

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* implement multi screen support for Vision: [[Multi screen support]]
* collaborate with the [[internationalization]] team
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=

Everyone interested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-vision es-vision@origo.ethz.ch]

* Project Leader: Raffaele
* [[User:korzieher| Adrian]]
* [[User:Dartzki| Dario]]
* [[User:Bayt| Bayt]]
* [[User:frEeAx| Michele]]
* [[User:Serafin| Serafin]]

=Communication=
We agreed to communicate via [http://de.wikipedia.org/wiki/Irc IRC] (orwell.freenode.net/es-vision).
For Windows user there are different programs available. For example:
* [http://hydrairc.com/index.php?page=downloads HydraIRC]
* [http://www.mirc.com/get.html mirc]

Linux user (for ex.) one of the following
* xchat
* irssi (console-app.)

after downloading and installing, you can connect to a server with the command
<pre>
/server <serveradress>
</pre>
where <serveradress> is (for ex.) orwell.freenode.net ([http://freenode.net/irc_servers.shtml more freenode servers]).

to enter our channel, type:
<pre>
/join #es-vision
</pre>

also you can set/change your nickname with
<pre>
/nick <new_nick>
</pre>
where <new_nick> is you nickname.

Internationalization

2006-04-21T16:25:02Z

Carlo: /* Team */

[[Category:Projects]]

=Overview=

''To be added''

=Milestones=

==M1: April 25th==
* set up mailinglist es-i18n@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=

Everyone interested in this project is welcome to [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-i18n join our mailinglist] es-i18n@origo.ethz.ch

* Project Leader: [[User:Carlo|Carlo Vanini]]
* [[User:leo| Leo Fellmann]]
* Ivano Somaini
* Andreas Hans Murbach
* [[User:etienner|Etienne Reichenbach]]
* Hong Zhang
* Christian Conti
* Martino Trosi
* [[User:Schoelle| Bernd Schoeller]]