Spec shouldn't rely on trailing whitespace about fountain

[stuartpb]

Okay, I jumped to write this before I got to the section for Boneyard. I suppose this could also work as a (moderately ugly) workaround without having to mess with the spec:

DEALER
Ten.
Four.
Dealer gets a seven.
  /**/
Hit or stand sir?

Still curious about the backslash-escaping angle brackets, though.

[nyousefi]

I completely agree with you, and you articulated this issue wonderfully. I'll push this up the food chain and try and get a change here. Thanks!

[tinlash]

I have an idea for solving this issue, but want to be sure I understand the problem.

Using two spaces at the end of a line is a workaround. The problem is recognizing action lines as action when the text is preceded by a single newline, or even \n\s*\n, i.e., a problem that only occurs with single vertically spaced action lines. Is this correct?

[strokirk]

I'd like to revive this. Having some way of explicitly marking dialogue would be really useful. Trailing space is a little tricky to enforce.

[stuartpb]

For what it's worth, in Markdown, the alternative to the thing whitespace offers is to explicitly write <br> (as the canonical Markdown implementation is designed to intermingle with HTML); perhaps <br> could be explicitly recognized as a token in Fountain?