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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"Thorsten Albers" <albersRE@xxxxxxxxxxxxxxxxxxx> wrote in message
news:01c55cc4$cf7628e0$LocalHost@xxxxxxxxxxx
>
> Yes, >some<, but no upper case to lower case conversion etc.

Then I don't understnad. What does StrConv(..., vbUpperCase) and
StrConv(..., vbLowerCase) do that is not "upper case to lower case
conversion"?

> What can be converted depends on what code page
> and Unicode support is installed on the OS.

Yes, that is what I am trying to say.

> This conversion has nothing to do with conversion from upper to lower case
> (and vice versa) or code point sorting...

When you say sorting, do you mean that VB does not have a sort function or
statement? Or are you saying that when it sorts, it sorts incorrectly?

>> > - Codepoint properties
>> > - Codepoint composition and decomposition"
>> I am not sure I understand what you mean, but if I understand then they
> are
>> either font-dependent or are defined by the Unicode standard. It seems
>> reasonable to me that they are not part of the language.
>
> They are part of the Unicode standard, and for Unicode support they are of
> basic significance. Since VB does not support this part of the Unicode
> standard, it does not implement real Unicode support.

I still don't know what codepoint properties, composition and decomposition
are, but I don't remember what I meant when I said that they are defined by
the Unicode standard. In other words, I seem to have implied that being part
of the standard makes it unnecessary for VB to support them, and that is
certainly foolish. I will try to remember to look up codepoint properties,
composition and decomposition.

> No (.NET?). But that is not the point: The question was if VB has real
> Unicode support implemented. And is hasn't, no matter if other computer
> languages have or not.

I consider the fact that other languages (including Java and ECMAScript) do
not have the support you are describing to be significant. Note that C# is
also an ECMA standard, so I am interested in knowing if it has the support.
I will assume it does not, but I know that neither of us know. Assuming that
C# also does not have the support, there are good reasons why the languages
don't have the support. Regardless, if the other languages do not have the
support, it is unreasonable to expect VB to have the support.

The C# standard is at:
http://www.ecma-international.org/publications/standards/Ecma-334.htm

> a) The MS Forms are not allowed to be redistributed.

> b) The fully Unicode enabled MS Forms are not installed with VB but with
> MS
> Office products (see above!).

There is an official, documented way to install the forms controls free of
charge. It is in one of the KB articles I referenced.

> c) MS Forms is not designed for use in VB and may cause major problems
> when
> used in VB.

Yes. The important point is that it is possible to use a control for Unicode
characters. I stated explicitly that it would be better to use another
control (or set of controls).

> MS Forms again has nothing to do with the Unicode support of VB.

Yes, they do, to the extent that Unicode is supported but not by VB. In
other words, the fact that MS Forms provide the ability but they are
separate from VB shows that the separaration of the functions is logical.


.

Relevant Pages

  • Re: Factory Pattern
    ... It has the ISO standard and surely will be revised. ... Now imagine that C introduces support for Unicode in names. ... and the binary symbol names will stay Latin1 ...
    (comp.lang.ada)
  • Re: Factory Pattern
    ... It has the ISO standard and surely will be revised. ... Now imagine that C introduces support for Unicode in names. ... and the binary symbol names will stay Latin1 ...
    (comp.lang.ada)
  • Re: R6RS mail archives, formal comments, next r6rs draft
    ... They can just use the reference ... not require support for Unicode case conversion. ...
    (comp.lang.scheme)
  • Re: Most Komplex Kanji ?
    ... But those aren't the reasons you post ... >> in unicode. ... > support every language on the planet in a single standard. ...
    (sci.lang.japan)
  • Re: R6RS mail archives, formal comments, next r6rs draft
    ... They can just use the reference ... not require support for Unicode case conversion. ...
    (comp.lang.scheme)