[chrismorgan]

You cite RFC 8478 as though it being an RFC gives it weight, but always remember when looking at IETF RFCs to check the Category, which is Informational in this case, not Standards Track.

> Despite use of the word "standard" as part of its name, readers are advised that this document is not an Internet Standards Track specification; it is being published for informational purposes only.

This is an IETF-stream document, which I believe (though I’m not certain) implies that it’s at least a little more than just Facebook saying “here, can we publish this?”, but it hasn’t come through any working group, so it hasn’t been subject to the full IETF experience which is so helpful at improving things by collaboration.

(It’s also obsoleted by RFC 8878, to which the same caveats apply.)

[vanderZwan]

> It’s also obsoleted by RFC 8878, to which the same caveats apply.

Tangent: I decided to sit down and read that RFC yesterday. So I downloaded the PDF to my e-reader (because it doesn't support mono fonts for the plain text option). Turns out my Kobo H20 for some reason can't render the "fi" and "ff" ligatures, which made it a real struggle to read at times ("compressed les", "Human Encoding Trees").

Does anyone have any advice for how to turn plaintext RFCs into minimal PDFs with an embedded mono font?

https://www.rfc-editor.org/info/rfc8878

[rini17]

Print as PDF from a browser or wordprocessor? In LibreOffice Writer you have the option to embed the font.

[vanderZwan]

... sometimes the simplest solutions are the best. I feel so dumb, thanks!

I could probably even set the page size to the right dimensions in LibreOffice Writer