Re: [Tools-discuss] Unicode decode error for RFCs
Nico Williams <nico@cryptonector.com> Mon, 05 April 2021 19:24 UTC
Return-Path: <nico@cryptonector.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A41C3A247B for <tools-discuss@ietfa.amsl.com>; Mon, 5 Apr 2021 12:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 QZQYNwqtN1KR for <tools-discuss@ietfa.amsl.com>; Mon, 5 Apr 2021 12:24:23 -0700 (PDT)
Received: from antelope.elm.relay.mailchannels.net (antelope.elm.relay.mailchannels.net [23.83.212.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C2453A2478 for <tools-discuss@ietf.org>; Mon, 5 Apr 2021 12:24:22 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id AA899542047; Mon, 5 Apr 2021 19:24:21 +0000 (UTC)
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (100-96-18-61.trex.outbound.svc.cluster.local [100.96.18.61]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 300FE541FD2; Mon, 5 Apr 2021 19:24:21 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.18.61 (trex/6.1.1); Mon, 05 Apr 2021 19:24:21 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Broad-Reign: 46d2d74e04cc9b03_1617650661477_196754937
X-MC-Loop-Signature: 1617650661476:3079080386
X-MC-Ingress-Time: 1617650661476
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTP id B2AA285DB2; Mon, 5 Apr 2021 19:24:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=kmcir/+qTXKC6+ PFiHhCOEs33yw=; b=QQnH0Wcq+SzfZ16hly0MulQC3/2qPDxKwxglH0VCIv5wId xj/Qk29Xc4YBXSlbP5Q4x9McxJxQdCvNi9GP2QKuaDi0rVgn3iQhGwZ5yUOxKdvk YqVhWlv6/VpbBFXO8tC2W75OvpoPoS80zAbt91YO5N93ZB2fcb4baLfiJsxis=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTPSA id 6589385DB1; Mon, 5 Apr 2021 19:24:18 +0000 (UTC)
Date: Mon, 05 Apr 2021 14:24:16 -0500
X-DH-BACKEND: pdx1-sub0-mail-a70
From: Nico Williams <nico@cryptonector.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>, tools-discuss <tools-discuss@ietf.org>
Message-ID: <20210405192415.GI3828@localhost>
References: <3C729A10-5F70-465F-AD97-0A1338836C82@vpnc.org> <4790f6a6-5893-e8e6-7361-74657a6735d7@gmail.com> <20210404210629.GE3828@localhost> <AB577D47-8ED4-4229-AF06-7873DCD7BBFC@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AB577D47-8ED4-4229-AF06-7873DCD7BBFC@akamai.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/0efeFlUQxnt3QeJilKNXpY0wHlw>
Subject: Re: [Tools-discuss] Unicode decode error for RFCs
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 19:24:27 -0000
On Mon, Apr 05, 2021 at 03:53:08PM +0000, Salz, Rich wrote: > On Sun, Apr 04, 2021 at 03:41:21PM +1200, Brian E Carpenter wrote: > > I mean, who cares about the htmlized versions of HTML RFCs? > > I also like them better. I can also read them on any device (yeah, > responsive design). But I mean specifically the htmlized versions versus HTML produced by xml2rfc or any XSLT conversion. I like the pagination (yes, yes, I know, we as a community want to stop paginating). I like the way footers and headers are rendered. I like the metadata header at the top with the version history, alternative formats links, and datatracker/nits/IPR/diffs links. I accept that we'll eventually lose the pagination, but a) the tools.ietf.org URIs are kinda useful now just because they are so recognized, b) we should really not lose the metadata header. > If we're writing for the Internet, text/html is way more important and > useful than text/plain. I read these things in $PAGER as much as in $BROWSER. I don't mind the text. I just don't want to lose all the value provided by the htmlize tool right now.
- [Tools-discuss] Unicode decode error for RFCs Paul Hoffman
- Re: [Tools-discuss] Unicode decode error for RFCs Brian E Carpenter
- Re: [Tools-discuss] Unicode decode error for RFCs Carsten Bormann
- Re: [Tools-discuss] Unicode decode error for RFCs Paul Hoffman
- Re: [Tools-discuss] Unicode decode error for RFCs Carsten Bormann
- Re: [Tools-discuss] Unicode decode error for RFCs Julian Reschke
- Re: [Tools-discuss] Unicode decode error for RFCs Hoi lam Poon
- Re: [Tools-discuss] Unicode decode error for RFCs Paul Hoffman
- Re: [Tools-discuss] Unicode decode error for RFCs Brian E Carpenter
- Re: [Tools-discuss] Unicode decode error for RFCs Nico Williams
- Re: [Tools-discuss] Unicode decode error for RFCs Michael Richardson
- Re: [Tools-discuss] Unicode decode error for RFCs Nico Williams
- Re: [Tools-discuss] Unicode decode error for RFCs Salz, Rich
- Re: [Tools-discuss] Unicode decode error for RFCs Nico Williams
- Re: [Tools-discuss] Unicode decode error for RFCs Paul Hoffman
- Re: [Tools-discuss] Unicode decode error for RFCs Nico Williams
- Re: [Tools-discuss] Unicode decode error for RFCs Brian E Carpenter
- Re: [Tools-discuss] Unicode decode error for RFCs Andrew G. Malis
- Re: [Tools-discuss] Unicode decode error for RFCs Robert Sparks
- Re: [Tools-discuss] Unicode decode error for RFCs Jay Daley
- Re: [Tools-discuss] Unicode decode error for RFCs Brian E Carpenter
- Re: [Tools-discuss] Unicode decode error for RFCs Nico Williams
- Re: [Tools-discuss] Unicode decode error for RFCs STARK, BARBARA H