- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Sat, 14 Nov 2020 16:14:10 +0900
- To: Barry Leiba <barryleiba@computer.org>, 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>
For what it's worth, the Erratum is also technically incorrect, in that
it says:
right and left quotes (U+8217 and U+8216)
The two characters are, in HTML/XML notation:
Hexadecimal: ’‘
or
Decimal: ’‘
U+-notation is hexadecimal, so this should be U+2019 and U+2018.
U+8217 and U+8216 are two Kanji, 舗 舖.
https://r12a.github.io/app-conversion/ is a very convenient tool for
such checks.
Regards, Martin.
On 14/11/2020 04:45, Barry Leiba wrote:
> 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).
>
> Barry
>
> 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 Saturday, 14 November 2020 07:14:29 UTC