• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

John August

  • Arlo Finch
  • Scriptnotes
  • Library
  • Store
  • About

Screenwriting Software

Fountain, 10x faster

June 25, 2012 Geek Alert, Highland, Screenwriting Software

We’re keeping Nima Yousefi busy working on Highland, but he’s found time to push a major update to [Fountain](http://fountain.io/), the open-source format and code library that [makes the magic possible](http://nimayousefi.com/2012/06/fountain-update/):

> It came to our attention that on iOS devices the parser’s performance was less than stellar. In fact, it was pretty terrible.

> Long story short, now there’s FastFountainParser. It’s a traditional line-by-line parser and roughly ten times faster than the old one. So, that’s a win.

What this means for screenwriters: Fountain-based screenwriting apps for the Mac and iPad will be much, much faster.

Also included in the package: our libraries for HTML export and pagination.

> It splits large dialogue blocks up across pages, adding the appropriate MORE and CONT’D, and is smart enough not to split in the middle of a sentence.

Fountain is designed to be completely agnostic — you can write Fountain in almost any app that generates text. That said, specialized apps can do amazing things, and we want developers to have a consistent base to jump off from.

I’ve had the chance to try out some of the forthcoming apps. You’re going to love them.

Getting to page one

Episode - 41

Go to Archive

June 12, 2012 Follow Up, Screenwriting Software, Scriptnotes, Transcribed

On the 41st Scriptnotes, John and Craig discuss screenwriting software, knowing when to start, and the Game of Thrones finale. But before moving on to new business, they update us on two topics of podcasts past.

Last we heard about Disney and Amazon Studios, there was a [vacancy atop the former](http://johnaugust.com/2012/the-disney-dilemma), and the latter had [decided to become a WGA signatory](http://johnaugust.com/2012/amazons-new-deal-for-writers). Now, Disney has hired Alan Horn as chief, and Amazon has announced its first project — but with no mention of the writer.

After they weigh in on these new developments, John tells us about the pros and cons of writing his most recent script in Scrivener, which opens up into a larger discussion about where screenwriting software seems to be heading.

Craig and John then adress a common frustration of beginning screenwriters: How do you know when you’re ready to move from the planning phase onto page 1? Diving into a script too quickly is a recipe for second-act problems, but overplanning can be just as dangerous. Where’s the sweet spot? What must you know about your story before you start, and how much familiarity is overkill?

They then move onto a listener-requested discussion of the Game of Thrones season finale, plus this week’s two One Cool Things.

Rawson Marshall Thurber, enjoy this Google alert made specially for you, courtesy of episode 41 of Scriptnotes.

LINKS:

* [Scrivener](http://www.literatureandlatte.com/scrivener.php)
* [Fountain](http://fountain.io/) and [Highland](http://quoteunquoteapps.com/highland/)
* [Fade In](http://www.fadeinpro.com/)
* [Final Draft iPad Writer](http://www.finaldraft.com/products/mobile/writer/)
* [Bronson Watermarker](http://quoteunquoteapps.com/bronson/)
* [Stencyl](http://www.stencyl.com/)
* [Flight](https://www.youtube.com/watch?v=xnVNNR6CEOE) trailer
* [Craig’s Wordplay post](http://www.wordplayer.com/pros/pr14.Mazin.Craig.html) on building marketing hooks into your screenplay
* INTRO: [Silver Spoons](http://www.youtube.com/watch?v=71RyZuJHpj0) opening
* OUTRO: [Garden of Your Mind](http://www.youtube.com/watch?v=OFzXaFbxDcM&feature=youtu.be) by Mister Rogers (remix)

You can download the episode here: [AAC](http://traffic.libsyn.com/scriptnotes/scriptnotes_ep_41.m4a).

**UPDATE** 6-14-12: The transcript of this episode can be found [here](http://johnaugust.com/2012/scriptnotes-ep-41-getting-to-page-one-transcript).

Say hello to Highland

February 16, 2012 Follow Up, News, Screenwriting Software

Today we’re announcing the beta release of [Highland](http://quoteunquoteapps.com/highland), our new screenwriting utility.

highland logoHighland lets you convert files between PDF, Final Draft (.fdx) and Fountain. It works in all directions.

→ It creates perfectly-formatted PDFs from Fountain or FDX files.

→ It creates future-proof Fountain files you can edit in any text editor.

→ It melts PDFs, making them editable.

That last part is basically magic. Highland can take almost any screenplay PDF and convert it back to an editable file in seconds.

Here’s a quick walk-through video I made to show how it works:

Highland is a Mac app. We’ll be selling it through the Mac App Store. But before we do that, we need screenwriters to beta test it.

This changes everything (into everything else)
—-

Screenwriters generally work with two kinds of files.

**Native files** like .fdx are for writing and editing. You need specific applications to use these files. They’re prone to obsolescence. If you have any old WriteNow files on your computer, you’ll have a hard time reading them.

**PDFs** are universal, and can be opened on nearly any device. Like digital paper, they’re basically frozen versions of the screenplay. They’re difficult to edit, in part because all the semantic information has been lost.

Last week, we introduced **Fountain files**, which split the difference between native files and PDFs. Because they’re plain text, they’re both universal and highly editable, since they can work with any text editor — and should for decades to come.

Highland is a quick way to move between these three formats.

Obviously, Highland is extremely useful for screenwriters who want to work in Fountain, or want to open a Final Draft file but don’t have the app. But its ability to convert PDFs is probably going to be its most-discussed feature.

Melting PDFs
—

It’s standard practice for screenwriters to deliver PDFs. Readers can easily read and print PDFs, but it’s onerous to change them — so they don’t.

As screenwriters, we’ve relied on security through difficulty: producers, directors and executives aren’t likely to mess with the PDF of a script because it’s just too much hassle.

Fountain takes away the hassle, for better or worse.

I fully expect some pitchforks: *How dare we assist the meddlers?*

I’d argue that there’s nothing inherently “safe” about turning in a PDF. Producers have always been able to muck around with scripts — it was just a lot of work. Relying on laziness is really no security at all.

With Highland, we’re going to respect the basic safeguards a screenwriter might take:

1. If you password-protect your PDF, Highland won’t convert it.
2. If your PDF is just a bunch of images, Highland won’t convert it. (For example, you could print your script then scan it, or use a feature like Bronson Watermarker’s “Deep Burn.”)

Could a meddling producer work around these safeguards? Absolutely. But she could also just have her assistant retype your script. That happens every day.

Highland and Fountain
—

LA-based screenwriters will have already guessed the origins of “Highland.”

Highland Avenue is a major north-south artery through Hollywood, just as Fountain is the famous east-west shortcut.

Much like how the real streets intersect, Highland and Fountain work well together — but they’re not the only ways to get somewhere.

Just as you can take many routes to drive through Hollywood, you should have lots of alternatives for working with your screenplay.

[Fountain](http://fountain.io) is an open-source markup scheme. We’re happy to see a lot of other developers embracing it. Some of them will come up with apps that are better than Highland, either by doing more or doing it smarter.

That’s the goal. That’s success.

But for today, Highland makes working with Fountain a lot easier. After this beta test, we hope to have an app that makes it effortless to move between formats and platforms.

If you want to help, we’re [accepting beta-testers now](http://quoteunquoteapps.com/highland#beta-signup). For this first round, we’re looking for fairly tech-savvy screenwriters — the app will fail, and we’ll need your help figuring out why. Down the road, we’ll expand the beta to get a better cross-sampling of users.

[Updated at 3:30pm: Due to great response — thanks! yikes! — we have all the beta testers we need for now. Follow us [@qapps](http://twitter.com/qapps) for news on future betas.]

We’re only going to add a few beta testers at a time, so not everyone will get picked. But if all goes well, we should be an inexpensive download before too long.

One More Thing
—

Remember my frustration about Final Draft’s old, incompatible .fdr format? The one with the [five-step workaround](http://johnaugust.com/2012/convert-old-final-draft-files-in-five-clever-but-tedious-steps)?

Well, Nima solved that last night. Highland will be able to open and convert .fdr files to modern formats.

Convert old Final Draft files, in five clever-but-tedious steps

February 14, 2012 Follow Up, Geek Alert, Screenwriting Software

Last week, I [urged](http://johnaugust.com/2012/pricing-fdx-reader) Final Draft to release a free converter app to let screenwriters move their old-and-busted .fdr files to the newer .fdx format.

A reader wrote in to say that Final Draft already has one. Sort of.

The evaluation version of Final Draft 8 — which supports both .fdr and .fdx — is free on the Final Draft website.

You can open an .fdr file, then save it as .fdx. The problem is, the evaluation version is limited to 15 pages.

[Mac Harwood](http://MacHarwood.blogspot.com/) has a solution:

> 1. Select the menu Format > Elements to bring up the Elements dialog box.
> 2. In the Font tab, select ‘Set Font’ and change the font size to ’1′.
> 3. Then press Apply Font/Size to all elements.
> 4. In the Paragraph tab, set ‘Space before’ to be 0, and then do the same for each element.

> Now the 200 page epic will only be a few pages, which you can save with the evaluation version.

This works, but the resulting file is a mess of tiny letters. His fix:

> Just open up the created .fdx file in your favourite text editor (I use Notepad++) and do a search and replace for all occurrences of “Size=1″ to a blank. Then save.

This workflow could save your life if you were stuck somewhere with an .fdr file and no way to open it, but it’s hardly a practical solution for screenwriters staring at folders full of old files. ((If someone out there finds a way to automate this crazy workflow, let me know.))

Erik Harrison offers a possible explanation for why a Final Draft converter isn’t forthcoming:

> There probably ISN’T a file format [for .fdr]. It’s likely just a binary dump of the state of internal memory at the time of save. Certainly that was true of a lot of word processors I used in the old day, and even still is true for Word in some senses.

If that’s the case, it helps explain why the new iPad app doesn’t support .fdr. In order to support the old format, the app would have to duplicate way too much of the full Final Draft.

« Previous Page
Next Page »

Primary Sidebar

Newsletter

Inneresting Logo A Quote-Unquote Newsletter about Writing
Read Now

Explore

Projects

  • Aladdin (1)
  • Arlo Finch (27)
  • Big Fish (88)
  • Birdigo (2)
  • Charlie (39)
  • Charlie's Angels (16)
  • Chosen (2)
  • Corpse Bride (9)
  • Dead Projects (18)
  • Frankenweenie (10)
  • Go (30)
  • Karateka (4)
  • Monsterpocalypse (3)
  • One Hit Kill (6)
  • Ops (6)
  • Preacher (2)
  • Prince of Persia (13)
  • Shazam (6)
  • Snake People (6)
  • Tarzan (5)
  • The Nines (118)
  • The Remnants (12)
  • The Variant (22)

Apps

  • Bronson (14)
  • FDX Reader (11)
  • Fountain (32)
  • Highland (73)
  • Less IMDb (4)
  • Weekend Read (64)

Recommended Reading

  • First Person (88)
  • Geek Alert (151)
  • WGA (162)
  • Workspace (19)

Screenwriting Q&A

  • Adaptation (66)
  • Directors (90)
  • Education (49)
  • Film Industry (491)
  • Formatting (130)
  • Genres (90)
  • Glossary (6)
  • Pitches (29)
  • Producers (59)
  • Psych 101 (119)
  • Rights and Copyright (96)
  • So-Called Experts (47)
  • Story and Plot (170)
  • Television (164)
  • Treatments (21)
  • Words on the page (238)
  • Writing Process (178)

More screenwriting Q&A at screenwriting.io

© 2025 John August — All Rights Reserved.