Text format proposal (was Re: Text reflow woes (or: I want bullets back!)y)

[Sean Conner]

It was thus said that the Great James Tomasino once stated:
> From: Sean Conner <sean at conman.org>
> > The two characters LF and CR MUST appear in that order in a Gemini index
> > file.  It is unspecified (at this time) what should happen if a single LF or
> > CR is encountered.  Both characters together constitute the "end of line
> > marker".
> 
> Was there an earlier discussion on this point? That looks lifted from the
> gopher RFC, but is there a reason why it's applying to Gemini? It seems
> quite specific and arbitrary to require both these days. Did someone have
> a good justification already?

  Well, the use of CRLF is mentioned several times in the Gemini spec:

=> gopher://zaibatsu.circumlunar.space/0/~solderpunk/gemini/spec-spec.txt

(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.

  I have code (used in both my gopher and gemini clients) that can deal with
either a CRLF (Internet standard; Windows text files) or LF (Linux, Mac
OS-X), but I think it might be easier on clients to just look for both (my
code will not deal with just a CR or an LFCR for instance, not that I've
ever come across any text with that format in a long time [1]).

  -spc (Didn't expect CRLF to be a point of contention ... )

[1]	I know Classic Mac (pre OS-X) and some older 8-bit computers used CR
	only.