Re: postscript vs PDF, Call for Community Feedback: Retiring IETF FTP Service

John C Klensin <john-ietf@jck.com> Sat, 28 November 2020 21:31 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F753A1116 for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 13:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 obNzeirLCdvD for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 13:31:10 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D17463A1115 for <ietf@ietf.org>; Sat, 28 Nov 2020 13:31:10 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kj7oD-000OMi-BM; Sat, 28 Nov 2020 16:31:09 -0500
Date: Sat, 28 Nov 2020 16:31:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>
cc: ietf@ietf.org
Subject: Re: postscript vs PDF, Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <541CBB9D85D6EEF8F3D05D51@PSB>
In-Reply-To: <20201128201704.D165728636C4@ary.qy>
References: <20201128201704.D165728636C4@ary.qy>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/flBgT-yxCQUyFiMv-8N_IojWyIQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Nov 2020 21:31:13 -0000


--On Saturday, November 28, 2020 15:17 -0500 John Levine
<johnl@taugh.com> wrote:

> In article <9E191D6ECFE4BC432E78DEE7@PSB> you write:
>> RFCs that were available in machine-readable form a few years
>> later, you would have to retrieve Postscript files and render
>> them.  I don't have any idea how stable Postscript rendering
>> mechanisms (and their supposed clones) were over time and
>> across devices or whether they were "improved" enough to make
>> assuming they represented what the author intended
>> questionable.
> 
> Postscript has always been well defined, in the original Adobe
> reference in 1985 and then the much expanded one in 1990.  Some
> of the PS RFCs may have depended on non-standard fonts but
> that all seems to be sorted out in the PDFs created from them.
> 
> I looked at a few of the first PS RFCs from 1989 in the viewer
> on my Mac and they all look fine.

Good to know and not surprising... but "looks fine" is not
necessarily sufficient to satisfy Tim's criterion of "intent of
the author".  My personal guess is that particular criterion
--at least as I, and I think Rich, interpreted it is basically
impossible.  So the key question is whether Tim intended that in
a way that is plausible and can be better defined or whether we
can (and should) just move on.

   john

> 
> R's,
> John
>