W3C home > Mailing lists > Public > public-ietf-collation@w3.org > September 2005

Re: comments on draft-newman-i18n-comparator-05.txt

From: Kent Karlsson <kentk@cs.chalmers.se>
Date: Fri, 23 Sep 2005 12:59:50 +0200 (CEST)
Message-ID: <20139.195.242.62.51.1127473190.squirrel@webmail.chalmers.se>
To: "Arnt Gulbrandsen" <arnt@gulbrandsen.priv.no>
Cc: public-ietf-collation@w3.org, "Philip Guenther" <guenther+collation@sendmail.com>

> Some collators don't operate on character strings. Ascii-numeric is a
> case in point. Those have to parse the parse the octet string and work
> on the resulting value.

"ASCII-numeric"?

Anyhow, ISO/IEC 14651, Annex C, has a section on numeric ordering
(on natural numbers, integer numbers, and numbers with fractions or
even exponent parts), expressed as prehandling on the string prior
to comparison.

> Cyrus Daboo mentioned a collator which sorts dates. That collator has to
> specify a date format (perhaps by reference), parse that format, and
> sort/compare the dates in its internal format.

ISO/IEC 14651, Annex C, has a section on date ordering
(and the "date parser" may well recognise several date formats,
as long as there is no ambiguity), expressed as prehandling
on the string prior to comparison.

Done that way, there is no need to mix in other datatypes than
character strings; like <some characters, a date object, maybe
some more characters, an integer value object (or a floating
point value object), more characters>.

Specifying which prehandlings to do is out of scope for 14651,
but it may well be in scope for an i-d.

     /kent k
Received on Friday, 23 September 2005 11:00:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:54 GMT