Sometimes you want to write something with broken lines and you write in the editor:

That’s right I’m Sokka
It’s pronounced with an Okka
Young Ladies, I rocked ya!

But it ends up looking like this:

That’s right I’m Sokka It’s pronounced with an Okka Young Ladies, I rocked ya!

The fix is to add two spaces between the final character and the carriage return.

I don’t understand what the problem is. CR should be easy enough to translate, and the users intentions are clearly confirmed because they’re looking right at what the expect it to look like when they hit submit.

Why does the user have to add two spaces? Why is the universe like this?

Edit: Holy Shit, look, I’m just an idiot typing text expecting WYSIWYG and I don’t see a good reason for why I’m not getting it other than that programmers lack theory of mind.

  • schipelblorp@sh.itjust.worksOP
    4·
    6 days ago

    “ANSI” was one of the earliest and most basic forms of rich text, again completely built on top of ASCII, and is still used sometimes for terminals today. It allows some basic colors and bold/underline, occasionally supporting double-width or italic.

    Oh, yes, ANSI. I’m having flashbacks to all the dark blue text on black background.

    I’ve had fights with Word condensing cut-and-pasted text from the web to print; one sticking point was having to search and replace pairs of both CR and LF. Oy vey.

    Thanks for the detailed explanation! Sounds like QWERTY–a decision that had good reasons behind it and kinda got stapled into a situation where maybe a different decision would have been made for the purpose, but now everyone’s used to it and it’s good enough the way it is.

    • cecilkorik@lemmy.caEnglish
      2·
      6 days ago

      Yeah, I think that’s a fair summary! I have to admit I’m still fond of ANSI (and some of the old DOS extended ASCII that included all kinds of fancy UI and box drawing characters) but it’s mostly nostalgia, and there’s the whole different rabbit hole of extended ASCII code pages to get into. :)