IETF Logo Mail Archive

Re: [I18ndir] [art] Just uploaded draft-bray-unichars-03

Carsten Bormann <cabo@tzi.org> Mon, 11 September 2023 15:44 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D366C14CE39; Mon, 11 Sep 2023 08:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1EMSgP2_e_I; Mon, 11 Sep 2023 08:44:30 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D84ACC14CE2B; Mon, 11 Sep 2023 08:44:25 -0700 (PDT)
Received: from smtpclient.apple (unknown [91.223.100.59]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RkrcQ4T4KzDCdF; Mon, 11 Sep 2023 17:44:22 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-EE667806-2470-4811-9C1E-CD8ABF8079A9"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3477e8e0-558c-8cbb-c282-ca70bf1467ae@ix.netcom.com>
Date: Mon, 11 Sep 2023 17:44:10 +0200
Cc: "Manger, James" <James.H.Manger@team.telstra.com>, Tim Bray <tbray@textuality.com>, i18ndir@ietf.org, ART Area <art@ietf.org>
Message-Id: <B34A53A3-02DE-4CF8-A58D-92CE01B92137@tzi.org>
References: <3477e8e0-558c-8cbb-c282-ca70bf1467ae@ix.netcom.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
X-Mailer: iPhone Mail (20G81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/D-dQBhTs5-upjh1Jwk2tJpyRnNw>
Subject: Re: [I18ndir] [art] Just uploaded draft-bray-unichars-03
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2023 15:44:32 -0000

The repertoire discussion actually is an interesting and useful one. The main point of modern network Unicode was to offer suggestions on repertoire, not based on historical mistakes (these can almost never be truly fixed), but on Design considerations that apply now and in the foreseeable future, helping designers to avoid repeating rookie mistakes. 

I would love to have this discussion, but not mixed up with apologetics for dumping out toxic waste into all protocols.  I would also like to separate the discussion of interchanging days items with Unicode semantics from the discussion of representing Unicode in ascii escape sequences (there is an rfc for the latter, bcp 137 = rfc 5137, which maybe could do with a update). 

Sent from mobile, sorry for terse

v2.23.0 | Report a Bug | By Email