IETF Logo Mail Archive

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

Rob Sayre <sayrer@gmail.com> Sun, 10 September 2023 07:06 UTC

Return-Path: <sayrer@gmail.com>
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 2CDCCC1519BD; Sun, 10 Sep 2023 00:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cK4Bu7iEKOre; Sun, 10 Sep 2023 00:06:12 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 6CB88C1519A0; Sun, 10 Sep 2023 00:06:12 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-52f33659d09so885596a12.1; Sun, 10 Sep 2023 00:06:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694329570; x=1694934370; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=N2TyVbhmWf7OnubzAppSZG9SXFXDib6LcW9zGyD/XxY=; b=LCxLxezF5SpnjX93XofIZF5MMVZNfZUJhXnCmaK/tgxPFz6FadP0qutPkiWZmqe5GG tkxE2kjCa15odS5/RjfQEfJrN3BQ7G1YLfV95VQnj9MmCbm0fnJ50O33YrqrleBAmqFm VVw3JgvHsWqbRsz7a5Z/e3NKYznrczhwoVE5voprepVJm835+UCDOoxaCBByiNyBCapZ fWnBqzQFw8lnmBjS7rro4RzS8h1adIeJ8Bgm4/sR5lKyjardZmpZr5Mh6KB1DbUWOefl fi8z/ZvBmu+im1JQbuOW6tOTyrLcl4ylUMd3W0z7XDfcvwFAFaDjmXS2InJwhGLEo2B2 WOhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694329570; x=1694934370; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=N2TyVbhmWf7OnubzAppSZG9SXFXDib6LcW9zGyD/XxY=; b=D29zNrncBldPY7spm2wsxgEGF8VRx1Q1ouKtKUwiGyiuhIRJxfd7b2II4rICUAge92 RxaUMvMnhyoLq/CMi84w0cHAdKl8BuH+739FUEVONd/cCtTkv8TIdbaa/9cYbML/6vHJ mUqS4VTVapCtsCTr3nPqBvY+LSvzFmpdUfx60IXL0CTTHCvfCp9bJ5OEo23Pb4LEfpwr KWGR3HCtdAwtAJwO+k6bcdOsVQrTUXD668pG5w3vuhaGxIozVi4JHjNtwfeug6JGHdo5 RcjPWe/PPDTPzyxP2kuiqamWI0GCZJFQS95H/6VTz6ROlX7U7IOfx71oa/0v8J62FkdG TKhg==
X-Gm-Message-State: AOJu0YwH/lNs54YmFUvd1dZhZUmExM9+bX/gWnNy3g6q+YNXcEmqfa8b HP1FpTdN+rhZl+446rEA2Z+L5Je0K77+P8P0RVY=
X-Google-Smtp-Source: AGHT+IH+9tVNMsVzXHLbvqwEtQrl+7dm0l2XK7Lv9txz+3KrdJpPFBXoulRHkeI74qaCUrvAQ1pJ2Wi/xXz2hEXPwIw=
X-Received: by 2002:aa7:d1d2:0:b0:523:c10d:1d5b with SMTP id g18-20020aa7d1d2000000b00523c10d1d5bmr5587015edp.37.1694329569829; Sun, 10 Sep 2023 00:06:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAHBU6is50TkpDsqXTp6WxdVSgE66j3gGHZ60ey2jFYbefaHFJw@mail.gmail.com> <20230909165843.GlTJy%steffen@sdaoden.eu> <CAHBU6iuixTeS=X1kccw11zEnHVG5tx9aHUC-pH00ociBmukhGQ@mail.gmail.com> <d9d5dee0-24d1-54f0-dde9-4bb9ad2e56e7@ix.netcom.com>
In-Reply-To: <d9d5dee0-24d1-54f0-dde9-4bb9ad2e56e7@ix.netcom.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Sun, 10 Sep 2023 00:05:58 -0700
Message-ID: <CAChr6Sygs5=fyQ7ZJSVoV5EY9hDZWRkj78r9yH2539vtNTT=aQ@mail.gmail.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
Cc: Tim Bray <tbray@textuality.com>, Steffen Nurpmeso <steffen@sdaoden.eu>, i18ndir@ietf.org, ART Area <art@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002465f70604fbd872"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/b-NrAr_ZeiJGkc7Z5rRD-Wq9inY>
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: Sun, 10 Sep 2023 07:06:14 -0000

>
>
> And then in 8.
>>
>>  8.  String and Character Issues
>>  8.1.  Character Encoding
>>     JSON text exchanged between systems that are not part of a
>>     closed ecosystem MUST be encoded using UTF-8 [RFC3629].
>>
>
> As Rob Sayre said above, the proposed document probably has to address the
> issue of JSON escapes and emphasize that they are not relevant to code
> point subsets.
>
> No they are. If you are in a JSON-based environment, but have restricted
> your repertoire, then even if JSON allows an escape, it's invalid if it
> violates your restriction. And your new specification SHOULD require
> something definite and drastic to happen in that case.\
>

That is exactly the point. The current draft mentions "Transformation
Formats", but doesn't mention that these transformation formats can and do
further encode questionable Unicode via escape sequences. The draft should
mention it.

Unfortunate, but true. So, you can have a perfect UTF-8 document that
represents a bunch of unpaired surrogate code points.

thanks,
Rob

v2.23.0 | Report a Bug | By Email