search

lmparppei / Beat

Beat - a simple and elegant screenwriting app for macOS
Other
168 stars 29 forks source link

Bug: Fountain 1.1 spec has narrower criteria for transitions #153

Open rnkn opened 3 months ago

rnkn commented 3 months ago

Describe the bug The Fountain 1.1 spec has narrower criteria for transitions:

The requirements for Transition elements are:

  • Uppercase
  • Preceded by and followed by an empty line
  • Ending in TO:

Beat appears not to follow the last criteria, i.e. ending in TO:, which makes things like FADE IN: or TITLE: parse/export as transitions.

Screenshots

screenshot

macOS version Sonoma 14.5 (23F79)

lmparppei commented 3 months ago

That's actually something that some users asked for to make Fountain a bit more language-agnostic, but agreed, that it can break documents for some others. I'll consider just returning back to TO:.

rnkn commented 3 months ago

Interesting. What other languages does it help with?

lmparppei commented 3 months ago

Interesting. What other languages does it help with?

Multiple languages, including Finnish, where you can have something like:

LEIKKAUS: (Cut to:)
RISTIHÄIVYTYS: (Dissolve to:)
and so on.

But yeah, this is where you should use > to force the transition. My reasoning was originally to avoid too many English keywords, and I saw some other Fountain parser accept transitions without TO: as well. But for consistency, this will now change!

rnkn commented 3 months ago

Of course! I thought other markup languages.