Re: [rfc-i] Unicode in xml2rfc v3
"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 18 December 2020 20:27 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 8F67C3A0163; Fri, 18 Dec 2020 12:27:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level:
X-Spam-Status: No, score=-2.451 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, NICE_REPLY_A=-0.001, 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=joelhalpern.com
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 NgUd5Ndxkmrm; Fri, 18 Dec 2020 12:27:33 -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 0DA273A0140; Fri, 18 Dec 2020 12:27:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1D488F406DB; Fri, 18 Dec 2020 12:27:22 -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 3BF0FF406DB for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 12:27:21 -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=joelhalpern.com
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 gyc6Nt56uYec for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 12:27:17 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) by rfc-editor.org (Postfix) with ESMTPS id 716BCF406D6 for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 12:27:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4CyL5C1nRKz6GKMD; Fri, 18 Dec 2020 12:27:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1608323247; bh=C7DeRKvFTkoY0qcyX5nmN1IUSlN2EjrrxU9g474PMxI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=eTkWQmS+Jd2Os/9f772RGG2InncTjrDQH0Lw8pgRDaWiP9D6sUlXGzbN7MT+w7rxB cZHSMuhPGiOdC63nh0nS8YUDC0qvFp3zFNKwLAfKuQY4+danlpZLnogl9khViHB8Lg 2do8fIca648hTg0BwBcFeBEhpT1oAn5G3SN5Eluw=
X-Quarantine-ID: <FJUhFwXV_lXp>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4CyL5B4lhcz6G9Vy; Fri, 18 Dec 2020 12:27:25 -0800 (PST)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
References: <20201216184835.CE1CA2ABC7A1@ary.qy> <AF7F0885-2D39-4F8D-A43B-E1D015146EAE@eggert.org> <72467617-6ca7-b2af-b826-d264c6b6380e@gmail.com> <D8AC8FA8-74DC-4B93-AB5B-73FBE1880F26@ietf.org> <4ef03ad3-1072-20e9-9676-2822a743a614@gmx.de> <afc0024a-e68b-0db8-90ef-1632875d2245@gmail.com> <10411562-B919-46E2-8BB2-A3D8AAD37FCC@tzi.org> <CABcZeBMeqa7R2Yd+sNHkTe1TUTBuxjXeWQ05vhEUEML_vUkwug@mail.gmail.com> <aa501ccc-b84e-c149-4610-ec2e4d34cd01@alum.mit.edu>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <3e6f31f5-4e85-35f5-d701-d15944577f2c@joelhalpern.com>
Date: Fri, 18 Dec 2020 15:27:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <aa501ccc-b84e-c149-4610-ec2e4d34cd01@alum.mit.edu>
Content-Language: en-US
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>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Actually, gien the differences in rendition, documents (if we ever have such) about color or gray scale may be exactly when you do NOT want to use color and grayscale. Slight mis-rendition could easily result in quite confusing documents. Our initial agreement did include that we would revisit this. And get publication expertise on the known problems in this space would be very helpful. (We are not the first folks to wrestle with these issues.) Yours, Joel On 12/18/2020 12:13 PM, Paul Kyzivat wrote: > On 12/17/20 7:29 PM, Eric Rescorla wrote: > >> FWIW, while I don't generally think we ought to have our documents >> written in emojis, I do see some potentially valid reasons for them to >> appear, for instance if one was writing a document about the use of >> emojis. > > Agree. > > Similarly, I don't think we should totally ban graphics that contain > color or greyscale. There are good reasons to restrict that sort of > usage to make documents accessible to more people. But surely there are > exceptions. For instance a document that is explicitly concerned with > color and greyscale. > > Thanks, > Paul > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://www.rfc-editor.org/mailman/listinfo/rfc-interest _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Henrik Levkowetz
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Michael Richardson
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Martin Thomson
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 tom petch
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Jay Daley
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Eric Rescorla
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Martin Thomson
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 tom petch
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Paul Kyzivat
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Joel M. Halpern
- Re: [rfc-i] Unicode in xml2rfc v3 Eric Rescorla
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Salz, Rich
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Martin J. Dürst
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Paul Kyzivat
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann