Difference between revisions of "Internationalization/obstacles"
(added function arguments and case conversion problems in eStudio) |
|||
| 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. | ||
Revision as of 06:30, 29 June 2006
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.
