At 6:39 PM -0500 8/19/98, Pete Resnick wrote:
On 8/19/98 at 3:30 PM -0700, Randall Gellens wrote:
Do we need to? The draft says that SP-CRLF means "this line can be
flowed with the next". Since paragraphs are typically separated by a
blank line, a single-line paragraph will end in SP-CRLF-CRLF, that is,
a flowed line followed by an empty non-flowed line.
We could say that.
But then there'd be no way to represent what I've typed here.
I don't know, but that doesn't seem like a good thing to me.
Seriously, though, even though all we will be missing is the ability to
"type haikus", it still seems like single line paragraphs come up enough
that we should deal with them somehow.
You didn't say what you wanted flowed in your example and what you didn't.
Seems there's no problem with encoding what you wrote unless we're worried
about 17 or less column displays. The encoding would be:
We could say that.\r\n
But then there'd be no way to represent what I've typed here. \r\n
I don't know, but that doesn't seem like a good thing to me.\r\n
What I think we can't do is prevent wrapping of the following on a 16
column or less display:
Hey you. Don't
muck with my
three line table.
I not worried about this because it's no worse than we do today. If we
could express via the extra space or some other mechanism that the above
text is not to be wrapped then the possible behaviors on a 10 line display
are:
1) horizontal scrolling. This would be optimal and correct, but it'a pain
to implement.
2) truncate at 10 lines. Also correct, but no MUA author in their right
mind would do this unless they like upset users.
3) wrap. This is what we do now with text/plain and what we would get out
of format=flowed the way it's currently proposed. As far as I know most
MUAs do this now except for Netscape that does the horizontal scroll bar.
Am I missing something?
LL