Live data from Hacker News

Fountain – A markup language for screenwriting

fountain.io

1–10 of 51 posts

Re: Fountain – A markup language for screenwriting

#3
This looks like a standardization of the way that screenwriting is done, rather than a revolutionary change in the way screenwriting is done. When I opened the .fountain file, I half-expected to see XML litter the place :-D

I could see myself writing a screenplay using this - and a really positive thing is that it imposes a framework on how I should be writing one. (I've tried multiple times, believe me)

Am really curious: what's the plan to foist this onto the Hollywood screenwriters?

Re: Fountain – A markup language for screenwriting

#4

This looks like a standardization of the way that screenwriting is done, rather than a revolutionary change in the way screenwriting is done. When I opened the .fountain file, I half-expected to see XML litter the place :-D I could see myself writing a screenplay using this - and a really positive thing is that it imposes a framework on how I should be writing one. (I've tried multiple times, believe me) Am really cu…

There are tools that let you convert Fountain to Final Draft (the due facto standard) and back, so I don't think foisting is needed.

Re: Fountain – A markup language for screenwriting

#6

This looks like a standardization of the way that screenwriting is done, rather than a revolutionary change in the way screenwriting is done. When I opened the .fountain file, I half-expected to see XML litter the place :-D I could see myself writing a screenplay using this - and a really positive thing is that it imposes a framework on how I should be writing one. (I've tried multiple times, believe me) Am really cu…

I'm not sure why this is making the front page of HN now. It's been around since 2012 and it's predecessor was around for a year or two before that. When they started, they advertised it as markdown for script writing (in fact, it extended a format literally called 'screenplay markdown'). It's not really a standardization of anything. If anything, it's a vast departure from the standard way of formatting scripts (which is to just use Final Draft). One of the driving forces behind fountain was the ability to write screenplays on the iPad. This was back when Final Draft was dragging their heels about releasing an iOS version.

Anyway, I doubt they have a plan to 'foist' this on anyone. It's another way to write screenplays that still produces what everybody expects to read: pdfs and final draft (fdx). There are a number of other formats that do this. I used a LaTeX extension at one point (but I don't recommend it).

Re: Fountain – A markup language for screenwriting

#7
The awesome thing about this is that it lets you use git. It's a shame your chances of finding a co-writer who can use git are negligible. I wonder what Final Draft etc do about version control?

Another thing: I wish I could work out a free, no-nonsense way of turning fountain into pdf on Linux. I've been going via html, which works OK but feels a bit dirty.

Re: Fountain – A markup language for screenwriting

#8

This looks like a standardization of the way that screenwriting is done, rather than a revolutionary change in the way screenwriting is done. When I opened the .fountain file, I half-expected to see XML litter the place :-D I could see myself writing a screenplay using this - and a really positive thing is that it imposes a framework on how I should be writing one. (I've tried multiple times, believe me) Am really cu…

> This looks like a standardization of the way that screenwriting is done

I don't think many people have written scripts in plain text since they stopped using typewriters.

Re: Fountain – A markup language for screenwriting

#9
Fountain lets me screenwrite like how I code, which is awesome. I use Goyo[1] and capslock.vim[2] to reduce distraction and make the capitalization easier. Git in Dropbox works well when only one person is committing.

1: https://github.com/junegunn/goyo.vim

2: https://github.com/tpope/vim-capslock

My cowriter uses afterwriting[3] (locally[4]) to view them although we still use unformatted .docx for rough drafts, since he normally writes those and I revise.

3: http://afterwriting.com/

4: https://github.com/ifrost/afterwriting-labs

Post reply on HN