join paragraphs of dialog or action which are broken over multiple lines deliberately (as ventilated prose or sense lines) for simpler changes tracking in git. They could be saved broken over multiple lines in the original fountain file, then the linter could join them before PDF etc. export or to save as a final draft.
Fixup of wonky ellipses: groups of two (three?) or more dots or spaces e.g. word. . .word or word... word or word . . .word or word . . . word corrected to word...word.
Replace all em-dash and en-dashes and word - word or word -- word with word--word.
Flag all end of scene slug daylight descriptions which are not either --DAY or --NIGHT for the user to correct them for production usability. --DUSK or --DAWN or --TWILIGHT or --EVENING make production planning more difficult. OR alter them all to --NIGHT for INT. scenes (a safer production planning bet--and dark indoor scenes should have that in the slug even if technically the scene is set during daytime) and --DAY for EXT. scenes.
Other things I list here suited for exact regex matches, or things I solve here (which is a tool I'm deprecating but has regexes perhaps portable for this task).
I have opinionated use cases to suggest:
word. . .word
orword... word
orword . . .word
orword . . . word
corrected toword...word
.word - word
orword -- word
withword--word
.--DAY
or--NIGHT
for the user to correct them for production usability.--DUSK
or--DAWN
or--TWILIGHT
or--EVENING
make production planning more difficult. OR alter them all to--NIGHT
forINT.
scenes (a safer production planning bet--and dark indoor scenes should have that in the slug even if technically the scene is set during daytime) and--DAY
forEXT.
scenes.