Re: Microsoft Layer for Unicode on Windows 95/98/Me systems

Sam Hobbs <samuel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im Beitrag
<OZ7FTePVFHA.2616@xxxxxxxxxxxxxxxxxxxx>...
> Yes, VB has little support of external representation of characters.
Windows
> however does and VB depends on Windows to draw the characters. In other
> words, Windows provides fonts that provides external representation of
> characters.

Please read the postings of mine more carefully:

"- Codepoint conversion from upper to lower case and vice versa
- Codepoint sorting
- Codepoint properties
- Codepoint composition and decomposition"

These are examples I have listed for missing Unicode support in VB. I did
not talk about "external representation of characters" (maybe you are
mixing some postings of others in this thread up with the postings of
mine).

But if you want to talk about external representation:

With this VB lacks Unicode support completely! The standard controls
shipped with VB are alltogether >not< Unicode enabled.

> Most fonts provided by Windows are not Unicode fonts, but Windows can
> convert Unicode characters (code points) to characters in the fonts. It
is
> not necessary for VB to do that; therefore it is unreasonable to expect
VB
> to do that.

Again: Most fonts provided by Windows (since 95) are indeed 'Unicode fonts'
or - better - do include Unicode character encoding tables! And Windows
(since 95) is able to make use of these character encoding tables and to
draw Unicode encoded texts.
But to allow Windows to do so the respective application has to use the
relevant functions, i.e. the "W" versions of them. And this is what the
standard controls shipped with VB are not doing. So, VB is the one that
indeed lacks the necessary Unicode support.

--
----------------------------------------------------------------------
THORSTEN ALBERS Universität Freiburg
albers@
uni-freiburg.de
----------------------------------------------------------------------

.

Relevant Pages

  • Re: Unicode Support
    ... >> (I know this is a poor example, but think about other languages, eg ... First things first, when you register your RosAsm windows classes, you ... the messages with ANSI / UNICODE parameters in ANSI or UNICODE form... ... with their alphabet characters, as with the numbers and punctuation...so, ...
    (alt.lang.asm)
  • Re: Filename Encoding Help
    ... I suggest UTF-8, it's the most efficient for regular text, and it's the default for all methods reading and writing text files in .NET. ... UTF-16 but I am not sure what Windows Vista does. ... UTF-8 can represent the full Unicode spectrum, but many characters wind up encoded in just one or two bytes. ...
    (microsoft.public.dotnet.framework)
  • Re: _mbslen vs strlen
    ... My Windows application was unicode ... The length in characters, ... C++ on Linux has wide character characters as well as single byte ...
    (comp.os.linux.development.apps)
  • Re: _stprintf
    ... Some versions of Windows implement DBCS, apparently the Japanese version of Windows had ... This also means that if you are using Unicode to represent Kanji, ... to use MAX_PATH Kanji characters to name a file. ...
    (microsoft.public.vc.mfc)
  • =?windows-1252?Q?Re=3A_Encrypting_Unicode_=96_Using_ASCII_as_a_Surrogat?= =?windows-1252?Q?e
    ... characters of an exotic eastern language using an ASCII keyboard. ... communicate in large volume with China or Japan using CJK from Unicode ... present the message text to Alice as a string of hexadecimal numbers ... by the computer as an external file and enciphered by a stream cipher ...
    (sci.crypt)