Basta scrivere l'intestazione delle scene e i soggetti dei dialoghi in maiuscolo, seguendo l'ordine logico, in un normale file di testo allineato a sinistra. Poi caricarlo in
Screenplain che lo impagina correttamente in HTML, PDF o FDX (il formato di Final Draft). Ricordatevi di salvare il file in Unicode...
Oppure usare Fountain Loader:
Fountainloader, in questo caso salvando il file in UTF-8.
Il testo può essere caricato direttamente come Script in Final Draft, che riconosce Fountain (il markup language), eventualmente perfezionato da pochi, elementari comandi facili da memorizzare.
––––––––––––––––
Fountain Syntax | A markup language for screenwriting
To make any line a Transition, start it with a greater-than symbol.
Scene Heading (unless the line is preceded by an exclamation point !).
INT. HOUSE - DAY #1#
FLASHBACK (1944)
Fountain respects your line-by-line decision to single or double-space, taking every carriage return as intentional.
MOM (O. S.)
Luke! Come down for supper!
HANS (on the radio)
What was it you said?
You can force a Character element by preceding it with the "at" symbol @.
Manual line breaks are allowed in Dialogue, as are intentionally.
Dual, or simultaneous, dialogue is expressed by adding a caret ^ after the second Character element.
BRICK
Screw retirement.
STEEL ^
You create a Lyric by starting with a line with a tilde ~.
The requirements for Transition elements are:
Uppercase
Preceded by and followed by an empty line
Ending in TO:
> Burn to White.
If a line matches the rules for Transition, but you want in interpreted as something else, you have two options:
Precede it with a period to force a Scene Heading, or
Add one or more spaces after the colon to cause the line to be interpreted as Action (since the line no longer ends with a colon).
Centered text constitutes an Action element, and is bracketed with greater/less-than:
>THE END<
*italics*
**bold**
***bold italics***
_underline_
Markdown, emphasis is not carried across line breaks.
Information is encoding in the format key: value.
Title:
_**BRICK & STEEL**_
_**FULL RETIRED**_
Credit: Written by
Author: Stu Maschwitz
Source: Story by KTM
Draft date: 1/20/2012
Contact:
Next Level Productions
1588 Mission Dr.
Solvang, CA 93463
A page break is implicit after the Title Page. Just drop down two lines and start writing your screenplay.
Values can be inline with the key or they can be indented on a newline below the key (as shown with Contact above). Indenting is 3 or more spaces, or a tab. The indenting pattern allows multiple values for the same key (multiple authors, multiple address lines).
Page Breaks are indicated by a line containing three or more consecutive equals signs, and nothing more.
use a preceding ! to force the uppercase line to be Action:
Leading tabs or spaces in elements other than Action will be ignored.
A Note is created by enclosing some text with double brackets. Notes can be inserted between lines, or in the middle of a line.
[[It was supposed to be Vietnamese, right?]]
The empty lines around the Note on its own line would be removed in parsing.
If you want Fountain to ignore some text, wrap it with /* some text */. In this example, an entire scene is put in the boneyard. It will be ignored completely on formatted output.
Your /* ... */ pairs
They do not appear in formatted output.
Sections are optional markers for managing the structure of a story.
Create a Section by preceding a line with one or more pound-sign # characters:
# This is a Section
Synopses are optional blocks of text to describe a Section or scene.
Synopses are single lines prefixed by an equals sign =.
They can be located anywhere
U so anche mi che se catava e caaaaaaaase.