Talk:Migration to Unicode - Revision history

Alexander Kogtenkov: Added answer to the question "Where is UTF_CONVERTER?"

2012-09-26T09:19:19Z

Added answer to the question "Where is UTF_CONVERTER?"

← Older revision		Revision as of 09:19, 26 September 2012
Line 10:		Line 10:
	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? ==		'''[[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?

	~~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.
	--[[User:~~Colin-adams~~\|~~Colin-adams~~]] 08:45, 26 September 2012 (UTC)

Colin-adams: /* Where is UTF_CONVERTER? */ new section

2012-09-26T08:45:40Z

Where is UTF_CONVERTER?: new section

← Older revision		Revision as of 08:45, 26 September 2012
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)

Alexander Kogtenkov: Some clarification on use of *_FILE_32 classes.

2012-09-26T04:07:47Z

Some clarification on use of *_FILE_32 classes.

← Older revision		Revision as of 04:07, 26 September 2012
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.

Peter gummer: Questions about migration to Unicode

2012-09-25T22:25:44Z

Questions about migration to Unicode

New page

[[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.

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?