🚀 go-pugleaf

Thanks again .    :-))

� "Remy Lebeau (TeamB)" <gambit47@yahoo.com> ������ ��� ������
news:3eac3eff$1@newsgroups.borland.com...
>
> "MCh" <min_char@yahoo.gr> wrote in message
> news:3eac2fd4@newsgroups.borland.com...
> > If I create a RichEdit control using CreateWindow -in
> > runtime - ,will be possible to use Unicode characters in it?
>
> Yes, if you create the control using CreateWindowExW() and the
"RichEdit20W"
> class name.
>
> > Microsoft's RichEdit version 2 (Riched20.dll) supports unicode.
>
> Yes.  However, Microsoft does make the following comments about it that
you
> should be careful of:
>
>
>
http://msdn.microsoft.com/library/en-us/shellcc/platform/commctls/richedit/r
icheditcontrols/aboutricheditcontrols.asp
>
>     Rich Edit 2.0 includes the following features in addition to the
> features provided by Rich Edit Version 1.0.
>
>     Unicode
>     Unicode eases the effort in handling international text. However
effort
> is needed to maintain compatibility with existing non-Unicode
documents-that
> is, the ability to convert to/from non-Unicode plain and rich text. Also,
> substantial effort is needed to run correctly on Windows 95/98/Me.
>
>     In Rich Edit 2.0, if you create a Unicode rich edit control (one that
> expects Unicode text messages), you must specify only Unicode data in any
> window messages sent to the control. Similarly, if you create an ANSI rich
> edit control, send only ANSI or double-byte character set (DBCS) data. You
> can use the IsWindowUnicode function to determine whether a rich edit
> control uses Unicode text messages. Note that the rich edit COM interfaces
> use Unicode text unless they encounter a code page argument.
>
>
> Gambit
>
>