This is largely the reason I gave up on rich text editors in favor of a plain text source and some sort of rich text compiler.
There is an absolutely mind boggling amount of programming work that goes into making a WYSIWYG word processor. and this complexity tends to bleed out into editing quirks and corrupted documents. Not that there are no quirks or corruption with an explicit separate compiler it is just that it will not touch your original source, so you can fight the quirks in a systematic way. I think this is why word perfect users love the show codes function so much.
"You know why they call a word processor right? Have you ever seen what a food processor does to food?"
This is largely the reason I gave up on rich text editors in favor of a plain text source and some sort of rich text compiler.
I have written a lot of words in troff/groff + various macros and adjacent tools (eqn, pic) over many years and produced consistently decent if plain looking documents. And I've started using it again. Still covers about 85% of getting words on paper in a readable format. Spent lots of time with LaTeX, too, which produced perhaps nicer looking documents over all (and beautiful mathematics), but at the expense of much more complexity; YMMV.
There is an absolutely mind boggling amount of programming work that goes into making a WYSIWYG word processor. and this complexity tends to bleed out into editing quirks and corrupted documents. Not that there are no quirks or corruption with an explicit separate compiler it is just that it will not touch your original source, so you can fight the quirks in a systematic way. I think this is why word perfect users love the show codes function so much.
"You know why they call a word processor right? Have you ever seen what a food processor does to food?"