IETF Logo Mail Archive

Re: [rfc-i] Unicode in xml2rfc v3

Lars Eggert <lars@eggert.org> Wed, 16 December 2020 15:29 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 549B03A0F39; Wed, 16 Dec 2020 07:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 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, 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=eggert.org
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 CSEAETZoT4kD; Wed, 16 Dec 2020 07:29:28 -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 350143A0F01; Wed, 16 Dec 2020 07:29:28 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0F8EEF40754; Wed, 16 Dec 2020 07:29:21 -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 746C3F40754 for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 07:29:20 -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=eggert.org
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 kxhELZxqqsNy for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 07:29:16 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) by rfc-editor.org (Postfix) with ESMTPS id 6A03EF40752 for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 07:29:16 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:ecaa:61ef:480d:9247] (unknown [IPv6:2a00:ac00:4000:400:ecaa:61ef:480d:9247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 39CFD60C26A; Wed, 16 Dec 2020 17:29:14 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1608132554; bh=xQiQVf8FiRapmC4E5obTpkEu8DmtbgD3pQ3a2e7bTb0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=fKb5FrQAD9pYNpxAjiMJhhvFldGVPUU+1HqJliIuUjmYJ0ySWBDG+PZ8pwM2plaov blC9dFyUQWCa0kzQnY0FsEgAamQflgb3YzO1eCRa9EM+eBVCFmlEdyhpGSzatJ6h24 dHlQ8ejnupPYm4hWNhRX9Is3idGImuiu0ZfBYrIw=
From: Lars Eggert <lars@eggert.org>
Message-Id: <BB864858-1E71-45CF-9411-2ECB003B5EC0@eggert.org>
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Wed, 16 Dec 2020 17:29:13 +0200
In-Reply-To: <2CB2234E-0F90-4C2A-8084-7E89656AA9C9@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
References: <F2E370D6-BCA9-4902-836E-8C5BADFE5209@eggert.org> <4cff4b9c-6464-659d-8b27-32396b59182c@levkowetz.com> <EC333D0C-D024-416B-9CAA-880D3E90368F@eggert.org> <115988ED-68A9-4E99-BB2E-55E0B5B0E96A@tzi.org> <44D623BB-9F0C-41F9-92E3-A39B0FAB8164@eggert.org> <C1E69941-33B2-41D4-84A1-3B621F67E292@tzi.org> <5129aae3-d14b-23ee-43b0-ad7a0cf44bee@gmx.de> <F6BBDA54-9906-45BB-83B1-B8866B94F109@tzi.org> <3199a9ee-e568-fa59-e8cd-4bb861a57daf@gmx.de> <2CB2234E-0F90-4C2A-8084-7E89656AA9C9@tzi.org>
X-MailScanner-ID: 39CFD60C26A.A4EA8
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Subject: Re: [rfc-i] Unicode in xml2rfc v3
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>
Cc: Julian Reschke <julian.reschke@gmx.de>, RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: multipart/mixed; boundary="===============5394714145541481301=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 2020-12-2, at 14:55, Carsten Bormann <cabo@tzi.org> wrote:
> 
>> I will stick with my opinion that <contact> should be reverted to its
>> original definition (block content, for formatting similar as authors),
>> and that we should just allow non-ASCII in prose (with the production
>> center having an eye an abuse).
> 
> Completely agree.

Agree as well.

> Until that change happens, we have the workaround, which is marred by the incomplete integration of <contact/> into the grammar.

And other places, as we just discussed on GitHub today.

It's ridiculous that I can't just write α when I mean α.

(Sorry, I'm grumpy.)

Lars

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

v2.23.0 | Report a Bug | By Email