Jump to content
Storyist Forums

Search the Community

Showing results for tags 'fountain markdown export'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Storyist for Mac
    • Announcements
    • Using Storyist
    • Feature Requests
    • Troubleshooting
    • Sharing
  • Storyist for iPad
    • Announcements
    • Using Storyist for iPad
    • Feature Requests
    • Troubleshooting
  • Community
    • Novel Writing
    • Screenwriting
    • Writing Resources
    • General Topics
    • Member Introductions and News
    • Writers' Lounge
    • NaNoWriMo 2007
    • NaNoWriMo 2008
    • NaNoWriMo 2009
    • Script Frenzy 2010
    • NaNoWriMo 2010
    • Script Frenzy 2011


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. I didn't pay much attention to the .fountain support in v1.3. I've always liked the idea of the markdown type metatagging you can do in plain vanilla text files, but I'd rather just write than worry about formatting the text until much later in the process. One thing that has kept me from using Storyist is the prorpietry format of the storyist project files. I want to edit a manuscript on my PC as well as my iPAD, bouncing between the two via Dropbox. As I don't own a MAC, I don't have any way of accessing my files outside of my iPAD. Yes, I could just export as a text file, but that would mean I'd lose any metadata (such as synopses or comments) when I reimported the file. I then started experementing with final draft format, still a propriety format but one at least that several 3rd part editors can import/export. But I finally tested out .fountain and was delighted to find out that Storyist parses the text file and allows you to work as if it was a normal screenplay document. It also saves your synopses and comments, as well as the index cards when you export as a .fountain text file. Now it's not perfect. I found in a simple test that I'd loose my first synopsis and index card label when I'd export then reimport the file. Corruption seems to increase if you keep simply exporting and reimporting, probably due to the heuristic contextual processing of screenplay elements that don't have definitive tagging. It als doean't seem to support the section tag ("#") which I'm sure everyone recognises from the novel manuscript format. However, it does seem to be a nice way of using the features of Storyist (excluding index card colors) while remaining in plain text format. I wonder if this import/export ability could be extended to the novel format and not just the screenplay. In fact, maybe it would be better to have a subset of .fountain tagging that could be done to novel manuscripts rather than potentually accidentally tagging upper case words as action or dialog: Scene Headings (index card labels). Start line with a period - .The Factory Notes. Encase note in double square brackets - [[this is a note]] Synopses (text on index cards) - start (and end?) line with equals sign. =this is a synopsis= Sections. Use # symbol at start of line (up to 3 deep) - #Chapter 1 ##Beginning ###Intro #Chapter 2 Other formatting commands could be added, for bold or italic text for instance, but anything not tagged would be considered body text. Most of this can of course be done right now, just using the screenplay template to begin. However I think having a subset of fountain available to use (that won't confuse body text with screenplay tags) I think would be very useful.
  • Create New...