Re: [art] New RFCs text formatting

Brian Carpenter <brian.e.carpenter@gmail.com> Sun, 01 December 2019 21:21 UTC

Return-Path: <brian.e.carpenter@gmail.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 ADCA2120113 for <ietf@ietfa.amsl.com>; Sun, 1 Dec 2019 13:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 SCT_Xo51RvBe for <ietf@ietfa.amsl.com>; Sun, 1 Dec 2019 13:21:37 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 6CE29120110 for <ietf@ietf.org>; Sun, 1 Dec 2019 13:21:37 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id f8so15157246edv.2 for <ietf@ietf.org>; Sun, 01 Dec 2019 13:21:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6buCCIaK8IAkLvMe1W08WUCdANe10f9SN2py7zgWmG8=; b=j1LI7/s8Eg48opI9/PEUDJq1zgkhgNPorRYVLgtWTsFd7FGeyYx+1kK5+bFO8e2bNa mlw3TW9OcIsY/V4v9LNN0abDVU41mgoNxZc9l/6I1/aN55IG70qxOaSJiRVhm5Ze1Tu1 TYCMjGpiDIFLVIZ6iCtmfCStlZmzwfAOGqPc9N17MWzFXTOVWhwc3QIq9JC6LnXSjLrP 74OxDs4M2oQkm4xDgaqMhCgdju83IFdz8Q8dDn3GODAiR4MI398P6MOnIqtiN7wRI8ZE tdwQEJ4OPc90MawEsrCjLVpQJNZbHfzOv5e/sHg/GLOfHHJzlyGjmMg3ksqi4IvwrQ42 Itiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6buCCIaK8IAkLvMe1W08WUCdANe10f9SN2py7zgWmG8=; b=aG2up8hEdUB6XNCy7hyk+WxLOv3SJItdAP1atN1sU5/j339xW7uOR4HEE73mSZFBUy KnvlqtX2D/wf83anigPmV3uvTq0pwj/H5X/1skW8gTBzc9Uz1e865EE9qlu+37R23hfY P/zS0X4yq0vENTyi/x9ML2AWQnpPNj6aShAvYCnkbrNSYfJfWgtIEL/Tl0AqmZ9X/i2u cQSxTuVkj4JPdsbVyVWn6TXLMSVTCvy+XOV04LSENC/NC1dfREQkOxQP54f9xQ5QvkSF f5f2OrDUh5eC3rHI7bwoWxJHRaO+2x+ocQeHfzAjma2URaSUm3tHSM9u/Nyo+mM3fhmg MIbQ==
X-Gm-Message-State: APjAAAVR6qydv+kdRxtUex5dF3S23twGfMrAG81ilR0sav6KwxfUzBpe RE5L6kl6bbITIzbaF1Jd6OZmAonRl6hf9cj2sAuedw==
X-Google-Smtp-Source: APXvYqxDUYBTA78i8u5fwShxU1+sUbb226tJoWMyKJHdYguEGxuXcUSacFc5uY3OTanVFoYLGMnzhxl5o6H1kXybFig=
X-Received: by 2002:a50:99cc:: with SMTP id n12mr28109506edb.66.1575235295914; Sun, 01 Dec 2019 13:21:35 -0800 (PST)
MIME-Version: 1.0
References: <20191201190954.3CC38FF7AAB@ary.qy> <d136f7ad-373d-7a57-8ae1-c391a5b6f7de@gmail.com> <87B6A278-AAB7-45DA-9675-9ABCCC3FE497@sobco.com> <d4dc9942-c660-e856-d352-3e8b83e4e639@gmail.com> <869D2C59-A667-4EE6-9D5A-6B7E37C42AA2@sobco.com>
In-Reply-To: <869D2C59-A667-4EE6-9D5A-6B7E37C42AA2@sobco.com>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 02 Dec 2019 10:21:23 +1300
Message-ID: <CANMZLAbKaA3yremuQ20oMteqhS8pJk3YxD0CNhSnZpXKVfSQbw@mail.gmail.com>
Subject: Re: [art] New RFCs text formatting
To: "Scott O. Bradner" <sob@sobco.com>
Cc: IETF discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary="000000000000402ea90598ab0cad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xAACDvB6XiHf_5h4LIHeNbgyoOk>
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: Sun, 01 Dec 2019 21:21:40 -0000

Understood, but since the new canonical form is XML there is a much harder
issue.

Regards
    Brian
    (via tiny screen & keyboard)

On Mon, 2 Dec 2019, 09:48 Scott O. Bradner, <sob@sobco.com> wrote:

> the usefulness of a link depends on where the reference is used - I, for
> example, reference RFCs very
> frequently in expert reports in patent cases where everything is still
> paper-based so the references
> need to work when printed on paper
>
> Scott
>
>
> > On Dec 1, 2019, at 3:45 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> >
> > Scott,
> >
> > On 02-Dec-19 09:36, Scott O. Bradner wrote:
> >>
> >>
> >>> On Dec 1, 2019, at 3:33 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> >>>
> >>> On 02-Dec-19 08:09, John Levine wrote:
> >>>> In article <1a1726cf-70a0-019d-1138-c5e22f258d4d@network-heretics.com>
> you write:
> >>>>> I thought the format was a compromise between US Letter format, A4
> >>>>> format, and printers.
> >>>>
> >>>> I thought it was 72 characters because that's how many you got on a
> >>>> punch card, leaving 8 for the sequence number.
> >>>
> >>> Keith is right and it was one of Postel+Reynolds's wiser decisions.
> The only case where it goes wrong is with software or printers that fail to
> recognise the FF (form feed) character correctly.
> >>>
> >>> Phill is correct that it wastes some white space; that's the price of
> fitting into both paper sizes. When I print drafts, which is rarely, I do
> it "booklet" style which limits waste paper considerably.
> >>>
> >>> As we discussed 3 years ago, numbered pagination is useful in a
> printable format but irrelevant in a screen-only format.
> >>
> >> except for references - section numbers are frequently far too far
> apart when you want to point someone to a particular
> >> chunk of text
> >
> > Yes. I sometimes use page numbers for that reason, like
> https://tools.ietf.org/html/rfc3056#page-15 (random example with no
> significance). For new-format HTML, any internal <xref/> should generate a
> link.
> >
> >    Brian
> >
> >>
> >> Scott
> >>
> >>>
> >>> Can we stop now?
> >>>
> >>>    Brian
> >>>>
> >>>>> What would be parochial would be to assume that nobody in the world
> >>>>> needs to print RFCs using mechanical printers any more - that
> everyone
> >>>>> in the world should have laser printers, ample power for their
> fusers,
> >>>>> and a generous supply of suitable paper and toner -
> >>>>
> >>>> I think that if you price all the printers made in the past decade or
> >>>> two, you'll find that there are a lot of laser and inkjet printers and
> >>>> close to nothing else, certainly nothing restricted to fixed pitch
> >>>> text.  The only mechanical printers I recall seeing in recent years
> >>>> are antique Okidata dot matrix units printing whatever it is they
> >>>> print at airport gates.
> >>>>
> >>>> R's,
> >>>> John
> >>>>
> >>>>
> >>>
> >>
> >>
>
>