Re: [xml2rfc] [irsg] character sets, was UPDATE regarding <u>

Fred Baker <> Sat, 04 March 2023 18:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CA386C14CF09 for <>; Sat, 4 Mar 2023 10:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Status: No, score=-7.094 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gYNEYQFvr_X3 for <>; Sat, 4 Mar 2023 10:50:10 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::62c]) (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 (Postfix) with ESMTPS id 1D792C14CEED for <>; Sat, 4 Mar 2023 10:50:10 -0800 (PST)
Received: by with SMTP id h8so6092809plf.10 for <>; Sat, 04 Mar 2023 10:50:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677955809; h=to:references:message-id:cc:date:in-reply-to:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=6+MNaLt8qpQ41eu/Adtcs+AfiQOSxLzGY4SHdIy2lAo=; b=KED63T3Z/C2oCjPr3xQnPndj8fivMcz9CAk4pnUyEWF9Y3nD97UPFNzbTVj2F6hoVg crCgsVFg/98tT1p/zEf3EFQKbbg5oyFgszwjC4fsiGoIbNayor1zlSrDe0nG7gY7yFUl wnYgo3qxNYhHf1eGgzSRukRneqGXxFskcrDOcKjOD4XCs5D69E13GkjJRztP1uDdjWTE lO1lrg+AwYrav5qLv3FUo1j9v2JezqTnWBK7JKJmFBuUnXV0xi1mCzFty0VBsIfiCoFo tek6SI/fU2fQCrt0QSlD5ItQ0Ly1ehDF4+6SjvyvteYXNDq15QKM7v4vTQHSB1JtWLVo +52w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1677955809; h=to:references:message-id:cc:date:in-reply-to:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=6+MNaLt8qpQ41eu/Adtcs+AfiQOSxLzGY4SHdIy2lAo=; b=QpsR9c2xEozkSisINMoo8p9cyOzCvUOq+RXK/XgGJBZiKmOdx2Kb6VD7h8o8rF+A66 a9nQG/W+zarYnfU3MyeKC40Mf9lL2MnDN0t8W2KWtYqSfYC64SM/spUnCa53QwzTFoOM CQmCHV57hhj+z7+/QVY5y0xhBA16ITuxLTOIdOxMas6Jbkj9BBG7VnOwzEWyMHGU2+GI jCljT34R4MXD9vSiR2CYJT3fA7gq9BZH6TSpauaxqJHG/3qsW2oZsjme/PYMA7RMwdqg 8ZVu+K0iQl3QY/Cb2kADqPck60NprZXVLAngRP1b2D0ihO82C+u/GmJnwiyOoGXX7zPg PRRw==
X-Gm-Message-State: AO0yUKUN9doJWrwFtMsgytTgkIXk/u8dfU/kmOUZEBnRfBxmEbO2v5df MN/6wvs+Gz6rYIoYSKW+yWOHfT8scBw=
X-Google-Smtp-Source: AK7set9JoqKL1+F3PDMRvxiipXItfuuFmx77m0w+JiptdLoQQ2ITz663eiAvZb6pOQHMxh+6EhgJ0Q==
X-Received: by 2002:a05:6a20:1e4f:b0:cc:b5de:3037 with SMTP id cy15-20020a056a201e4f00b000ccb5de3037mr5191874pzb.51.1677955808942; Sat, 04 Mar 2023 10:50:08 -0800 (PST)
Received: from ([2600:8801:d605:5e00:a961:1ec5:2701:4c82]) by with ESMTPSA id k25-20020a63ba19000000b004facdf070d6sm3669766pgf.39.2023. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 04 Mar 2023 10:50:08 -0800 (PST)
From: Fred Baker <>
X-Google-Original-From: Fred Baker <>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
In-Reply-To: <>
Date: Sat, 04 Mar 2023 10:49:57 -0800
Cc: "John R. Levine" <>,
Message-Id: <>
References: <>
To: Carsten Bormann <>
X-Mailer: iPhone Mail (20D67)
Archived-At: <>
Subject: Re: [xml2rfc] [irsg] character sets, was UPDATE regarding <u>
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 04 Mar 2023 18:50:13 -0000

My name includes an umlaut, as yours does. “Juergens”. I might expect that this is reasonably common.

Sent using a machine that autocorrects in interesting ways...

> On Mar 4, 2023, at 8:38 AM, Carsten Bormann <> wrote:
> On 2023-03-04, at 16:46, John R Levine <> wrote:
>> In any event, this reminds us that we need some discipline in what we allow beyond letters and punctuation.  Unicode does not make this any easier by providing so many different glyphs that look nearly or exactly the same.
> Correct, except that the “allow” is a bit misplaced.  “Recommend”, “nudge authors towards”,  “consider good style” etc. would have worked better for me.
> Anyway, that’s why there is now authoring support in kramdown-rfc for character repertoire diagnostics, initially with the tool “echars” (which doesn’t require actually using markdown).  
> For those actually using markdown, eventually, I expect the yaml header to the markdown input to be able to carry a declaration of what non 10,32-126,160,8203,8209,8288 characters are actually desired in the input, so warnings can be emitted if the document isn’t staying inside those bounds.
> Both of these would be helped by access to information about the current repertoire limitations of xml2rfc, which is why I initiated this subthread.
> Grüße, Carsten
> _______________________________________________
> xml2rfc mailing list