On Friday, July 18, 2003 10:18 PM, Michael Everson [EMAIL PROTECTED] wrote:
I *prefer* Unicode to any subset thereof.
Why such preference? Unicode does not define the charset (which are defined by
ISO10646), but character properties and related algorithms, and (in cooperation with
ISO10646)
At 15:23 +0200 2003-07-19, Philippe Verdy wrote:
Unicode does not define the charset (which are defined by ISO10646),
That isn't true. They both define the same character set. (I will not
use the term charset.)
but character properties and related algorithms, and (in cooperation
with ISO10646)
At 00:57 +0200 2003-07-18, Philippe Verdy wrote:
Why is row 03 so resticted? Shouldn't it include those accents and
diacritics that are used by other characters once canonically
decomposed? Or does it imply that MES-2 is only supposed to use
strings if NFC form?
Also, is this list under full
On Friday, July 18, 2003 7:36 AM, Michael Everson [EMAIL PROTECTED] wrote:
At 00:57 +0200 2003-07-18, Philippe Verdy wrote:
Why is row 03 so resticted? Shouldn't it include those accents and
diacritics that are used by other characters once canonically
decomposed? Or does it imply that
At 12:16 +0200 2003-07-18, Philippe Verdy wrote:
Is there some work at CEN to align its MES-2 subset into a revized
(MES-2.1 ???) which not only takes into consideration the ISO10646
reference but also its Unicode properties to make this set
self-closed, and actually implementable, at least
Philippe Verdy wrote:
MES-2 is a collection of characters independant of their actual
encoding.
To support MES-2 in a Unicode-compliant application, extra characters
need to be added, notably if the minimum requirement for information
interchange is the NFC form used by XML and HTML related
On Friday, July 18, 2003 12:42 PM, Michael Everson [EMAIL PROTECTED] wrote:
At 12:16 +0200 2003-07-18, Philippe Verdy wrote:
Is there some work at CEN to align its MES-2 subset into a revized
(MES-2.1 ???) which not only takes into consideration the ISO10646
reference but also its
At 13:35 +0200 2003-07-18, Philippe Verdy wrote:
I note that you prefer the European Multilingual Subset to MES-2.
Is it an extended set that includes MES-2, and fills the holes by
using all characters defined in blocks of some version of the
Unicode set?
It is script-based, not character
At 13:07 +0200 2003-07-18, Kent Karlsson wrote:
This is not to say that the MESes are unproblematic. To mention just
two points not already mentioned: none of the new math characters
are included even in MES-3 (a, b), despite that all math characters
were supposed to be included
That isn't true.
On Thursday, July 17, 2003 9:23 PM, Michael Everson [EMAIL PROTECTED] wrote:
At 17:01 +0100 2003-07-17, William Overington wrote:
Now, I have never heard of the MES-2 whatever that is. However, I
do not have deep knowledge of the various standards which exist.
Could you possibly say some
282 MES-2 is specified by the following ranges of code positions as
indicated for each row...
Philippe Verdy asked:
As most of these characters are canonically decomposable, shouldn't this
list include also the decomposed characters?
Why is row 03 so resticted? Shouldn't it include
On Friday, July 18, 2003 2:18 AM, Kenneth Whistler [EMAIL PROTECTED] wrote:
MES-2 was not designed by the UTC, nor did it take any of
these considerations into account. It is not really an
appropriate construct for the Unicode Standard. A more
meaningful way to think of it is: if you want to
12 matches
Mail list logo
