IETF Logo Mail Archive

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

Sam Hartman <hartmans-ietf@mit.edu> Sun, 24 September 2006 18:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GRYn4-0002nj-Am; Sun, 24 Sep 2006 14:33:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GRYn2-0002nS-Jl; Sun, 24 Sep 2006 14:33:20 -0400
Received: from c-66-30-121-250.hsd1.ma.comcast.net ([66.30.121.250] helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRYn1-0007YP-De; Sun, 24 Sep 2006 14:33:20 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 16030E0127; Sun, 24 Sep 2006 14:33:15 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Julian Reschke <julian.reschke@gmx.de>
References: <4514FC44.5090204@gmx.de>
Date: Sun, 24 Sep 2006 14:33:15 -0400
In-Reply-To: <4514FC44.5090204@gmx.de> (Julian Reschke's message of "Sat, 23 Sep 2006 11:20:04 +0200")
Message-ID: <tsly7s9cdxw.fsf@cz.mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: ietf@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

>>>>> "Julian" == Julian Reschke <julian.reschke@gmx.de> 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 that it now uses a framework in which
    Julian> the solution may become available in the future).

Yep, but at least it points to a solution.  I'd be much happier if
there was a mandatory colation that was a good fit for international
calendar usage.  I understand thogh that we have to balance forward
progress against forcing people to solve everything all at once.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email