Skip to content
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

Open
shaedrich opened this issue Jun 8, 2023 · 6 comments
Open

[EPIC] Fountain syntax extension #50

shaedrich opened this issue Jun 8, 2023 · 6 comments

Comments

@shaedrich
Copy link

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):

Title Status Proposed syntax Rendered as Suggested by
Stage directions discussion +stage directions+ <div style="text-align:right;">stage directions</span> @Reaper10
Sound effects discussion
  • ^sound effect
  • <sound effect
  • &sound effect
  • ^sound effect^
@Reaper10
Scene metadata discussion @severdia
Element references discussion [{label}]({type}:{identifier}) <a href="[{type}:{identifier}">{label}</a> utilizing CURIE/URN @shaedrich
dramatis personae discussion table https://scriptigo.com/help/fountain-format/133-improvements-to-the-fountain-format @severdia
Script lining discussion [[ and ]], starting with the word "LINE" vertical lines with different colors @shaedrich
Annotations discussion extended markdown syntax to highlight text (== and ==) in connection with footnotes ([^1] and [^abbr]: endnote text or ^[inline footnote]) <mark title="{label}">{text selection}</mark> @shaedrich
@stovak
Copy link

stovak commented Mar 27, 2024

I am +1 on the script lining.

I would, however prefer something like

[[SHOT "Scene 3 shot 3"]]
Tom shot himself in the head and
[[/SHOT]]
[[SHOT "Scene 3 shot 4"]]
The gun fell to the floor.
[[/SHOT]]

Then you could run a production report and get a shot list.

@shaedrich
Copy link
Author

Would you say, that a line and a shot are entirely identical?

@stovak
Copy link

stovak commented Apr 3, 2024

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

@stovak
Copy link

stovak commented Apr 3, 2024

[[LINE <label>]]
Tom shot himself in the head and
[[LINE <label2>]]
The gun fell to the floor.
[[/LINE]] [[/LINE]]

or you could do them like HTML tags... <line label="blah"></line>

@stovak
Copy link

stovak commented Apr 3, 2024

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.

<line label="blah" storyboard="storyboard.svg">
   Tom shot himself in the head and
     <line label="blah2" storyboard="storyboard2.svg">
        The gun fell to the floor.
     </line>
</line>

@shaedrich
Copy link
Author

shaedrich commented Apr 30, 2024

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

@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 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants