1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
About Screenplain
=================
You're a hacker. The command line is your home. You know tools like grep, sed
and Git inside out. You have formed a symbiotic relationship with your text
editor. Those tools are powerful in the right hands. But you're also a
screenwriter. Screenwriting is much like programming. It's about structure and
form, and -- obviously -- about reading, writing and modifying huge amounts of
text. You don't want to use software that lacks the power of your hacking
tools just because you're writing a screenplay instead of a shell script.
Enter Screenplain.
Screenplain allows you to write a screenplay as a plain text file. Text files
are simple and supported by all text manipulation software. It's not just for
hackers, too. The simplicity of plain text allows you to easily view and edit
them on devices such as tablets and phones. No need for specific screenwriting
software.
The magic that Screenplain performs is to take your plain text file and
convert it to a good looking PDF in standard screenplay format. Send that file
off to your producer, agent, director or screenwriting competition.
An [Online version of Screenplain](http://screenplain.appspot.com) is
available, running on Google App Engine.
Note that Screenplain is under development and is missing features and
the master branch may not always work.
Thanks for the inspiration goes to:
* [Stu Maschwitz](http://prolost.com) for the [Screenplay Markdown](http://prolost.com/spmd)
post that got me around to actually publish this work when far from finished.
* [John August](http://johnaugust.com/) for the [Scrippets](http://scrippets.org/) project.
The idea for that is similar, as it converts plain text to a formatted output. The focus of
Scrippets is on presenting snippets of screenplays online, specificially in blog posts and
comments. Screenplain's format is similar to Scrippets.
Input format
============
The input to Screenplain is *Screenplay Markdown* as [proposed by Stu Maschwitz](http://prolost.com/storage/downloads/spmd/SPMD_proposal.html).
License
=======
Screenplain is released under the [MIT license](http://www.opensource.org/licenses/mit-license.php).
Developing
==========
As it should run under Google App Engine, Screenplain should be
compatible with Python 2.5. Use that version for development to make
sure it works. Python 2.5 is no longer available in Ubuntu at least,
but see
[this link](http://kovshenin.com/archives/installing-python-2-5-on-ubuntu-linux-10-10/)
about how to install it.
To install reportlab, you'll need Python's development files. In
Ubuntu, just do
sudo apt-get install python2.5-dev
Set up environment using virtualenvwrapper:
mkvirtualenv -p python2.5 --no-site-packages screenplain
pip install -r requirements.txt
|
