2026-07-29 15:03 UTC
@fanf@mendeddrum.org Back in the day I wrote a program to optimize printing of text files containing such shenanigans, and what I ended up doing was reading the whole line, outputting *just* the overstrikes, sending a carriage return, and outputting the letters.
* It was WAY faster, especially on a device with an actual carriage that moved and had inertia.
* If you were displaying on a device that didn't handle overstrikes (like a CRT) the result was still readable.
Replies (1)
-
@resuna@ohai.social 2026-07-29 15:08
@fanf@mendeddrum.org It also did things like sending a line feed followed by an escape sequence if it knew the output was a CRT because \E=YX or even \E[XXX;YYYx was shorter than a bunch of spaces and tabs. Edit: Also that meant it didn't screw up when some MF changed the terminal tabstop settings.