- From: Willy Tarreau <w@1wt.eu>
- Date: Sat, 14 Nov 2020 20:02:33 +0100
- To: "John R. Levine" <johnl@iecc.com>
- Cc: Julian Reschke <julian.reschke@greenbytes.de>, jeffbrower0@gmail.com, fielding@gbiv.com, Mark Nottingham <mnot@mnot.net>, Murray Kucherawy <superuser@gmail.com>, ietf-http-wg@w3.org, Barry Leiba <barryleiba@computer.org>, tpauly@apple.com, RFC Errata System <rfc-editor@rfc-editor.org>
On Sat, Nov 14, 2020 at 01:52:57PM -0500, John R. Levine wrote:
> On Sat, 14 Nov 2020, Willy Tarreau wrote:
> > On Fri, Nov 13, 2020 at 06:27:58PM +0100, Julian Reschke wrote:
> > > > Notes
> > > > -----
> > > > The generated PDF contains misleading right and left quotes (U+8217 and
> > > > U+8216), which are not ASCII characters. The text and html versions of the
> > > > RFC have the correct apostrophe and grave accent characters (' and `).
>
> That PDF was generated mechanically from the definitive text RFC. We use a
> generic text to PDF converter (I can check which one) and it's not
> surprising that it uses heuristics to guess which kind of quote to use, nor
> is it surprising that it sometimes guesses wrong in technical text.
But here there are clearly two distinct characters, one is 0x27 and the
other one is 0x60. Both are perfectly printable ASCII characters, which
is why this is particularly surprising.
> If you want to copy and paste ABNF, for heaven's sake copy it from the
> definitive text version, not the PDF.
Sure but when just checking for a message validity, the PDF or even a
printed copy are commonly used as well.
Best regards,
Willy
Received on Saturday, 14 November 2020 19:03:19 UTC