3 ms·

> which causes the renderer to overwrite the earlier text making it invisible No. It does not overwrite anything nor does it make anything invisible. The only

> which causes the renderer to overwrite the earlier text making it invisible No. It does not overwrite anything nor does it make anything invisible. The only thing the codepoints you're referring to can do is make things appear out of order (and that's a bug in editors for not rendering them as special characters, not a bug in Unicode). There are invisible codepoints (such as ZWSP) but they also have are also necessary and again, a failure to render them as special characters is an editor bug. And they don't make anything else invisible. (* There have also been other editor/renderer bugs such which might result in crashes or disappearing text, but those are from failures to be compatible with Unicode, not from Unicode) You need to go read the paper I linked (which is linked from your blog post), not a 3 paragraph blog post. If you think that these are errors in Unicode, then I have some errors in ASCII and a text editor that treats NUL as end-of-file to sell you. Control characters have always been necessary and will always be necessary. > eurt ton I'm not even going to address that other than to say LOL

WalterBright 5y ago
> It does not overwrite anything nor does it make anything invisible Sure it does. It causes the renderer to reverse direction, which overwrites the previous characters. It's EXACTLY this effect which allows for invisible malware insertion into code. Errors in ASCII are not justification for going bananas adding them everywhere. >> eurt ton > I'm not even going to address that other than to say LOL You could try. Somehow I managed to trick HN into rendering text right-to-left by never stepping outside of ASCII. Unicode further botched things up by introducing modes. And how many official Unicode letter 'a' glyphs are there? Somehow Unicode decided it needed to confuse fonts with characters. They're not even always different fonts, they sometimes are indistinguishable. I wouldn't be in the least surprised if Unicode added a clockwise spiral rendering mode. clock iralw i !si ps es Dare I ask - is there one already?
- jfrunyon 5y ago
  > Sure it does. It causes the renderer to reverse direction Correct. > , which overwrites the previous characters. Wildly incorrect. Again, you don't even being to understand what's going up, so please go educate yourself.

WalterBright 5y ago

> It does not overwrite anything nor does it make anything invisible Sure it does. It causes the renderer to reverse direction, which overwrites the previous characters. It's EXACTLY this effect which allows for invisible malware insertion into code. Errors in ASCII are not justification for going bananas adding them everywhere. >> eurt ton > I'm not even going to address that other than to say LOL You could try. Somehow I managed to trick HN into rendering text right-to-left by never stepping outside of ASCII. Unicode further botched things up by introducing modes. And how many official Unicode letter 'a' glyphs are there? Somehow Unicode decided it needed to confuse fonts with characters. They're not even always different fonts, they sometimes are indistinguishable. I wouldn't be in the least surprised if Unicode added a clockwise spiral rendering mode. clock iralw i !si ps es Dare I ask - is there one already?

jfrunyon 5y ago
> Sure it does. It causes the renderer to reverse direction Correct. > , which overwrites the previous characters. Wildly incorrect. Again, you don't even being to understand what's going up, so please go educate yourself.