IETF Logo Mail Archive

Re: [rfc-i] Unicode in xml2rfc v3

Lars Eggert <lars@eggert.org> Mon, 11 January 2021 09:23 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 D76C43A1738; Mon, 11 Jan 2021 01:23:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level:
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, 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 DZ_o484TpxaC; Mon, 11 Jan 2021 01:23:13 -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 5C5003A1736; Mon, 11 Jan 2021 01:23:13 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 255D1F40753; Mon, 11 Jan 2021 01:23:05 -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 D4C69F40753 for <rfc-interest@rfc-editor.org>; Mon, 11 Jan 2021 01:23:03 -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 lSuLskPFM0PL for <rfc-interest@rfc-editor.org>; Mon, 11 Jan 2021 01:23:00 -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 C58E4F40752 for <rfc-interest@rfc-editor.org>; Mon, 11 Jan 2021 01:22:59 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:6dd9:b2bf:beaa:fad8] (unknown [IPv6:2a00:ac00:4000:400:6dd9:b2bf:beaa:fad8]) (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 CE1EC600079; Mon, 11 Jan 2021 11:22:59 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1610356979; bh=3PGp2mVDSVWMdfBmhWO2+U9SNLP6nBCrxjdj8s1glA0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=yeiXqpLVSAAU494V85aMsWCzxbbn4Q0+edUjNYT9CkVOZ+PgQG0XB1B3CJe022E7P pJwG3SFfiCTkORTae1F0E/6izqtZ2zpp4iApCAP2miG3EB1LTJDSOSq5je+P9cWz5N z9oCJHo2Lq1Z+7SIQFdKKqeagkuUCGu/xW3P517o=
From: Lars Eggert <lars@eggert.org>
Message-Id: <F4B91C67-7E4A-407D-A09A-EFC11D2F6678@eggert.org>
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Mon, 11 Jan 2021 11:22:59 +0200
In-Reply-To: <bc4cb5b1-ac77-9d84-b0a3-38fc2dcb512b@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
References: <20201216184835.CE1CA2ABC7A1@ary.qy> <AF7F0885-2D39-4F8D-A43B-E1D015146EAE@eggert.org> <2fb0b749-8d33-c5b2-39dd-8f351cdfac0@taugh.com> <CEF858E8-023A-4AEA-AAC6-1EC1246D147E@eggert.org> <eb70885d-dda-bd2-5c9-cb6143192e98@taugh.com> <bc4cb5b1-ac77-9d84-b0a3-38fc2dcb512b@it.aoyama.ac.jp>
X-MailScanner-ID: CE1EC600079.A4583
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: rfc-interest@rfc-editor.org
Content-Type: multipart/mixed; boundary="===============9043167508549342838=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 2021-1-11, at 11:13, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> What I'd recommend to do is to give the RPC a little tool that shows all the non-ASCII characters with a special background color so that they can very quickly check what's in there (because it usually shouldn't be much). Having tooltips giving more character information, and with time building up a list of dos and donts would be the next step.

Like it!

Could even be an option to xml2rfc, to allow authors to verify whether any of the tools they used did weird things.

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