Fuller handling for headings, notes and synopses

[arikrupnik]

fountain specification includes a number of markers that aid in structuring a screenplay which are invisible in final output: [[note]], /* comment */, #ATX header (###with multiple levels of hierarchy) and =synopsis. Textplay deletes notes and comments, and converts the rest to <note> in its internal XML. It then converts these to <Paragraph><ScriptNote><Text> for FDX and <p class="comment"> for HTML.

In my use case, it is helpful to have explicit structure to the screenplay (breaking it into acts and sequences, and scenes into shots). My use case mostly uses the XML output of Textplay. Depending on your level of interest in this feature, here are three proposals on incorporating it into Texplay:

• Continue ignoring [[note]] and /* comment */ to avoid dealing with multi-line issues. Convert ATX headers to <h1> - <h6> or similar in internal XML and =synopsis to <synopsis>. For HTML and FDX, convert all these Textplay converts <note>s now. This is the least intrusive option.

• As above, but preserve these elements in HTML and FDX. For HTML, this would mean either amending the CSS to differentiate new headers from existing uses for sluglines and transitions or replacing them with something like <p class=header1> and setting display: none in CSS.. I don't know how FDX handles headers and document structure, but I expect there's some use it can make of this information.

• As above, but handle multi-line notes and comments as well. This would require stepping away from the line-oriented processing Texplay employs, at leas for these elements. Multi-line notes are not important to my use case, but may be for others.