Re: [Tools-discuss] Unicode decode error for RFCs
Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 05 April 2021 22:05 UTC
Return-Path: <brian.e.carpenter@gmail.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 D6D783A29DB for <tools-discuss@ietfa.amsl.com>; Mon, 5 Apr 2021 15:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.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 gfMZkZQ6TACT for <tools-discuss@ietfa.amsl.com>; Mon, 5 Apr 2021 15:05:11 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB763A29D1 for <tools-discuss@ietf.org>; Mon, 5 Apr 2021 15:05:11 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id x26so2289414pfn.0 for <tools-discuss@ietf.org>; Mon, 05 Apr 2021 15:05:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=TYyaMm2EJN/MY12anE4rro0PiUI/hfhzM2LVJKiSBX0=; b=miuS/jr7jWZb4Fmnm30Y/IhHW5uWa3xkgJrv0qA1L7g07b7Sn5Q4WmPk+zbxVyBszA UtqNmXerNymjjgQ4VtCmuihHkwbYy8KUtZchE+Jw0f3G6PZvsJhhqwNCqDFDSmXVnjiW EY1f4zQhRxSLtaPqPlGDwd9+GiSg0EiDWvNjBYB1ztI9rmnwFUDQAORtnS3QVP2eoE3U 25vMb6FBSc6f3LiffGheHRMrKnpIig3LMEctfzHxGd0Nt1/8uSSMIJz916nzER812ART 85Fkk/CQA0+99Wko7udbEqnoTR/GuqX+0j2f/vTXqcpBMZ5PnHwHsllbwNqQxMAq5Exp OyVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TYyaMm2EJN/MY12anE4rro0PiUI/hfhzM2LVJKiSBX0=; b=XKNcpPojuWXIxCHgPg0qCZa/lHRdGOFo1w+f4Ac5EMdgxHBHyYoQHJb0anjgpAHFiW qIm+EdlM/r+oYTtF3MvM/vizZR7Bi6Hsqbcw1uHqST8vBl2QqsqUutFFCvsWeO0heOTf 6OAs9xg5Y7rNUh2JOkF+v4y4wHkU/hkY0wihd+nyXr04OpRQiL4RX+jaHPsfQ0AtuNUp 5sc95Zh/Esf4Wv2s5AmZ/EMlurg8donwMEzzNtU5NBB8n74JerxNM2VUSnnWBlHbvSXC cCAg2FZ5QM0siEpSHEctUfRw2RnpOxKCBvF8ZivrGnLi9Mb2v//l/2vsOHY7X1kcFYb6 ZRvA==
X-Gm-Message-State: AOAM533ahFtlz9Mmtbj6vr5ooq0RbPAgN/JhX/wcJm2EtmbUuSvce9yN Ro77A8oML3nCd+IDi7/hSmG6uQfSNsxFkA==
X-Google-Smtp-Source: ABdhPJwwraMkL7AC8iARRmH1Ih0+dntzi3JFas3bMNOQb4B+UcJ5fHTv3Op5fyfHuQLDFqp9W5FLEg==
X-Received: by 2002:a63:1352:: with SMTP id 18mr23940737pgt.11.1617660308874; Mon, 05 Apr 2021 15:05:08 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.131.14]) by smtp.gmail.com with ESMTPSA id mr5sm359581pjb.53.2021.04.05.15.05.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Apr 2021 15:05:08 -0700 (PDT)
To: Robert Sparks <rjsparks@nostrum.com>, Paul Hoffman <paul.hoffman@vpnc.org>, tools-discuss <tools-discuss@ietf.org>
References: <3C729A10-5F70-465F-AD97-0A1338836C82@vpnc.org> <4790f6a6-5893-e8e6-7361-74657a6735d7@gmail.com> <9e9c8c7e-c6f2-bd59-4f8b-2e009b50447b@nostrum.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d35e36c1-ffaa-5859-9e5b-53b6bc6e7584@gmail.com>
Date: Tue, 06 Apr 2021 10:05:04 +1200
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: <9e9c8c7e-c6f2-bd59-4f8b-2e009b50447b@nostrum.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/S0FviqiT8f8CUXJbkymJMsB1kns>
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 22:05:16 -0000
On 06-Apr-21 09:57, Robert Sparks wrote: > Replying to this, even though the thread has mostly moved on, to point > at a detail that we need to remember. > > On 4/3/21 10:41 PM, Brian E Carpenter wrote: >> Paul, >> >> https://datatracker.ietf.org/doc/html/rfc9007 is OK. And the tools repository is going away anyway. Maybe the Twitterland needs to be told. >> >> https://www.rfc-editor.org/rfc/rfc9007.html is even more OK. I mean, who cares about the htmlized versions of HTML RFCs? > > Other systems (software, SDOs) need to be able to point at the > appropriate thing for both old and new RFCs. There's been a strong > preference in the past to point to the HTMLized versions for many reasons. > > For pre-v3 era RFCs, the htmlized versions is what we have - we do not > have the xml2rfc v3 html output, and it is not currently on any plan to > try to retroactively create any such thing. > > Asking software and other SDOs to learn to use two different URL > patterns (one before and one after the v3 switch) is not likely to be heard. Indeed. I believe the RFC Editor would prefer us to use their landing pages like https://www.rfc-editor.org/info/rfc9007 or https://www.rfc-editor.org/info/rfc1, but I'm not sure that will catch on. Brian > RjS > > >> Regards >> Brian Carpenter >> >> On 04-Apr-21 14:23, Paul Hoffman wrote: >>> See https://tools.ietf.org/html/rfc9007 >>> >>> (Hat tip to https://twitter.com/elithebearded/status/1378520379229044736 >>> for pointing it out, and the @FakeUnicode Twitter user for reposting.) >>> >>> ___________________________________________________________ >>> Tools-discuss mailing list - Tools-discuss@ietf.org >>> This list is for discussion, not for action requests or bug reports. >>> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org >>> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org >>> * Report all other bugs or issues to: ietf-action@ietf.org >>> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss >>> >> ___________________________________________________________ >> Tools-discuss mailing list - Tools-discuss@ietf.org >> This list is for discussion, not for action requests or bug reports. >> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org >> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org >> * Report all other bugs or issues to: ietf-action@ietf.org >> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss > >
- [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