RichEdit and Unicode

Thread View: borland.public.cppbuilder.nativeapi

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by MCh Sun, 27 Apr 2003 19:30

#16755

Author: MCh
Date: Sun, 27 Apr 2003 19:30

6 lines
1096 bytes

If I create a RichEdit control using CreateWindow -in runtime - ,will be
possible to use Unicode characters in it?
Microsoft's RichEdit version 2 (Riched20.dll) supports unicode.
Is it right.?

I use C++ builder 5 pro xp greek.

Re: RichEdit and Unicode

#16757

Author: Remy Lebeau (TeamB)
Date: Sun, 27 Apr 2003 20:36

36 lines
2488 bytes

"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/richeditcontrols/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

Re: RichEdit and Unicode

#16758

Author: MCh
Date: Sun, 27 Apr 2003 21:33

48 lines
2799 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads