I will reverse the changes and document line breaks exceptions
in the message rendering section.
Thank you.
I am not sure whether it is a good idea to add a special "soft
break" character (e.g., '\' to follow C and Unix shell convention).
Using your own arguments, people may try to use those "soft break"
characters in real world and complain that they do not work.
Anybody thinks it is a good idea to add '\' for rendering
purposes only?
I am also not 100% sure.
But such a character could then easily be used to do a "Replace All".
I hope that soft breaks in text will not be needed often.
But if we need to add, the example will not work directly neither with
CRLF nor with \CRLF. Easy transformation to working code is a plus I think.
One solution would be to make SP and CRLF interchangeable, but
that complicates parsing. MIME has something like that (implied LWS
rule), but virtually no HTTP agent we tested supported it correctly!
Finally, what do you think about indentation? Can we still
use it for rendering purposes? Please? :-)
...
Comments/opinions?
I agree, that this is much nicer.
But it will break many more examples than soft line breaks.
I think we either need to define in OCP that any number of TAB characters
are allowed after CRLF or forget about the indentation in the text.
We could replace all existing CRLF in the BNF with NewLine and define
NewLine = CRLF *(TAB) ; if TAB is the correct name for that char
Regards
Martin