Sean Conner <sean at conman.org> writes:
> (specifically sections 1.2, 1.3.1 and 1.3.5.2). It doesn't have the
> language MUST, SHOULD, etc, though. Also, CRLF is an Internet standard for
> transfering text (you'll see it in many other specifications, like SMTP and
> HTTP), so that's why I added that language.
IMO, it makes sense to require CRLF in the plain text parts of the
protocol (after requests, after the status line of a response), but I
don't think that the text/gemini file format needs to have CR/LF; IMO
clients should be prepared to accept either LF or CR/LF just as they
would with text/plain. And maybe if we're serious about supporting old
devices, clients should be prepared for bare CR, too (Classic MacOS).
But it's a pain in the arse to authors to have to save text documents
with non-native line endings, and I don't feel like servers need to be
in the business of reformatting the content they serve.
--
Jason McBrayer | ?Strange is the night where black stars rise,
jmcbray at carcosa.net | and strange moons circle through the skies,
| but stranger still is lost Carcosa.?
| ? Robert W. Chambers,The King in Yellow
---
Previous in thread (45 of 148): 🗣️ solderpunk <solderpunk (a) SDF.ORG>
Next in thread (47 of 148): 🗣️ Jason McBrayer <jmcbray (a) carcosa.net>