I think it's simpler to focus on "phrases" instead of line breaks. A phrase is easier to talk about in the context of Fountain rules. The reason is that a line of a fountain file isn't actually a line of a script, for any of the alternate meanings of "line".
My question then, is what are you trying to achieve with the line breaks in your phrases?
It seems like if you're writing one phrase that's all lyrics, you shouldn't be also burdened with deciding where the line breaks go. That's the formatter's job. That's what the host application is supposed to be doing *for* you.
Perhaps you're trying to manually indicate meter or cadence? It seems consistent that if you're manually overriding the formatter, then you should also manually indicate phrase types. If you're unlucky or digging deep enough, you can see this philosophical approach in other places in fountain, where manual overrides generally require extra work and attention.
None of this is to say that we shouldn't be handling this the same way across our applications. Compliance however, is rather tricky for fountain, because a benchmark between applications is only possible if we include pagination rules, which we've sorta been trying to avoid. Probably gonna have to happen eventually, I'm just not ready to take that plunge yet.
The technical reason (separate from the philosophical approach), is that it makes it possible to alternate between singing and speaking for a single character. If you, uhmmm, "infect"(?) nearby lines with lyrics, then you'd need some other notation or rule to manually undo that. Maybe that rule would be something like "a 2-space (blank-printing) line above and below can break application of the lyrics rules", but that's far more complicated than something like "Lyrics begin with ~".
-Clint
On Tuesday, February 28, 2017 at 10:26:29 AM UTC-8, Hendrik Noeller wrote: