Screenplain:

News

July 22nd, 2012

Fixed a bug that appeared on the last update, which made dual dialog fail for HTML output.

July 10th, 2012

A paragraph starting with more than one period (like an ellipsis) is not parsed as a scene heading.

Leading spaces in character names in dialogue are stripped for output.

Page breaks in Fountain (three or more =) are parsed and output in HTML.

March 1st, 2012

Got rid of the extra vertical space when the screenplay has a forced line break.

When writing HTML output, Screenplain now creates <br/> tags instead of new <p> tags for line breaks. This is more in line with how you are supposed to use those tags, but more importantly the CSS assumed it.

Note:

• Feedback is appreciated. Contact me on my blog or Twitter!
• The file should use the Fountain syntax.
• Plain text only! Input formats like Word documents, PDF, RTF, etc. are not supported!
• Currently supports output to Final Draft (FDX) and HTML.
• Output as text and PDF will come later.
• The following features of Fountain are currently supported:
  • Emphasis: Bold, italic and underline
  • Scene heading (slug)
  • Scene numbers
  • Sections
  • Character, Dialog and Parentheticals
  • Dual Dialog
  • Action
  • Transitions
  • Centered text
  • Explicit line breaks
  • Boneyard (commenting out)
  • Synopsises
  • Title page (ignored on output)
  • Page breaks
• Not implemented yet:
  • Title page output
  • Notes