IETF Logo Mail Archive

Re: [rfc-i] Unicode names in RFCs and xml2rfc

"Martin Thomson" <mt@lowentropy.net> Wed, 04 December 2019 10:20 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840F512022A for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Dec 2019 02:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.75
X-Spam-Level:
X-Spam-Status: No, score=-4.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=lowentropy.net header.b=pJsbzI9Z; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=uNBbl54w
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjf67Y76637g for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Dec 2019 02:20:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4242B120131 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 4 Dec 2019 02:20:37 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C9625F40712; Wed, 4 Dec 2019 02:20:34 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2B4E5F40712 for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 02:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=pJsbzI9Z; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=uNBbl54w
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp5j1Yv5JuB2 for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 02:20:31 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by rfc-editor.org (Postfix) with ESMTPS id A68EEF40711 for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 02:20:31 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8D6E722746; Wed, 4 Dec 2019 05:20:31 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 04 Dec 2019 05:20:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=jbtPTD+xe61nymqN9ulWt26J6xSOwrw JypYagtIWSYw=; b=pJsbzI9ZUqDx+ee5iXYQ1k7DGnQKb93IlsZtiKnsXHyqtBU DZzD+X13VDbfgCZL62lHdUXx7T0ORcrMBizvdODSqKK4YcRWxKv+PbfzJKRTain7 PzYSvZRBy3sE69skNXIGz3X/cJwiZGwSNmyLH64HomRC90bGWE87EGI72Qs/Duiw yGN3jeJAOtsKfVB3MwbXahQw/pu87xLJCtfR00nHqO55YBnSdsf5gvf2Kk1OeZx6 JCf0iv3UFTQBgsvZhmLie/tjK+2lWd1nyGRJV8FMtcWzU+ks05W4guvC30HYEYq8 /dV8OTQWi9fBBVI/toCiTMKdFa8VU+RUJh6BHHg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=jbtPTD +xe61nymqN9ulWt26J6xSOwrwJypYagtIWSYw=; b=uNBbl54wqK+jpz6TzyR8RA OplwuF++abiwE6C4b7AqBngg5scU9NVdRmjyYyIKcQXrGfakOdXgz0rBuhauQYMc xQrfqNFMVUVKmS1T/HGDxpHefe3AYuKfH9ke+i+y1+UAYolN7npALECUHxlu+Qbn wa/a/CoweGB8yrOXyIEhptYzFPlC8k1Iwe0pxlXLgcwVjKaNOZWEwosL6Idlecpy LUPzEoEo2FUt7TzEq/hbhXBzMFRoTm8BxyoIDAYL892wnhCo+f0/63EFalriDFVV rkPGSDacU7H5pqYW/1AjFFoIKLDjibxuGZy2hV87+Z7/qMV4VyxTJmuxv6gzRJZw ==
X-ME-Sender: <xms:bojnXUxpu_8XTo_eFnpQH8xRC6Z8qwDb2z9gdmI0lKvH5k7CoY-XOg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejledgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecurf grrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:bojnXTAuopXo9uHtntT0_1ZGVhZGDy8VQY_EWh9y-Veexn8WSLmj1w> <xmx:bojnXVOab6zS5Brcak3kDLdKRNuKQzWntL_P5June84k_1ata9PvwA> <xmx:bojnXZSg94p4zGzoK5HGPB2Ul9cIDtIRi2nSL0e7km0zE3_4jEVeRA> <xmx:b4jnXf--hd5cwf1LuSYQUDZQgJPNK29VWyAptiNCBnyr_ZzM6YZJ-A>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id B40F1E00A2; Wed, 4 Dec 2019 05:20:30 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-612-g13027cc-fmstable-20191203v1
Mime-Version: 1.0
Message-Id: <82ef4920-f193-49d6-9105-cd51cd834c30@www.fastmail.com>
In-Reply-To: <8813e75d-f541-94ea-6c6a-14b624ae1850@levkowetz.com>
References: <76d730cb-9fe1-4572-acbe-8db5bc0bd598@www.fastmail.com> <8813e75d-f541-94ea-6c6a-14b624ae1850@levkowetz.com>
Date: Wed, 04 Dec 2019 21:20:10 +1100
From: Martin Thomson <mt@lowentropy.net>
To: Henrik Levkowetz <henrik@levkowetz.com>, rfc-interest@rfc-editor.org
Subject: Re: [rfc-i] Unicode names in RFCs and xml2rfc
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Wed, Dec 4, 2019, at 20:54, Henrik Levkowetz wrote:
> I'd love to make it possible to use a <contributor> element with the same
> child elements as <author> in text, to achieve rendering of contributors
> in the same format as authors, with the same provisions for both ASCII and
> non-ASCII content.  However, accomplishing any changes to the schema which
> the design team didn't envision has been hard; so hard, actually, that I've
> had to step back and mostly stop engaging on the xml2rfc-dev list.

In this case, where I'm looking for acknowledgments only, a <contributor> element wouldn't help.  I'm just looking for a name, not something equivalent to an author block.

In this case, it's the requirement to include 'num' in the format for <u> that is a little over-constraining.  A generic "this is unicode" element is fine, but coupling that to a particular output is what I'm finding problematic.
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.26.15 | Report a Bug | By Email | System Status