Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

On Mon, Sep 25, 2006 at 11:07:32AM -0700, Lisa Dusseault wrote: > > On Sep 23, 2006, at 2:20 AM, Julian Reschke wrote: > > > > >But as a matter of fact, draft-newman-i18n-comparator-14 doesn't > >define any collations that would actually solve the Unicode NF > >issue, so it's not really clear

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

I've got a "very liberal" comparator in production at the Linux Counter project. It mostly works, because the people who assign names tend to not assign names that collide under the comparator. But the strings that result from the comparator are quite distant from "expected" strings in many c

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

--On Monday, 25 September, 2006 11:07 -0700 Lisa Dusseault <[EMAIL PROTECTED]> wrote: > On Sep 23, 2006, at 2:20 AM, Julian Reschke wrote: >> But as a matter of fact, draft-newman-i18n-comparator-14 >> doesn't define any collations that would actually solve the >> Unicode NF issue, so it's

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

Lisa Dusseault wrote: > one could define a Very Liberal Comparator (VLC) for general > use. It would be handy to have one which matched e with E, > é, è É... and matched o with O, ø, ô, and so on. Good idea. I'm thinking of something in that direction for my mail filters: At the moment any ty

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

Lisa Dusseault writes: Last week Ted & I were discussing whether one could define a Very Liberal Comparator (VLC) for general use. It would be handy to have one which matched e with E, é, è É... and matched o with O, ø, ô, and so on. That would help in calendar searching use cases, e.g. a user

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

On Sep 23, 2006, at 2:20 AM, Julian Reschke wrote: But as a matter of fact, draft-newman-i18n-comparator-14 doesn't define any collations that would actually solve the Unicode NF issue, so it's not really clear how this helps CalDAV (except that it now uses a framework in which the solut

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

> "Julian" == Julian Reschke <[EMAIL PROTECTED]> writes: Julian> But as a matter of fact, draft-newman-i18n-comparator-14 Julian> doesn't define any collations that would actually solve Julian> the Unicode NF issue, so it's not really clear how this Julian> helps CalDAV (except

Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

Julian Reschke writes: Maybe the set of initial registrations in needs to be extended? Two more used to be there, but I split them off for various reasons and will them as submit them as separate drafts. As it is, the docu

Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

Hi, I notice that draft-dusseault-caldav-15 now delegates part of the text matching semantics to draft-newman-i18n-comparator-14, which probably is a good thing. As far as I can tell, this change was made in following up to Sam H's comments in