Talk:Internationalization/locale - Revision history

Cconti at 14:54, 23 June 2006

2006-06-23T14:54:43Z

Cconti at 14:49, 23 June 2006

2006-06-23T14:49:09Z

Carlo: formatting

2006-06-22T21:40:28Z

formatting

Carlo at 21:23, 22 June 2006

2006-06-22T21:23:18Z

Cconti at 15:13, 22 June 2006

2006-06-22T15:13:23Z

Cconti at 15:10, 22 June 2006

2006-06-22T15:10:36Z

Cconti at 15:07, 22 June 2006

2006-06-22T15:07:24Z

Cconti at 15:06, 22 June 2006

2006-06-22T15:06:57Z

Carlo at 22:31, 18 June 2006

2006-06-18T22:31:25Z

Carlo at 22:30, 18 June 2006

2006-06-18T22:30:36Z

New page

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)

@@ Line 26: / Line 26: @@
 :: There is already a feature in eiffel that gets the environment variables, it's called get (in class EXECUTION_ENVIRONMENT)
+:: There is a big problem on windows with the macro (at least on my laptop):
---[[User:Cconti|Cconti]]
+:: if I run the program step by step eiffel crashes when it arrives at the macro

← Older revision		Revision as of 14:49, 23 June 2006
Line 23:		Line 23:

	: 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)		: 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)
		+
		+
		+	:: There is already a feature in eiffel that gets the environment variables, it's called get (in class EXECUTION_ENVIRONMENT)
		+
		+	--[[User:Cconti\|Cconti]]

@@ Line 17: / Line 17: @@
 "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)
-−
 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)
+: 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)

← Older revision		Revision as of 21:23, 22 June 2006
Line 20:		Line 20:

	--[[User:Cconti\|Cconti]]		--[[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)

@@ Line 16: / Line 16: @@
 just to be clear:
 "it" is not sufficient, we need "it_ch" to have complete information
 --[[User:Cconti|Cconti]]

← Older revision		Revision as of 15:10, 22 June 2006
Line 9:		Line 9:

	Feel free to add them to the article.		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 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)?

@@ Line 10: / Line 10: @@
 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]]

← Older revision		Revision as of 15:06, 22 June 2006
Line 5:		Line 5:

	(these notes should be added to the article) --[[User:Carlo\|Carlo]] 00:30, 19 June 2006 (CEST)		(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]]

← Older revision		Revision as of 22:31, 18 June 2006
Line 1:		Line 1:
−	At present we are using [http://en.wikipedia.org/wiki/ISO_639 ISO 639] to identify the languages.	+	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.		[http://www.unicode.org/onlinedat/languages.html Here] is a list of correspondences between different coding conventions.