Paul Dempsey replied to me:
> > [T]he Sam editor [...] correctly puts the
> > UCS-2 format under CF_UNICODE, but the CF_TEXT format holds UTF-8 text,
> > Sam's native format.
> That is an incorrect use of the CF_TEXT format. No windows application will
> expect UTF-8 in CF_TEXT. They will expect text in the system codepage.
Absolutely. My point is that the mere fact of setting CF_UNICODE
does not constrain CF_TEXT, nor vice versa, contrary to the statement
in _Developing International Software_ previously quoted:
# Any text
# copied to the clipboard is enumerated in all three
# formats, so it's possible to cut and paste across
# applications supporting different character sets.
-- John Cowan http://www.ccil.org/~cowan email@example.com You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (FW 16.5)
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:39 EDT