Open vekuda opened 5 years ago
We currently use the Afterwriting library for rendering the PDF preview and export. The most straightforward solution would be if there were a way to toggle automatic (CONT'D) via the library options, though I don't see this as an option. There is an issue that mentions a feature, but it doesn't have a lot of details. It might be better to move the conversation there and see what their team thinks about it.
I'm personally somewhat in agreement with John August's argument that use of (CONT'D) is context sensitive enough that it's better to do manually. However, I could see it being useful if there is a well-enough accepted set of rules on when CONT'D should be automatically added.
I think the only one that should be automatic is the page break. Modern conventions don’t require them when action breaks up a character’s dialogue.
@superlou So do you suggest that I should open a new issue on their repo?
I'm personally somewhat in agreement with John August's argument that use of (CONT'D) is context sensitive enough that it's better to do manually. However, I could see it being useful if there is a well-enough accepted set of rules on when CONT'D should be automatically added.
Same for me.
I would keep it Manual, but I reckon that I might switch it on for fast-paced projects or that some writers would keep it Auto by default...
I'd recommend posting in that existing repo, and opening a new feature request if they think that a new issue is needed to flesh out the requirements.
'Auto-add (CONT'D) to PDF' could be a very useful tool, depending on writer's preference.
There are those who always use the (CONT'D), and those who are writing a contemplative story, or who just don't like that dialogue reprises include the (CONT'D). That's why the necessity of making it optional.
Displaying the various (CONT'D)s on the Fountain file itself might cause headaches to the devs or practical issues to the users, but having them displayed on the PDF preview / export - depending on how the toggle is set - is definitely what I am suggesting here.
I don't know if it can be ported by the develoipers, but there's a pull request for VS Code's Better Fountain which seems to address this very improvement.