Internationalization/obstacles - Revision history

Manus at 19:34, 31 October 2006

2006-10-31T19:34:46Z

Manus at 19:33, 31 October 2006

2006-10-31T19:33:44Z

Leo: added obstacle in ES

2006-10-21T23:33:11Z

added obstacle in ES

Leo at 02:11, 18 October 2006

2006-10-18T02:11:34Z

Etienner: small syntax fix

2006-06-29T17:08:49Z

small syntax fix

Carlo: added function arguments and case conversion problems in eStudio

2006-06-29T14:30:58Z

added function arguments and case conversion problems in eStudio

Carlo at 23:15, 27 June 2006

2006-06-27T23:15:27Z

New page

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

* Many strings are hard-coded anywhere inside EiffelStudio, making the translation difficult

← Older revision		Revision as of 19:34, 31 October 2006
Line 1:		Line 1:
−	~~[[Category:Projects]]~~
	[[Category:Internationalization]]		[[Category:Internationalization]]
	==Obstacles found during the semester project==		==Obstacles found during the semester project==

← Older revision		Revision as of 19:33, 31 October 2006
Line 1:		Line 1:
		+	[[Category:Projects]]
		+	[[Category:Internationalization]]
	==Obstacles found during the semester project==		==Obstacles found during the semester project==

← Older revision		Revision as of 23:33, 21 October 2006
Line 6:		Line 6:

	===EiffelStudio===		===EiffelStudio===
		+
		+	*Formatters require a certain property to be a lowercase string and read this directly from INTERFACE_NAMES, meaning that if the i18n library supplies a translated string that is not lowercase, an exception violation happens. This would superficially be relatively easy to fix, but it is not such a good idea to do this anyway, because with STRING_32 there may not even be a lowercase version of the string (asian scripts come to mind). This behaviour may also happen elsewhere, but I am not sure.

@@ Line 1: / Line 1: @@
-Problems we encountered during implementation
+==Obstacles found during the semester project==
 * 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:===
 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 the studio, these should have been implemented by the vision project and may be buggy.

@@ Line 8: / Line 8: @@
 * 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.
+* It seems that to_uppercase and to_lowercase procedures are not defined for STRING_32 and are used in the studio, these should have been implemented by the vision project and may be buggy.

← Older revision		Revision as of 14:30, 29 June 2006
Line 4:		Line 4:
	* Facilities to write and read STRING_32 to/from files were not present		* 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		* 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.