Re: Revised proposal for "Missing character" glyph

2002-09-01 Thread David Hopwood
-BEGIN PGP SIGNED MESSAGE- "Michael (michka) Kaplan" wrote: > Not sure how this could be generally possible to restrict, since > WinNT/2K/XP/.Net all will transparently map CF_TEXT an CF_UNICODETEXT so > that if one if put on the clipboard and the other is asked for, you will get > it. "S

Re: Revised proposal for "Missing character" glyph

2002-09-01 Thread Doug Ewell
wrote: > A couple of corrections. First, if an app supports only WM_CHAR and > not also WM_UNICHAR, that does not imply that it uses a legacy > encoding. If running on NT/2K/XP and registered as a wide (Unicode) > app, the WM_CHAR messages will supply UTF-16 code units. If running > on Win9x/Me

Re: Revised proposal for "Missing character" glyph

2002-09-01 Thread Peter_Constable
On 08/31/2002 04:50:48 PM "Doug Ewell" wrote: >> Of course, one limitation is that apps can alter >> the data before they put it on the clipboard; in fact, an app might >> opt to convert everything to some default codepage and put only that >> on the clipboard. > >It would make sense for a Unico