Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Fountain Support Appreciated
-
Thank you for adding support for Fountain. This is brilliant and greatly appreciated. Writing on iOS with Editorial is now almost exactly like using Highland on the desktop. On iOS I no longer have to push the script to Weekend Read to see it rendered, which saves time.
There is one part of the specification that isn't working properly and may just be a bug.
Fountain should respect line endings in action/description blocks, but in v1.2 the blocks get wrapped into normal paragraphs.
For example, if action is written this way:
He stared at the treasure.
Gold. Silver. Jewelry.
All his dreams come true.
A king's ransom, but how to get it out?
Searching...for answers.it should remain as written. However, in v1.2 it gets wrapped like this when previewed:
He stared at the treasure. Gold. Silver. Jewelry. All his dreams come true. A king's ransom, but how to get it out? Searching...for answers.
This happens even if double spaces are added after each line ending (like Markdown).
Here's what the spec says:
Action, or scene description, is any paragraph that doesn't meet criteria for another element (e.g. Scene Heading, Character, Dialogue, etc.). Fountain respects your line-by-line decision to single or double-space, taking every carriage return as intentional.
So far, this is the only issue I've discovered with the current previewer.
Again, thank you very much for adding Fountain support.
My environment: iPad Air (first gen), iOS 8.3
-
The fountain support is really awesome. Seems to work great for the most part. Love the syntax highlighting, it improves readability tremendously.
Is there any way to highlight inline notes [[notes]] as well? These are notes in the fountain spec that don't show up in the finished document. I couldn't find anything in the documentation one way or the other.
The app is really awesome, thanks for everything! -
To WRK3
i meet the same problem than you. I get around that problem using this workflow: FOUNTAIN PREVIEW by /olemoritzhttp://www.editorial-workflows.com/workflow/5215636485570560/diZz8hHAW1c
