Internationalization/obstacles: Difference between revisions
Jump to navigation
Jump to search
m small syntax fix |
No edit summary |
||
| Line 1: | Line 1: | ||
Problems we encountered during implementation | ==Obstacles found during the semester project== | ||
===Library=== | |||
No significant problems. There were some slight hiccups with UTF-16, as the gobo parser expects a BOM and so cannot parse UTF16LE or UTF-16BE. Unluckily for us, windows uses little-endian UTF-16. | |||
===EiffelStudio=== | |||
==Problems encountered during the SA project== | |||
===Problems we encountered during implementation=== | |||
* Unicode (UTF-8) support was not fully implemented (e.g. for gtk) | * 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 | * 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 | * 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. | * 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. | * 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. | ||
Revision as of 02:11, 18 October 2006
Obstacles found during the semester project
Library
No significant problems. There were some slight hiccups with UTF-16, as the gobo parser expects a BOM and so cannot parse UTF16LE or UTF-16BE. Unluckily for us, windows uses little-endian UTF-16.
EiffelStudio
Problems encountered during the SA project
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 the studio, these should have been implemented by the vision project and may be buggy.