John August

Apps

Final Draft and WGA registration

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.

The One with the Guys from Final Draft

Episode - 129

Go to Archive

Apps, Directors, QandA, Scriptnotes, Software, Transcribed, WGA

The makers of Final Draft pay us a visit to clear up John and Craig’s misconceptions of, well, everything. It’s double the umbrage for your money.

Then we discuss Quentin Tarantino’s leaked script, the upcoming WGA negotiations, and how to make it clear you’re attached to direct your spec.

Links:

You can download the episode here: AAC | mp3.

UPDATE 2-6-14: The transcript of this episode can be found here.

Fountain 1.1 — “Use The Force”

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.

Highland wins 2013 Macworld Eddy

Apps, Highland

The editors of Macworld named Highland one of the [best products of 2013](http://www.macworld.com/article/2071020/macworld-editors-choice-awards-the-best-products-of-2013.html?page=2):

> Writing is hard. Writing a script or screenplay can be harder. That’s why we like Highland, Quote-Unquote Apps’ minimalistic $20 screenwriting tool. Highland offers writers a clean, unadorned space to work on their screenplay.

> All Highland files are saved as plain text, allowing you to open them in just about any program on your Mac, PC, or iOS device. You can even import your PDFs and Final Draft files into the app for easy editing, and then export them back into their original formats for further work.

> Certainly for those in the film industry, this app is more than worth its price.

Many thanks to the editors of Macworld, and big congratulations to the Quote-Unquote apps team for their hard work on Highland.

Nima Yousefi has built and rebuilt Highland’s parsing engine a dozen times, taking it from impressive to magical to so-good-you-forget-it’s-difficult. (The next build is even better.)

Ryan Nelson has designed and tweaked our graphics down to the pixel. Minimalism is hard, because there’s nothing to hide behind.

Stuart Friedel keeps tabs on sales figures and industry chatter. He and I use the app daily, so it’s often our observations and annoyances that set the agenda.

I was excited to see so many other apps I love on the list of Eddy winners, incluing 1Password, Badland, Bartender, Capo, Drafts 3, Fantastical 2 for iPhone, Gone Home (Craig’s One Cool Thing), IFTTT, Launch Center Pro, and nvAlt.

For 2014, we’ll be keeping up development of Highland while introducing a new app that works related magic for folks who deal with screenplays.

In the meantime, you can [check out Highland](http://highland.quoteunquoteapps.com/blog-eddy) on the Mac App Store.