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

Julian Reschke <julian.reschke@gmx.de> Wed, 04 December 2019 11:00 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 DD5FF12080C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Dec 2019 03:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.499
X-Spam-Level:
X-Spam-Status: No, score=-4.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, 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 (1024-bit key) reason="fail (body has been altered)" header.d=gmx.net
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 STK2o0-mC6PW for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 4 Dec 2019 03:00:54 -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 43CB9120806 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 4 Dec 2019 03:00:54 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F2ABAF40712; Wed, 4 Dec 2019 03:00:51 -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 CB3AAF40712 for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 03:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 LfQSHalaMRnN for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 03:00:50 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by rfc-editor.org (Postfix) with ESMTPS id 9C703F40711 for <rfc-interest@rfc-editor.org>; Wed, 4 Dec 2019 03:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1575457235; bh=RI0frhGA1Cves7MydtJSzeU6/0nOh+4Jtml8RUvfMbc=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=V9fwIkhrFLqGdr7gUgA/vjHLpnFlIlNR6DJNpopG9D60vPCoewdxNrIpvS2ZxqQB2 bUsADmYEo0yFmxfKH3P0PKvPRyvtxDbm749QjwWDG/l3BG3K3PhYtiummkMTiF3iVs ThkU4W/J1oLMY8lMSDYdpvSoDCG17SlKnLVOfo8w=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MFsUv-1iYMbE2xUV-00HRPk; Wed, 04 Dec 2019 12:00:35 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, Martin Thomson <mt@lowentropy.net>, rfc-interest@rfc-editor.org
References: <76d730cb-9fe1-4572-acbe-8db5bc0bd598@www.fastmail.com> <8813e75d-f541-94ea-6c6a-14b624ae1850@levkowetz.com> <82ef4920-f193-49d6-9105-cd51cd834c30@www.fastmail.com> <6718ee2f-d081-156e-224e-da4a1ceb5300@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <f2bdb493-6e0c-452b-0e2c-f89b25e7b6a0@gmx.de>
Date: Wed, 04 Dec 2019 12:00:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <6718ee2f-d081-156e-224e-da4a1ceb5300@levkowetz.com>
Content-Language: en-US
X-Provags-ID: V03:K1:oTFrkFyyZzdXW5AEV0QVJe2fpK0ZA3FD7aGpH/x7BZGD+7IilUF M0zC1FAQCwldSAX0rZYP3olKvhRZf8FfDYgEVDkvQ85LCQPaqUh4XCBDwsBDQobnA+inVp0 ejX8WG8zd+2L14BFSJlHE9H6cKg6nWYWkQ9dK8Vbhbc8RiGvxSu9doOGvy1XoGytWigH8b8 72XTrkD0yr911bM3RbhKQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:P6j19jttSXw=:VAfNPJhCwCJf8TpgeFAzy6 NgE2qWAxgQAa8VzIuFYPzgEyzl8r3KnkwxZQkNVJL7z1f+kxIHpZSfwL0LqQbLiqiGIyoUhAo 3vGKnvpWOPZ+WqVMn6pHP68a80HYIBe8wQCdxy5CdGOgKIAj76hP/IKc8i/HcdpkA4HhT49TU o/+iz7LIE4PZLyQvVym2/BXE6yNqGzK5AYC6guZujMk0SM/cZJQN+0rG+U9cjMlQ+Z6tagDem xL5/UVNnZWbs+4GBWM598/7fPiuatyl6QiLQQK179VHMoFDCoijpJuCo/a9qp5ksumdBwnmAZ EPuF4jh01UgRB04H3sn/pD1a0fyHGLkF+EHZ15OScYgL2OoBDlm5yKnwwKjvYQEAGO/aizlTb 7LGhnX2eGvg2eFvBSknhWI3HSVLbDf/eekLEZCO075ITL9tSJjHRrq9zvaNGSVQCA+hAgsqHX C4lPYDG2O5K7cf28Yq4U0LW9ifKyj2CO7OfhvvDgpZmGZiNLE0I2Y0LWjgCS6p81Q8EEDy0Gb nJ8cbqhJ6QZ+1icH48njteR4C2ynrXdgSB8ysuPRUvC6XkCKdeTl2s0M9Kpar8XlW4gBUj4q+ LGr4G8gzPcOaUKWPwu92uAjsLgB3RdUCYspI2jEM2aq/7ru3zCd/n2HjMwMpXzNC/KCQMBVsN JzverSGfMCv2kEfQ9LnOtR4fCplVgIUFimY3cJyRomSQg1ALxfIvVmoE5QIGe60E60F9JHKEK +I7et1iq9UfXB8lfCanf9tvf8zvZggZyjw/1rLAt8v25jrNbecSL3rjCS8LQalKLu575wBSfg jLZXLTWGo8QgAyvDi60PfXVPawgYp3HelMGjUbKoj4s2oXHuZOew8qeZ2O69LXEOvbyP3STe9 lNUBKhyO9IPws6rpPCUCxlKDdcJHvfRRXM70ZDrpPOlZgTEOLY09DDUGP7vioRYAQEv5VK1rd NGVhRwhxxXYn1N6NTdIytb/GXgmi3T9E3/m6nvND6JPYDhYHw/V2e5SB2ZUQnkc6yzv29MjtB gp1depZZj2nL+TSK7r0ardW6iSwOfFeKe7jVjjfiKaq1V65vEuwMMwY7vYZuh2K8hRvd9DXis dS9zwgHqIU31qNU5/80irPWSj90SfoKia+Nv19KYc4cRUtqC6r6nGPQWH0gJ+pX+OqrHKEfGb 76Xsu7SrHBbspr2Clilis1ukX9JOlYfyyODFv7t6h3VlPUDmkqEj/Ndi9pRufrp2K475tUsPo qRDNPa/M1bqRubl9Q8xIxfjiiI1mB6F8VHlvQSR8Uq+QUPUMOPbrJS79/sVA=
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 04.12.2019 11:34, Henrik Levkowetz wrote:
> Hi Martin,
>
> On 2019-12-04 11:20, Martin Thomson wrote:
>> 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.
>
> There are several possible renderings for an author block, depending on
> context.  Making it possible to control this for a contributor entry would
> make sense.

That's a possibility, but IMHO that just makes things more complicated
than needed. Sometimes a string is just a string.

> ... > You're trying to use the <u> entry for something it very explicitly
wasn't
> designed for.  A <contributor> entry would not only be able to give you the
> output you want, it would also provide the correct semantic labelling in the
> XML file.
> ...

What would that labelling be used for? Not every name mentioned in an
RFC necessarily refers to a contributor, after all.

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest