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

John August

  • Arlo Finch
  • Scriptnotes
  • Library
  • Store
  • About

Screenwriting Software

On error messages

May 8, 2014 Apps, Rant, Screenwriting Software

Brent Simmons has straightforward [advice on error messages](http://inessential.com/2014/05/05/error_messages):

> They should be of the form “Can’t x because of y.”

> A similar form is this: “Noun can’t x because y.” (As in “‘Downloaded.app’ can’t be opened because it is from an unidentified developer.”)

Badly-written dialog boxes make me lose faith in an app very quickly. Here’s Final Draft 9 when you hit Next on the last element in the Reformat box.

dialog box

Oh. Okay.

It has the icon for “important warning,” but it’s nothing I need to be warned about. We’ve reached the end of the document. That’s all.

Rather than making you close a new dialog box, the app could place a notification within the Reformat box itself.

Or better yet, do nothing. If you’re at the top of a script and hit Previous, FD9 doesn’t give you any warning. This feels like the better behavior, because you can see where you are anyway.

Simmons also warns against pronouns:

> One thing error messages never say is sorry. They’re just reporting, and they respect you enough to know you want the facts, clearly expressed, and don’t need to be apologized-to by a machine.

> Also: they rarely (if ever) use the words I, me, my, you, and your.

Here’s Final Draft 9 again:

dialog waring

A better way to phrase it might be:

**Can’t delete across a page break because pages are locked.**

Getting rid of the pronoun subtly changes the tone: “It’s not your fault, it’s just how things are.”

Highland as a bona fide screenwriting app

May 6, 2014 Apps, Highland, Screenwriting Software

As of this afternoon, version 1.7.1 of Highland has exactly one review on its main page in the Mac App Store:

I honestly never knew how much time I was spending formatting and making pages look pretty, until I started writing in Highland. I’m a more efficient writer, focusing on what a writer should be focusing on: words. I’ve switched over to Highland for my latest screenplay and I can honestly say that I will never go back. Highland is where I will write from now on.

The highest compliment I can pay this program is that it gets out of my way. It makes me want to KEEP writing. Which is a writer’s dream.

Jmedwarren’s five-star review is so lovely that I almost don’t want to tell him the backstory: Highland wasn’t meant for writing at all.

When we announced Highland in 2012, we billed it as a “screenplay utility” for converting between formats: PDF, FDX and the newly-minted Fountain. You dropped a file on it and selected a new file type.

This is what it looked like:

highland screenshot

The initial betas had no editing view, because we assumed users would write and edit Fountain using any of the excellent plain-text editors available. Likewise, we had no preview, because we were going to export a PDF or Final Draft file anyway.

In practice, we discovered that we often wanted to make small tweaks to a file we had just converted. For example, if we needed to modify title page information, it was a hassle to have to save the Fountain text, open it in iAWriter, fix it, then re-open it in Highland.

To avoid this round-tripping, we added a very basic editor and a preview. The user could switch between these views to see the changes reflected before export.

highland screenshot

As the betas progressed, we changed the UI significantly, moving from two tabs on the top to the current sidebar. ((The sidebar was prompted largely by plans for an iPad version of Highland.)) This is what version 1.7 looks like:

Highland 1.7

By the time we shipped — almost a year later — we saw ourselves largely as a companion to Slugline. They focused on writing while we converted files. ((To this day, Slugline still has a “Send to Highland” menu command.))

Still, I started to be comfortable calling Highland a screenplay editor rather than a screenplay utility. Last year, I wrote:

Highland is a great bridge between apps, but over the last year we’ve found more and more users are simply doing their writing in Highland. It’s a full-featured editor, with spelling, versions and find-and-replace. Because it’s plain text, you can focus on the words and not the formatting.

When asked if someone could write a script in Highland, my answer was generally, “Well, you could. But that’s not really what it’s for.” I steered users to other apps as alternatives. As a company, we spent our time refining Highland’s underlying engine for parsing PDFs and dealing with edge cases.

But people kept using Highland like a traditional screenwriting app. Or perhaps it’s better to say they used Highland in lieu of a traditional screenwriting app.

People like our app store reviewer Jmedwarren saw Highland as primarily a writing tool, not a converter.

So with version 1.7 of Highland, we’re embracing the fact that we’re really a screenwriting app. We don’t do everything other apps do, but we do some things significantly better, enough so that we’re the right choice for some screenwriters.

Highland pros and cons

Here’s where Highland is actually better:

Focus. When you’re writing in Highland, it’s just the words. There’s nothing to distract you. You can’t fiddle with margins, or futz with how the pages break. Even the little bits of syntax gray themselves out so all you see is your text.

Speed. Highland is lean and mean. From scrolling to previews, Highland is blisteringly fast. Because it’s Mac-only, we optimize it using the latest Apple technologies. Because we separate editing from preview, you’re never waiting for a long document to reformat as you type.

It’s hard to market speed as a feature, because you don’t think of a screenwriting app needing to be fast. But in practice, Highland feels better under your fingers.

Typography. Highland features Courier Prime and Highland Sans, two typefaces we commissioned. Screenwriters shouldn’t have to look at ugly fonts all day.

Standards. Because we helped forge the Fountain standard, Highland does it well. We’re often the first to incorporate new specs, such as lyrics and forced character names. But you can always open Highland’s files in any plain text editor, so you’re never stuck with us. If another screenwriting app comes along that’s vastly better, you can jump ship instantly.

Dark Mode. I don’t understand why more apps don’t offer it. It makes writing in dark places — or public spaces — much more comfortable.

PDF melting. This was Highland’s breakout feature. While other apps have added it, our PDF parsing is unmatched. It’s a tricky, thankless task, but a key part of both Highland and now Weekend Read, so we keep getting better.

Active development. Highland receives regular updates, sometimes twice a month, incorporating user-requested features in almost every build. We’re small enough to move quickly, but big enough that we’re not going out of business tomorrow. When things break — and they do — we fix them fast.

Created by working screenwriters. This is the hardest advantage to show, but probably the most important factor in why Highland works the way it does. I use Highland every day for actual paid work. I rely on it, so major and minor annoyances get addressed.

I’m not the only one using it, either. Justin Marks wrote me to say he was doing his latest feature largely in Highland, in part because it made working with lyrics so much easier.

These are some of Highland’s advantages, but there are things other screenwriting apps do better than Highland — or that we don’t do at all. Our work this next year will be figuring out what we can do to make Highland more useful without losing focus.

Outlining. I use Workflowy for outlining, but I’d love an integrated outliner that smartly leverages Fountain’s section and synopsis lingo. Slugline sort of does it, but its sidebar outline is mostly a navigator rather than a writing tool. (Still, Slugline’s sidebar is really useful for long documents, and I miss it sometimes.)

Revisions. Last week, I needed to turn in a draft with small changes. I really wanted to create starred changes in the margins without having to leave the comfort of Highland. We have ideas for dealing with revisions, both within the Fountain spec and on an app level, but it’s a challenging problem. For all my issues with Final Draft, it actually does a solid job with starred changes (and more complicated production features) once you understand how it works.

Collaboration. This is a topic for a longer blog post, but collaboration can mean both two people typing in the same document at the same time (like Google Docs) or the ability to suggest edits (like Draft). Both are useful. Both are difficult. But Fountain’s plain-text background is a huge help. Fully online tools like WriterDuet may be plenty for some writers, but I have a hunch there’s more to be done here, particularly for writers working on the staff of a show.

Title Pages. This is a Fountain issue as much as anything, but creating a title page in Highland is frustratingly hit-or-miss. We had good intentions; title and author metadata is part of the file itself, as it should be. But it’s very hard to get title pages to look the way you really want. We may call a mulligan and find a better way.

All of these issues are shortcomings, not showstoppers.

For my daily use, Highland is still a better way to write a screenplay. Particularly for my first drafts, I agree with Jmedwarren in that the best thing about Highland is that it gets out of your way.

We’ve redesigned the Highland site to reflect Highland’s role as a screenwriting app. Take a look and see how it works for you.

Final Draft and WGA registration

February 5, 2014 Follow Up, Fountain, Highland, Screenwriting Software

Update: Final Draft has removed the “preferred file format” line from their site.

In prepping for our [Final Draft episode](http://johnaugust.com/2014/the-one-with-the-guys-from-final-draft), I came across [this tidbit](http://store.finaldraft.com/final-draft-9.html) on their site:

> The market leader and the preferred file format of the Writers Guild of America West Online Script Registration.

That surprised me. Here is the actual wording on the [WGAw Registry website](http://www.wgawregistry.org/webrss/regdetails.html):

> Preferred file formats are ASCII, XML, PDF (Adobe Acrobat), Word, Final Draft , and Movie Magic Screenwriter 2000; however, all file formats will be accepted.

> In addition, other screenplay software and standard computer file formats are acceptable.

So according to the WGA Registry itself, Final Draft is **a** preferred file format, not **the** preferred file format. Which doesn’t seem to be a claim worth trumpeting that loudly, considering the other options include “all file formats.”

Final Draft does get a small logo on the WGAw Registry site, though. Final Draft put out a [press release](http://www.deadline.com/2013/11/final-draft-wgaw-final-draft-9-2014/) about that. So Final Draft has some special relationship with the WGA. Perhaps it’s the most preferred of all the preferred formats, which include basically anything capable of rendering text.

And speaking of text, ASCII! Younger readers might not even recognize this term. It’s the plainest of plain text, just 128 characters. Do you have a dot-matrix printer? Feed it some ASCII.

Since you can register basically any type of file, can you register scripts written in Fountain? Yes.

Fountain is just text. So if you’re writing a script in Highland or Slugline or Scrivener or Fade In or the growing number of apps that use Fountain, the WGA Registry is happy to take it. PDFs are also a good choice, because they look like a printed screenplay.

While we’re at it, *should* you register your script with the WGA?

I have no strong opinion. For legal purposes, it can be useful to show you wrote something before a certain date. It’s [no substitute for copyright registration](http://zernerlaw.wordpress.com/2010/12/03/it’s-time-for-the-writer’s-guild-to-shut-down-the-wga-registry/), but then again, in many cases the screenwriter and the studio will be engaging in the mutually-beneficial practice of claiming something was a work-for-hire. So I don’t have an all-purpose answer.

All I know is that if you choose to register your script with the WGA, it doesn’t have to be Final Draft.

Fountain 1.1 — “Use The Force”

January 29, 2014 Apps, Fountain, Highland, Screenwriting Software

We’re about to put out the first revision to [Fountain](http://fountain.io) since we launched it two years ago, and are calling for comment from users and developers.

When we were developing the plain text screenwriting syntax, we tried to balance normal uses and edge cases. Overall, I think we think we got Fountain mostly right. But Stu Maschwitz and I always expected that we’d evolve the specification as we learned more about how people use it on a daily basis.

The theme of the Fountain 1.1 update is “Use The Force.” It’s all about better control over “forcing” elements.

Most times in Fountain, you don’t need to force anything. It just understands what you want. But when you need to, you can force a Scene Heading with a leading period. You can force a Transition using a leading greater-than symbol.

For Fountain 1.1, we’re discussing adding two new forceable elements, and making a change to how Action is forced.

## LYRICS

Highland has been testing a Lyrics variation on Dialogue for a while now, and it works. We think it’s time to make it official.

You create a Lyric by starting with a tilde ~.

~Willy Wonka! Willy Wonka! The amazing chocolatier!

~Willy Wonka! Willy Wonka! Everybody give a cheer!

The parser will remove the ~ and leave it up to the app to style the Lyric appropriately. For screenplays, lyrics are often handled like a dialogue element, but in italics. ((Courier Prime italics are especially nice for lyrics.)) For stage musicals, it’s often uppercase and placed on the left margin.

Lyrics are always forced. There is no “automatic” way to get them.

## CHARACTER

The ability to force a Character element will be helpful for names that require lower-case letters, and for non-Roman languages, where a character might be named something like 黒澤.

To force a Character element, precede a line with the “at” symbol: @

@McCLANE

Yippie ki-yay! I got my lower-case C back!

The parser will remove the @ and interpret McCLANE as Character, preserving its mixed case.

Speaking of lowercase, one other change is that Character Extensions, the parenthetical notations that are on the same line as a Character element, are no longer required to be uppercase:

HANS (on the radio)
What was it you said?

The parser interprets HANS (on the radio) as a Character element.

## ACTION

Figuring out how to handle forced action required the most discussion.

Fountain interprets an uppercase line followed by a second line as a Character. Most of the time, that’s what you want:

MARY

Hi, Tom.

But sometimes you really want two lines of action, with no blank line between them. You’re going to for a style — but Fountain doesn’t know that. So instead you get:

BOOM

BOOM BOOM. Closer.

In Fountain 1.0, we allowed the user to force Action elements with two trailing spaces.

BOOM{two spaces}

BOOM BOOM. Closer.

This has turned out to be problematic in practice. The spaces are invisible, and can be introduced by accident as you write. Highland and Slugline users got confused. Hell, I got confused, and I co-created the syntax.

MARY{two spaces I didn’t realize were there}

Wait! Why isn’t my character name where it should be? Why isn’t my dialogue being handled like dialogue? Nima!

Furthermore, not all Fountain apps supported the spaces consistently.

In the end, we’d like more transparency and less invisibility. Using spaces to force Action should be deprecated.

In Fountain 1.1, we propose that users force Action by preceding a line with an exclamation point:

!BOOM
BOOM BOOM. Closer.

The parser removes the ! and interprets BOOM as Action.

BOOM  

BOOM BOOM. Closer.

Since forcing action is rare, and the other changes are purely additive (and evident to the naked eye), we don’t anticipate huge issues for most users.

Unless we hear a hue and cry about these changes, we anticipate making them official next week. Apps can start supporting this syntax shortly thereafter.

But we’re not stopping there. Upcoming goals for Fountain include:

1. Better consistency among apps when parsing Fountain. We keep finding edge cases, and want to make sure they are handled the same way regardless of which app you’re using.
2. New syntax for marking changes or highlighting elements in finished documents.
3. Continued development of screenplay-like formats, including three-camera and stageplays.

If you have notes or suggestions, I’d invite you to join the discussion on the [Take Fountain](https://app.glassboard.com/web/app/boards/dff2b3bf-5f61-4ab6-8a64-16c71dd57160) Glassboard. Registration is free and open to everyone.

« 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.