IETF Logo Mail Archive

[Tools-discuss] Re: [Ext] PDF [Re: Tools team meeting tomorrow 9 July 2024 1800 UTC]

Paul Hoffman <paul.hoffman@icann.org> Tue, 09 July 2024 15:00 UTC

Return-Path: <paul.hoffman@icann.org>
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 F10BBC16940D; Tue, 9 Jul 2024 08:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGpLL-2HgQ33; Tue, 9 Jul 2024 08:00:24 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 888D9C14F6FB; Tue, 9 Jul 2024 08:00:24 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa2.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 469F0Nd4028552 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 9 Jul 2024 15:00:24 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.34; Tue, 9 Jul 2024 08:00:22 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1258.034; Tue, 9 Jul 2024 08:00:22 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: tools-discuss <tools-discuss@ietf.org>
Thread-Topic: [Ext] [Tools-discuss] PDF [Re: Tools team meeting tomorrow 9 July 2024 1800 UTC]
Thread-Index: AQHa0hC5enVi/77MoECCExL/CWJ8fA==
Date: Tue, 09 Jul 2024 15:00:22 +0000
Message-ID: <2DDDE58D-ABB8-44B6-9674-6EE305757031@icann.org>
References: <336856cc-9986-43ba-bc26-f5c96aaa9521@nostrum.com> <A4157066-C7BA-4560-812A-21DB8A063AC4@tzi.org> <A335A99C-F06B-479B-BF33-10137A58DDFA@eggert.org> <A757BF99-2FC1-41FD-9D8E-D1388C798606@tzi.org>
In-Reply-To: <A757BF99-2FC1-41FD-9D8E-D1388C798606@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <605DC95900F12844BF83F42FBC1FB7CA@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-07-09_04,2024-07-09_01,2024-05-17_01
Message-ID-Hash: WKTZPMAC3PI7U5Z7UNTLBQTX6WWULVRU
X-Message-ID-Hash: WKTZPMAC3PI7U5Z7UNTLBQTX6WWULVRU
X-MailFrom: paul.hoffman@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Working Chairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: [Ext] PDF [Re: Tools team meeting tomorrow 9 July 2024 1800 UTC]
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/eFQS1NiPgCcoMluieSqexl-Ae3I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>


> On Jul 9, 2024, at 03:37, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On 9. Jul 2024, at 08:04, Lars Eggert <lars@eggert.org> wrote:
>> 
>> Hi,
>> 
>> On Jul 8, 2024, at 21:34, Carsten Bormann <cabo@tzi.org> wrote:
>>> Could we maybe stop pdfizing things in weird ways and simply build the correct PDF form on I-D submission?
>>> The current state is just such a waste of time.
>> 
>> I have a more radical proposal: Stop PDFing completely,
> 
> I don't think we should do that as long as PDF is one of the presentation forms we get of an RFC.

What is the logic here? Drafts are quite temporary, RFCs are forever, so the rules can be different.

> (And we shouldn’t stop that either, but that is an RSWG issue.)

I disagree with the former, but agree with the latter. After the current RSWG work settles a bit, and we have better data from the Tools Team, it might be time to revisit the idea that we publish RFCs in PDF format at all.

>> and instead make sure that browsers can print-to-PDF the HTML version correctly.
> 
> That is certainly a good thing and can be pursued independently.

+1 

> The actual requirement here is that, for I-Ds, reviewers can look at useful previews of all the presentation forms that will be in the RFC even before RPC does its magic.

"useful" carries a lot of weight here, particularly when the text will change between the last draft and the RFC itself. For the few authors that care about this, the RFC Editor can have a portal where you tell it a current draft and it does a one-time conversion to PDF using their exact PDFing tool chain.

--Paul Hoffman

v2.37.1 | Report a Bug | By Email | System Status