cosmiciron

I beg to differ. People equate good writing with the cosmetics, which AI excels at, but it’s the substance that truly matters.

Its UI is too complicated for my taste. Besides, its screenplay support isn't perfect.

I'm not sure I understand what you are asking here. If it's some advanced feature, which is obviously out of my domain of expertise, you are welcome to participate and fork the project to implement it yourself.

AI helped me write the documentation because it does a better job than I ever could. I honestly wish I’d had AI to help me write my screenplay ten years ago.

I was an animation director, so I didn't do stunts. Sorry.

Who said I used HTML? It was impossible to write screenplay/manuscript in HTML and receive industry compliant outputs when printed/converted to PDF.

Because CSS is exactly what I wanted to avoid. I just needed predictable pager layout, and I didn't want to wrestle with CSS. Besides, this thing's tiny size allows it to run in a serverless function on the Edge, and that can be useful sometimes.

Why hide it?

And that's precisely why I'm neither a blockbuster director nor a massively paid "chief scientist", LOL.

As for the strange sentences? Before the web turned everything into paperless, infinite scrolls, people actually cared deeply about printed materials. With that came the strict requirement for pagination rules, widows, orphans, and deterministic behavior for margins. In fact, one of my favorite pieces of tech was built exactly around solving the discrepancy between display and print: NeXTSTEP with its Display PostScript technology.

To answer your question about the subtle difference between a line and paragraph break: mathematically, they trigger completely different layout states in a typesetting engine. A line break (soft return) just wraps text to the next line while preserving the current block's alignment and justification math. A paragraph break (hard return) ends the semantic block entirely, triggering top/bottom margins, evaluating widow/orphan rules for the previous block, and resetting the layout cursor for the next.

I had to build an engine that deeply understands this difference because in the film industry, screenplays are still written in Courier with strictly measured spatial margins and peculiar contextual rules on how blocks of dialogue break across pages. So this tool is basically my homage to an era long gone...

This project started from exactly there too until I couldn't push react-pdf any further. The MORE/CONT'D feature required by screenplay was impossible to implement with react-pdf's black box so I had to write my own.