Difference between revisions of "Talk:Migration to Unicode"
m (Some clarification on use of *_FILE_32 classes.) |
Colin-adams (Talk | contribs) (→Where is UTF_CONVERTER?: new section) |
||
| Line 9: | Line 9: | ||
As to using <e>*_FILE_32</e> classes, the only difference is the support of file names that use non-ASCII characters. Reading and writing the files is not affected. | As to using <e>*_FILE_32</e> classes, the only difference is the support of file names that use non-ASCII characters. Reading and writing the files is not affected. | ||
| + | |||
| + | == Where is UTF_CONVERTER? == | ||
| + | |||
| + | In which library is this class to be found? Is it available in 7.0? | ||
| + | --[[User:Colin-adams|Colin-adams]] 08:45, 26 September 2012 (UTC) | ||
Revision as of 23:45, 25 September 2012
Peter gummer 22:25, 25 September 2012 (UTC) These are interesting guidelines. Is this recommended already in EiffelStudio 7.1?
Our code currently uses STRING almost everywhere; the ECF maps STRING to STRING_8. Do the guidelines mean that we can change the ECF mapping from STRING to STRING_32? This would be much faster than editing every class individually.
The guidelines recommend using some *_FILE_32 classes. Most of our files are UTF-8, not UTF-32. Will using the *_FILE_32 classes work?
Alexander Kogtenkov 04:07, 26 September 2012 (UTC) This is a work in progress. Specifying mapping for the strings in an ECF might not work if application classes redefine features from the library classes.
As to using *_FILE_32 classes, the only difference is the support of file names that use non-ASCII characters. Reading and writing the files is not affected.
Where is UTF_CONVERTER?
In which library is this class to be found? Is it available in 7.0? --Colin-adams 08:45, 26 September 2012 (UTC)
