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

Re: [Technical Errata Reported] RFC7230 (6333)

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 19 Nov 2020 11:09:25 +0100
To: "John R. Levine" <johnl@iecc.com>, Willy Tarreau <w@1wt.eu>
Cc: 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>
Message-ID: <ac40df19-da20-bc26-fde4-f9131741b5d6@greenbytes.de>
Am 14.11.2020 um 19:52 schrieb John R. Levine:
> 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.
 > ...

FWIW: we should check what tool is doing that, and whether we can stop 
it from trying to be "smart".

 > ...

Best regards, Julian
Received on Thursday, 19 November 2020 10:09:43 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 19 November 2020 10:09:43 UTC