Difference between revisions of "Talk:Migration to Unicode"
Peter gummer (Talk | contribs) (Questions about migration to Unicode) |
m (Added answer to the question "Where is UTF_CONVERTER?") |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[User:Peter gummer|Peter gummer]] 22:25, 25 September 2012 (UTC) These are interesting guidelines. Is this recommended already in EiffelStudio 7.1? | + | '''[[User:Peter gummer|Peter gummer]] 22:25, 25 September 2012 (UTC)''' These are interesting guidelines. Is this recommended already in EiffelStudio 7.1? |
Our code currently uses <e>STRING</e> almost everywhere; the ECF maps <e>STRING</e> to <e>STRING_8</e>. Do the guidelines mean that we can change the ECF mapping from <e>STRING</e> to <e>STRING_32</e>? This would be much faster than editing every class individually. | Our code currently uses <e>STRING</e> almost everywhere; the ECF maps <e>STRING</e> to <e>STRING_8</e>. Do the guidelines mean that we can change the ECF mapping from <e>STRING</e> to <e>STRING_32</e>? This would be much faster than editing every class individually. | ||
The guidelines recommend using some <e>*_FILE_32</e> classes. Most of our files are UTF-8, not UTF-32. Will using the <e>*_FILE_32</e> classes work? | The guidelines recommend using some <e>*_FILE_32</e> classes. Most of our files are UTF-8, not UTF-32. Will using the <e>*_FILE_32</e> classes work? | ||
| + | |||
| + | '''[[User:Alexander Kogtenkov|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 <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. | ||
| + | |||
| + | '''[[User:Colin-adams|Colin-adams]] 08:45, 26 September 2012 (UTC)''' ''Where is <e>UTF_CONVERTER</e>?'' In which library is this class to be found? Is it available in 7.0? | ||
| + | |||
| + | '''[[User:Alexander Kogtenkov|Alexander Kogtenkov]] 09:19, 26 September 2012 (UTC)''' <e>UTF_CONVERTER</e> is not available in 7.0. Most probably it will be included in EiffelBase. | ||
Latest revision as of 01:19, 26 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.
Colin-adams 08:45, 26 September 2012 (UTC) Where is UTF_CONVERTER? In which library is this class to be found? Is it available in 7.0?
Alexander Kogtenkov 09:19, 26 September 2012 (UTC) UTF_CONVERTER is not available in 7.0. Most probably it will be included in EiffelBase.
