[Ltru] Re: UTF-8

Frank Ellermann <nobody@xyzzy.claranet.de> Sat, 16 September 2006 10:44 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GOXeS-0008MZ-BK; Sat, 16 Sep 2006 06:44:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GOXeR-0008MO-73 for ltru@lists.ietf.org; Sat, 16 Sep 2006 06:43:59 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GOXeM-0006VZ-Nn for ltru@lists.ietf.org; Sat, 16 Sep 2006 06:43:59 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GOXeJ-000547-P6 for ltru@lists.ietf.org; Sat, 16 Sep 2006 12:43:51 +0200
Received: from pd9fba8e3.dip0.t-ipconnect.de ([217.251.168.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 16 Sep 2006 12:43:51 +0200
Received: from nobody by pd9fba8e3.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 16 Sep 2006 12:43:51 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 16 Sep 2006 12:34:47 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 56
Message-ID: <450BD347.9EA@xyzzy.claranet.de>
References: <789E617C880666438EDEE30C2A3E8D10EEFC@mailsrvnt05.enet.sharplabs.com> <450B2B75.2F36@xyzzy.claranet.de> <6.0.0.20.2.20060916114849.081056e0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: pd9fba8e3.dip0.t-ipconnect.de
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc:
Subject: [Ltru] Re: UTF-8
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Martin Duerst wrote:

  [UTF-8 registry]
>> I'm opposed.
> It would be good to know why.

ftp://ftp.iana.org/assignments/language-subtag-registry

I've no clue what FTP clients would do with something like
that.  John's "net-UTF-8" draft isn't ready, and I had some
troubles to understand his last published version.

Another issue are fonts, for RFC 4646 there were proposals
to restrict the registry to Latn.  Fortunately that was
dropped, because the problem doen't exist with US-ASCII
plus NCRs.

> something like Bokm&#xE5;l is just plain annoying.

At least we know what this is.  Bokmål is less clear -
raw UTF-8 displayed as Latin-1, http://purl.net/net/ucode/E5

> I'm sure the logistic problems with IANA can be sorted
> out (e.g. using attachments).

Yes.  I doubt that there is any logistic problem for mail
submissions.  Only for the bulk update, the fattest I-D in
the history of the Internet using B64, they'd shoot us.

We could try QP, and silently send them Doug's original
data (as mail) in addition to the I-D.  But as you said,
that can be sorted out, it's not the reason why I prefer
to stick to the format as is.

We've no clear idea which tools will exist for the 4646
format in six months, how they do their updates (http or
ftp), and what local conversions they use.  Doug already
proposed that an UTF-8 version might have to keep the
&amp; convention, that could be confusing.  And we'd have
to decide if a signature is required, another change of
the record-jar ABNF.

> compression, this can be done mostly transparently.
> browsers tell servers what encodings they support, e.g.
> like so:
> Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0

ACK, I forgot this, my favourite browser uses HTTP/1.0 ;-)

An explicit gzip variant could still make sense for ftp
and HTTP/1.0 (?)  We can add some "IANA might consider to
offer" blurb in the IANA considerations, but IMO we can't
tell them how to run their servers.

Frank



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