Proposed minor spec changes, for comment.

[Martin Keegan]

On Thu, 21 May 2020, Luke Emmet wrote:

> If we force one line ending kind on authors, it will be a deterrent to them 
> forging ahead with writing user content if they have to use some tool just to 
> be able to get the content onto the server. Look at XHTML, it was a 
> resounding failure and rejected by authors even though there were some good 
> (and ill conceived) intentions of the spec writers.

I believe there's a difference between requiring servers only to use CRLF 
in the body, and content authors only to use CRLF. If it were specified 
that servers "MUST NOT" send text/gemini bodies that use line separators 
other than CRLF, then it remains up to server implementers to choose 
whether

1) to require content authors to develop or save their content with 
CRLFs, or

2) to translate the content themselves (either on the fly, or by
caching a fettled version with the right line separators).

This is why I keep banging on about having a gemini-check tool for file 
formats (though I understand someone may now have written one up in Go).

Mk

-- 
Martin Keegan, +44 7779 296469, @mk270, https://mk.ucant.org/