W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2020

Re: [Technical Errata Reported] RFC7230 (6333)

From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 13 Nov 2020 14:45:53 -0500
Message-ID: <CALaySJJHQO8AOC+fuhaYc=AuuJAPjYfN1DmogUA9XGkoraD-LQ@mail.gmail.com>
To: Julian Reschke <julian.reschke@greenbytes.de>
Cc: Jeff Brower <jeffbrower0@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, Roy Fielding <fielding@gbiv.com>, Murray Kucherawy <superuser@gmail.com>, Mark Nottingham <mnot@mnot.net>, Tommy Pauly <tpauly@apple.com>, HTTP Working Group <ietf-http-wg@w3.org>
Right: errata reports only cover the canonical published RFC, which is
the .txt file at rfc-editor.org.  So I'm going to mark this "Rejected"
for that reason.  If there's a problem in the generation of the .pdf
version, that needs to be reported to the RFC Editor separately
(they'll see this discussion, of course, so that might be sufficient).


On Fri, Nov 13, 2020 at 2:22 PM Julian Reschke
<julian.reschke@greenbytes.de> wrote:
> Am 13.11.2020 um 19:16 schrieb Jeff Brower:
> > The PDF you linked does contain the invalid characters:
> > image.png
> >
> > Notice the right and left quotes (6th and 13th items in this list)
> > rather than apostrophe and grave accent found in the text/html versions:
> > image.png
> >
> > Regards,
> > Jeff
> Funny enough, they look exactly the same in the image you attached, but
> yes, you are right, the PDF is incorrect.
> I recommend reporting this as a problem with the code that generates the
> PDFs from plain text. It definitively is not a problem in the published
> plain text RFC.
> Best regards, Julian
Received on Friday, 13 November 2020 19:46:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 13 November 2020 19:46:18 UTC