It was thus said that the Great Jason McBrayer once stated: > 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. I can live with that. Just note that lines can end in one of three possible ways: CR LF Windows LF Unix (which includes Linux and Mac OS-X) CR vanishingly small set of systems (classic Mac) I don't think I've ever come across the order LF CR. -spc
---
Previous in thread (48 of 148): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (50 of 148): 🗣️ solderpunk (solderpunk (a) SDF.ORG)