Re: [I18ndir] [art] Fwd: New Version Notification for draft-bray-unichars-04.txt

Steffen Nurpmeso <steffen@sdaoden.eu> Tue, 19 September 2023 22:37 UTC

Return-Path: <steffen@sdaoden.eu>
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 04CC8C1519AC; Tue, 19 Sep 2023 15:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 TIpOL_X1kDqU; Tue, 19 Sep 2023 15:37:26 -0700 (PDT)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (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 4C5E4C1519AD; Tue, 19 Sep 2023 15:37:24 -0700 (PDT)
Date: Wed, 20 Sep 2023 00:37:20 +0200
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Asmus Freytag <asmusf@ix.netcom.com>
Cc: Rob Sayre <sayrer@gmail.com>, "Manger, James" <James.H.Manger=40team.telstra.com@dmarc.ietf.org>, Tim Bray <tbray@textuality.com>, ART Area <art@ietf.org>, "i18ndir@ietf.org" <i18ndir@ietf.org>, Steffen Nurpmeso <steffen@sdaoden.eu>
Message-ID: <20230919223720.2qiHP%steffen@sdaoden.eu>
In-Reply-To: <1d19f72f-8c41-f10c-831c-8e5cea347478@ix.netcom.com>
References: <169479938668.18742.9199862891950651366@ietfa.amsl.com> <CAHBU6ivzUV947N+n7AoYkCFT3ZfaLobCQ4fBXw3dvkqTT=LBAw@mail.gmail.com> <SY4PR01MB5980D8DDE229D1C57AEDFB55E5FBA@SY4PR01MB5980.ausprd01.prod.outlook.com> <CAChr6SzRa8F+OrELa8N3rAMLmxdvr-g5c0i_9ESnWnwZY-iA4A@mail.gmail.com> <CAChr6Sy05spOW9nsy36kYr8Ob6OYS7vCgrEVPhhWs9Pe4LkpNA@mail.gmail.com> <2e6c2d13-9fc9-d320-3803-2b9a4df3b042@ix.netcom.com> <CAChr6Swr5tS2-wW8dZ0A4J7_Jd+RoHZNJkzhNfcVTi84oDvOPA@mail.gmail.com> <1d19f72f-8c41-f10c-831c-8e5cea347478@ix.netcom.com>
Mail-Followup-To: Asmus Freytag <asmusf@ix.netcom.com>, Rob Sayre <sayrer@gmail.com>, "Manger, James" <James.H.Manger=40team.telstra.com@dmarc.ietf.org>, Tim Bray <tbray@textuality.com>, ART Area <art@ietf.org>, "i18ndir@ietf.org" <i18ndir@ietf.org>, Steffen Nurpmeso <steffen@sdaoden.eu>
User-Agent: s-nail v14.9.24-510-g0c7d0ca1b7
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/4p-fGyJq6iCVYkAmnBRp6_jNO4w>
Subject: Re: [I18ndir] [art] Fwd: New Version Notification for draft-bray-unichars-04.txt
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: Tue, 19 Sep 2023 22:37:27 -0000

Asmus Freytag wrote in
 <1d19f72f-8c41-f10c-831c-8e5cea347478@ix.netcom.com>:
 ...
 |The disconnect may be that Unicode needs to define "string" in ways that 
 |are not limited to interchange.
 |
 |A string data type may transiently be in state that is not well-formed, 
 |or may be able to hold ill-formed input data before verifying its status.
 |
 |Unicode, in other words, has to be universal covering ALL possible uses 
 |of a "string". The same is not true for a protocol that defines a record 
 |with data fields. Those fields don't need to be able to accommodate 
 |ill-formed data.
 |
 |The exception might be a protocol that is "just a pipe". In that case, 
 |the responsibility for enforcing well-formedness belongs to (usually) 
 |the receiver connected to that "pipe". Such a protocol may well want to 
 |allow "all unicode code points".

Another thought i had during this thread.
Here in Hesse[n] Germany, already over 90 years ago, and
occasionally ever since, often in the say last 25 years, the
Rechnungshof (audit court) urged to care for the countryside
(besides the usual wastefulness), aka denounced the disparity.
(Leading to real desertification, and villages without bank,
doctor, even bakeries etc.)
Finally, a few years back, politics listened and actively started
to work the topic.  As a result there now is a law which says the
same.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)