You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are scenarios where it may be preferable not to include page numbers in the PDF instead of including incorrect page numbers, e.g. when exporting a subset of scenes/pages to replace outdated pages.
Describe the solution you'd like
The addition of a command line boolean flag to toggle page numbers e.g.
$ wrap pdf My-Screenplay.fountain --no-page-numbers
Describe alternatives you've considered
I think the main alternative is afterwriting CLI , which uses the format:
The prospect of exporting replacement pages from Fountain implies the notion of page-locking, something which Fountain is supposedly incapable of achieving. Some years ago I suggested a small extension of the page break specification to enable "forced page numbers", which, in theory, would allow page locking. The thread is here: https://groups.google.com/g/fountain-dev/c/W_cAivCNhIk
Although the suggestion was well received, it was never implemented, and the development of the Fountain specification seems to have then fragmented between Fountain 1.1 and the (now quite separate) Highland format.
So page-locking remains in a kind of limbo.
The text was updated successfully, but these errors were encountered:
We could add some syntax for this to the Wrap format (probably best to follow suit with Highland or other popular tools if they have something like this) and use the same kind of logic for pagenumbers as we do for scene numbers. 🙂
The syntax I suggested to force page numbers is just the existing page break syntax plus an alphanumeric string, with any right-side = ignored (for aesthetic purposes only), e.g.
=== 12
===20===
==== 76A ====
But this is a bit off-topic for the initial feature of a --no-page-numbers type flag.
Is your feature request related to a problem? Please describe.
There are scenarios where it may be preferable not to include page numbers in the PDF instead of including incorrect page numbers, e.g. when exporting a subset of scenes/pages to replace outdated pages.
Describe the solution you'd like
The addition of a command line boolean flag to toggle page numbers e.g.
Describe alternatives you've considered
I think the main alternative is afterwriting CLI , which uses the format:
Additional context
The prospect of exporting replacement pages from Fountain implies the notion of page-locking, something which Fountain is supposedly incapable of achieving. Some years ago I suggested a small extension of the page break specification to enable "forced page numbers", which, in theory, would allow page locking. The thread is here: https://groups.google.com/g/fountain-dev/c/W_cAivCNhIk
Although the suggestion was well received, it was never implemented, and the development of the Fountain specification seems to have then fragmented between Fountain 1.1 and the (now quite separate) Highland format.
So page-locking remains in a kind of limbo.
The text was updated successfully, but these errors were encountered: