-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Fountain syntax extension #50
Comments
I am +1 on the script lining. I would, however prefer something like
Then you could run a production report and get a shot list. |
Would you say, that a line and a shot are entirely identical? |
yes. My bad. Line is the visual implementation of a shot item. Either work, IMHO |
or you could do them like HTML tags... |
If you implemented them as "html-style" tags, you could have a writing view that ignores production tags, and a production view that you can match up to storyboards.
|
@stovak Thank you for your suggestions, much appreciated 👍🏻 Sorry for my late reply. I needed to settle on how to put my understanding into words 😅 My understanding was, that they are similar, yet not entirely identical, however, they could happen to point to the same thing, just not in general. What I mean, is that in my head (correct me if I'm wrong), a line is more synonymous with a camera setup than a shot since a camera setup can consist of one shot only but can also consist of multiple. But I'm not an expert, so I might be mistaken. Also, while line is a pre-production term, shot is a principal photography term and that might feel like mixing two very different workflows of two very different crew members. What I like about your XML/HTML style tags is the ability to add additional attributes like the storyboards 👍🏻 |
I thought, it might be a good idea, to collect all issues concerning syntax extension to have kind of an overview of where we stand on these issues (maybe @nyousefi can create a label for that):
+stage directions+
<div style="text-align:right;">stage directions</span>
^sound effect
<sound effect
&sound effect
^sound effect^
[{label}]({type}:{identifier})
<a href="[{type}:{identifier}">{label}</a>
utilizing CURIE/URN[[
and]]
, starting with the word "LINE"==
and==
) in connection with footnotes ([^1]
and[^abbr]: endnote text
or^[inline footnote]
)<mark title="{label}">{text selection}</mark>
The text was updated successfully, but these errors were encountered: