EiffelStudio: an EiffelSoftware project - User contributions [en]

Internationalization/posix locale

2006-09-07T12:14:28Z

Mingmei:

[[Category:Internationalization]]

==Summary==
My Summary is based on article by Michael Becker (see [http://www.ijon.de/comp/tutorials/locale.html here]).This summary is more or less concerning SuSE-Linux.

There are differences between User-locale and C-locale. C-locale, is the local, which is only effective in C-environment. If there are no locales set in user environment, then C-locale is effective, which is so called "POSIX"-locale.

With C-command <code>setlocale (LC_ALL,"")</code> one set C-locale with User-locale. So one could retrieve details about User-locale information with C-functions.

==Listing available locales==
There are two directories that one could get information about locales.
They are:
''/usr/share/locale/''
''/usr/share/i18n/''

In the first directory, the locales are binary files. So we could not need them for our purpose since i do not know how to read them for the moment.

In the second directory there are at least 2 subdirectories, with names charmaps and locales.

Shell command ''ls /usr/share/i18n/locales/'' list all the available locales.

==Checking for default locale==

With shell command "locale" one can get infomation about default locale.
In C, to get details of localeone can use
<code>setlocale (LC_ALL,"")
localeconv()</code>
see ''manpage locale(7)'' to get more information.

Another way to obtain the current locale is to use the environnement variable ''LANGUAGE'', this is done with the following code:

<code>[eiffel,N]
environement : EXECUTION_ENVIRONMENT
...
environement.get ("LANGUAGE")
-- returns the (rank)list (as string) of languages set by the user
</code>

== Retrieving locale information ==
C-command <code> nl_langinfo() </code>(defined in langinfo.h) one could get information about all categories.

===1. LC_NUMERIC ===

Comparing LC_NUMERIC formats in posix,en_US, de_DE,zh_CN
1.C-codes and their outputs:
====posix====
#include <stdio.h>
#include <langinfo.h>

int main (int arg,char** argv){
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);
}
Outputs are:12345678 12345678 123456.780000 123456.780000 12:34
====en_US====
#include <stdio.h>
#include <langinfo.h>
#include <locale.h>

int main (int arg,char** argv){
setlocale(LC_NUMERIC,"en_US");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,4,2);
}
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:04
====de_DE====
int main (int arg,char** argv){
setlocale(LC_NUMERIC,"de_DE");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);

}
Outputs are:12345678 12.345.678 123456,780000 123.456,780000 12:34
====zh_CN====
setlocale(LC_NUMERIC,"zh_CN"); only change to above code
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:34
===Analysing results===
Look at all the locale source files, the results are resonable to us.

Feld
Posix
en_US
de_DE
zh_CN
decimal_point
"<U002E>"
"<U002E>"
"<U002C>"
"<U002E>"
thousands_sep
""
"<U002C>"
"<U002E>"
"<U002C>"
grouping
-1
3;3
3;3
3

Where "<U002E>" means "dot"; "<U002C>" means "comma".

===2.LC_TIME===
For this purpose there is a C-function <code> nl_langinfo() </code> (defined in langinfo.h).
Here is a list of arguments for this function, which are useful for our project:
*ABDAY_x : abbreviated name of weekday x, %a-Descriptor
*DAY_x : name of day x,%A-Descriptor
*ABMON_x : abbreviated name of month x, %b-Descriptor
*MON_x : name of month x,%B-Descriptor
*[AM|PM]_STR: strings which can be used in the representation of time as an hour from 1 to 12 plus an am/pm specifier.
*D_T_FMT: time and date pattern in a locale-specific way.
*D_FMT: date pattern: date pattern in a locale-specific way.
*T_FMT: time pattern in a locale-specific way.

The result of nl_langinfo, called with one of the last three arguments, can than be used as argument for the C-function <code>strftime()</code>.

For example, with <code> nl_langinfo(D_T_FMT)</code>, one get a pointer at a string, which in form of %a %d %b %Y %T %Z.
where:
%a: The abbreviated weekday name according to the current locale
%d: The day of the month as a decimal number (range 01 to 31)
%b: The abbreviated month name according to the current locale
%Y: The year as a decimal number including the century.
%T: The time in 24-hour notation (%H:%M:%S)
%Z: The time zone or name or abbreviation

== Other information ==
Using a parser one could also retrieve locale information, about which I do not have a lot of idea.

Still there are C-functions to use categories.
For example,
<code>strftime()
strptime()
wcsftime()</code>
for LC_TIME
For another example,
<code>isalnum
isalpha
isblank</code>
and so on for LC_CTYPE.

For more information please read [http://www.opengroup.org/onlinepubs/007908799/xbd/locale.html local-Specification of Unix Open].
Another paper auf dem Linux Kongress 1995 in Berlin from Jochen Hein is also useful, see [http://www.jochen.org/vortraege/nls-1995.pdf National Language Support]

Internationalization/posix locale

2006-09-07T11:59:16Z

Mingmei:

[[Category:Internationalization]]

==Summary==
My Summary is based on article by Michael Becker (see [http://www.ijon.de/comp/tutorials/locale.html here]).This summary is more or less concerning SuSE-Linux.

There are differences between User-locale and C-locale. C-locale, is the local, which is only effective in C-environment. If there are no locales set in user environment, then C-locale is effective, which is so called "POSIX"-locale.

With C-command <code>setlocale (LC_ALL,"")</code> one set C-locale with User-locale. So one could retrieve details about User-locale information with C-functions.

==Listing available locales==
There are two directories that one could get information about locales.
They are:
''/usr/share/locale/''
''/usr/share/i18n/''

In the first directory, the locales are binary files. So we could not need them for our purpose since i do not know how to read them for the moment.

In the second directory there are at least 2 subdirectories, with names charmaps and locales.

Shell command ''ls /usr/share/i18n/locales/'' list all the available locales.

==Checking for default locale==

With shell command "locale" one can get infomation about default locale.
In C, to get details of localeone can use
<code>setlocale (LC_ALL,"")
localeconv()</code>
see ''manpage locale(7)'' to get more information.

Another way to obtain the current locale is to use the environnement variable ''LANGUAGE'', this is done with the following code:

<code>[eiffel,N]
environement : EXECUTION_ENVIRONMENT
...
environement.get ("LANGUAGE")
-- returns the (rank)list (as string) of languages set by the user
</code>

== Retrieving locale information ==
C-command <code> nl_langinfo() </code>(defined in langinfo.h) one could get information about all categories.
For example, with <code> nl_langinfo(D_T_FMT)</code>, one get a pointer at a string, which in form of %a %d %b %Y %T %Z.

=== LC_NUMERIC ===

Comparing LC_NUMERIC formats in posix,en_US, de_DE,zh_CN
1.C-codes and their outputs:
====posix====
#include <stdio.h>
#include <langinfo.h>

int main (int arg,char** argv){
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);
}
Outputs are:12345678 12345678 123456.780000 123456.780000 12:34
====en_US====
#include <stdio.h>
#include <langinfo.h>
#include <locale.h>

int main (int arg,char** argv){
setlocale(LC_NUMERIC,"en_US");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,4,2);
}
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:04
====de_DE====
int main (int arg,char** argv){
setlocale(LC_NUMERIC,"de_DE");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);

}
Outputs are:12345678 12.345.678 123456,780000 123.456,780000 12:34
====zh_CN====
setlocale(LC_NUMERIC,"zh_CN"); only change to above code
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:34
===Analysing results===
Look at all the locale source files, the results are resonable to us.

Feld
Posix
en_US
de_DE
zh_CN
decimal_point
"<U002E>"
"<U002E>"
"<U002C>"
"<U002E>"
thousands_sep
""
"<U002C>"
"<U002E>"
"<U002C>"
grouping
-1
3;3
3;3
3

Where "<U002E>" means "dot"; "<U002C>" means "comma".

== Other information ==
Using a parser one could also retrieve locale information, about which I do not have a lot of idea.

Still there are C-functions to use categories.
For example,
<code>strftime()
strptime()
wcsftime()</code>
for LC_TIME
For another example,
<code>isalnum
isalpha
isblank</code>
and so on for LC_CTYPE.

For more information please read [http://www.opengroup.org/onlinepubs/007908799/xbd/locale.html local-Specification of Unix Open].
Another paper auf dem Linux Kongress 1995 in Berlin from Jochen Hein is also useful, see [http://www.jochen.org/vortraege/nls-1995.pdf National Language Support]

Internationalization/posix locale

2006-09-07T11:51:17Z

Mingmei:

[[Category:Internationalization]]

==Summary==
My Summary is based on article by Michael Becker (see [http://www.ijon.de/comp/tutorials/locale.html here]).This summary is more or less concerning SuSE-Linux.

There are differences between User-locale and C-locale. C-locale, is the local, which is only effective in C-environment. If there are no locales set in user environment, then C-locale is effective, which is so called "POSIX"-locale.

With C-command <code>setlocale (LC_ALL,"")</code> one set C-locale with User-locale. So one could retrieve details about User-locale information with C-functions.

==Listing available locales==
There are two directories that one could get information about locales.
They are:
''/usr/share/locale/''
''/usr/share/i18n/''

In the first directory, the locales are binary files. So we could not need them for our purpose since i do not know how to read them for the moment.

In the second directory there are at least 2 subdirectories, with names charmaps and locales.

Shell command ''ls /usr/share/i18n/locales/'' list all the available locales.

==Checking for default locale==

With shell command "locale" one can get infomation about default locale.
In C, to get details of localeone can use
<code>setlocale (LC_ALL,"")
localeconv()</code>
see ''manpage locale(7)'' to get more information.

Another way to obtain the current locale is to use the environnement variable ''LANGUAGE'', this is done with the following code:

<code>[eiffel,N]
environement : EXECUTION_ENVIRONMENT
...
environement.get ("LANGUAGE")
-- returns the (rank)list (as string) of languages set by the user
</code>

== Retrieving locale information ==
C-command <code> nl_langinfo() </code>(defined in langinfo.h) one could get information about all categories.
For example, with <code> nl_langinfo(D_T_FMT)</code>, one get a pointer at a string, which in form of %a %d %b %Y %T %Z.

== LC_NUMERIC ==

Comparing LC_NUMERIC formats in posix,en_US, de_DE,zh_CN
1.C-codes and their outputs:
===posix===
#include <stdio.h>
#include <langinfo.h>

int main (int arg,char** argv){
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);
}
Outputs are:12345678 12345678 123456.780000 123456.780000 12:34
===en_US===
#include <stdio.h>
#include <langinfo.h>
#include <locale.h>

int main (int arg,char** argv){
setlocale(LC_NUMERIC,"en_US");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,4,2);
}
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:04
===de_DE===
int main (int arg,char** argv){
setlocale(LC_NUMERIC,"de_DE");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);

}
Outputs are:12345678 12.345.678 123456,780000 123.456,780000 12:34
===zh_CN===
setlocale(LC_NUMERIC,"zh_CN"); only change to above code
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:34
===Analysing results===
Look at all the locale source files, the results are resonable to us.

Feld
Posix
en_US
de_DE
zh_CN
decimal_point
"<U002E>"
"<U002E>"
"<U002C>"
"<U002E>"
thousands_sep
""
"<U002C>"
"<U002E>"
"<U002C>"
grouping
-1
3;3
3;3
3

Where "<U002E>" means "dot"; "<U002C>" means "comma".

== Other information ==
Using a parser one could also retrieve locale information, about which I do not have a lot of idea.

Still there are C-functions to use categories.
For example,
<code>strftime()
strptime()
wcsftime()</code>
for LC_TIME
For another example,
<code>isalnum
isalpha
isblank</code>
and so on for LC_CTYPE.

For more information please read [http://www.opengroup.org/onlinepubs/007908799/xbd/locale.html local-Specification of Unix Open].
Another paper auf dem Linux Kongress 1995 in Berlin from Jochen Hein is also useful, see [http://www.jochen.org/vortraege/nls-1995.pdf National Language Support]

User:Mingmei

2006-09-07T11:41:28Z

Mingmei:

hello everybody!

Now I am ready to work on this semester thesis [[internationalization|i18n]]. Last two weeks I was working as interpreter at Alstom Power. It was a lot of fun, but it was also quite stressy.

我现在在做学期论文，论题是[[internationalization|国际化]]。上两周我在阿而斯通做技术翻译，紧张而有趣。

Internationalization/posix locale

2006-09-07T09:51:52Z

Mingmei:

[[Category:Internationalization]]

==Summary==
My Summary is based on article by Michael Becker (see [http://www.ijon.de/comp/tutorials/locale.html here]).This summary is more or less concerning SuSE-Linux.

There are differences between User-locale and C-locale. C-locale, is the local, which is only effective in C-environment. If there are no locales set in user environment, then C-locale is effective, which is so called "POSIX"-locale.

With C-command <code>setlocale (LC_ALL,"")</code> one set C-locale with User-locale. So one could retrieve details about User-locale information with C-functions.

==Listing available locales==
There are two directories that one could get information about locales.
They are:
''/usr/share/locale/''
''/usr/share/i18n/''

In the first directory, the locales are binary files. So we could not need them for our purpose since i do not know how to read them for the moment.

In the second directory there are at least 2 subdirectories, with names charmaps and locales.

Shell command ''ls /usr/share/i18n/locales/'' list all the available locales.

==Checking for default locale==

With shell command "locale" one can get infomation about default locale.
In C, to get details of localeone can use
<code>setlocale (LC_ALL,"")
localeconv()</code>
see ''manpage locale(7)'' to get more information.

Another way to obtain the current locale is to use the environnement variable ''LANGUAGE'', this is done with the following code:

<code>[eiffel,N]
environement : EXECUTION_ENVIRONMENT
...
environement.get ("LANGUAGE")
-- returns the (rank)list (as string) of languages set by the user
</code>

== Retrieving locale information ==
C-command <code> nl_langinfo() </code>(defined in langinfo.h) one could get information about all categories.
For example, with <code> nl_langinfo(D_T_FMT)</code>, one get a pointer at a string, which in form of %a %d %b %Y %T %Z.

== Other information ==
Using a parser one could also retrieve locale information, about which I do not have a lot of idea.

Still there are C-functions to use categories.
For example,
<code>strftime()
strptime()
wcsftime()</code>
for LC_TIME
For another example,
<code>isalnum
isalpha
isblank</code>
and so on for LC_CTYPE.

For more information please read [http://www.opengroup.org/onlinepubs/007908799/xbd/locale.html local-Specification of Unix Open].
Another paper auf dem Linux Kongress 1995 in Berlin from Jochen Hein is also useful, see [http://www.jochen.org/vortraege/nls-1995.pdf National Language Support]

==Retrieving local information: LC_NUMERIC ==

Comparing LC_NUMERIC formats in posix,en_US, de_DE,zh_CN
1.C-codes and their outputs:
===posix===
#include <stdio.h>
#include <langinfo.h>

int main (int arg,char** argv){
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);
}
Outputs are:12345678 12345678 123456.780000 123456.780000 12:34
===en_US===
#include <stdio.h>
#include <langinfo.h>
#include <locale.h>

int main (int arg,char** argv){
setlocale(LC_NUMERIC,"en_US");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,4,2);
}
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:04
===de_DE===
int main (int arg,char** argv){
setlocale(LC_NUMERIC,"de_DE");
printf("%d\n",12345678);
printf("%'d\n",12345678);
printf("%f\n",123456.78);
printf("%'f\n",123456.78);
printf("%1$d:%2$.*3$d\n",12,34,2);

}
Outputs are:12345678 12.345.678 123456,780000 123.456,780000 12:34
===zh_CN===
setlocale(LC_NUMERIC,"zh_CN"); only change to above code
Outputs are:12345678 12,345,678 123456.780000 123,456.780000 12:34
===Analysing results===
Look at all the locale source files, the results are resonable to us.

Feld
Posix
en_US
de_DE
zh_CN
decimal_point
"<U002E>"
"<U002E>"
"<U002C>"
"<U002E>"
thousands_sep
""
"<U002C>"
"<U002E>"
"<U002C>"
grouping
-1
3;3
3;3
3

Where "<U002E>" means "dot"; "<U002C>" means "comma".

Internationalization/posix locale

2006-09-04T08:45:26Z

Mingmei:

Internationalization/posix locale

2006-09-03T16:31:36Z

Mingmei:

User:Mingmei

2006-09-01T16:53:22Z

Mingmei:

hello everybody!

Now I am ready to work on this [[internationalization|semester thesis]]. Last two weeks I was working as interpreter at Alstom Power. It was a lot of fun, but it was also quite stressy.

我现在在做学期论文，论题是[[internationalization|国际化]]。上两周我在阿而斯通做技术翻译，紧张而有趣。

Internationalization

2006-09-01T16:34:30Z

Mingmei: new account for Hong

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

===Brief history===

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

==What is internationalisation?==

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

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

=== Specific goals of the semester project ===

''to be completed''

=Milestones=

''add milestones of semesterproject''

==Mx: ??? ==
* Write a summary of how [[Internationalization/posix_locale|POSIX locale]] information is stored
* Write a summary of how [[Internationalization/nls_locale|NLS (Windows) locale]] infomation is stored
* Write a summary of how [[Internationalization/dotnet_locale|.NET locale]] information is stored
* Write a small summary of date and time classes in EiffelBase
* Examine the .ts file format, notably plural form handling
* Examine the .xliff file format, notably plural form handling (we did some of this already)
* Enter classes & features into EiffelStudio so we have a starting point and a BON diagram
* Sit down and think about the current class names. Some of them need improving.

==M5: July ?? ==
* Refactoring of whole library
* Use our library for EiffelStudio
* Clean up Wiki and improve Developer manual
* Add support for other aspects of localisation - dates, number format etc. ''(possibly we can defer this a bit)''
** Compile a [[Internationalization/l10n_features | list of basic features]] to provide (e.g. date/time format, system locale) ''(deferred from M3)''

= Documentation =

* [[Internationalization/user_manual|User manual]]: how to use the i18n library
* [[Internationalization/developer_manual|Developer manual]]: developer manual for the i18n library
* [[Internationalization/obstacles|Obstacles]]: setbacks we have encountered

=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

== Semester project ==

* [[User:leo| Leo Fellmann]]
* [[User:etienner|Etienne Reichenbach]]
* [[User:Mingmei|Hong Zhang]]
* [[User:Trosim|Martino Trosi]]
* Supervisor: [[User:Schoelle| Bernd Schoeller]]

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

User:Mingmei

2006-09-01T16:31:27Z

Mingmei: link to my project

User:Mingmei

2006-09-01T16:28:20Z

Mingmei:

hello everybody!

Now I am ready to work on this semester thesis. Last two weeks I was working as interpreter at Alstom Power. It was a lot of fun, but it was also quite stressy.