OMG this is one of my favorite tools paid for it all the way back when it went out. Have used it so many times just to write documentation for things like:
I believe here ASCII was used not as in ASCII-the-standard but as “ASCII” in ASCII-art. I also believe that ASCII art should actually be called “monospaced Unicode text” since people doing ASCII art have been using as many codepoints as were available in their platform of choice.
Yeah, "BOX DRAWINGS LIGHT UP AND LEFT" and "BOX DRAWINGS LIGHT DOWN AND LEFT". (If this were ASCII, it would have used | ("VERTICAL LINE") instead of "BOX DRAWINGS LIGHT VERTICAL".)
ASCII means more than just characters from the ASCII character standard today, for better or worse. The "modern" translation would be something like "text".
I don't agree or disagree with it, so don't argue with me, just trying to explain how people use it today.
Context is important, ya know? If we're talking about text encodings, that's one thing, but we're talking about drawing. "ASCII text" drawing was never entirely limited to ASCII even in the days of single-byte encodings. There were code pages which used the high bit for more useful drawing glyphs, people took advantage of that when they could.
The concept of an extended ASCII encoding goes way back: https://en.wikipedia.org/wiki/Extended_ASCII, and UTF-8 is just another extended ASCII encoding, albeit a very clever one, with a lot of codepoints.
Are you saying we should reserve the term "ASCII art" literally for text containing just the original 95 printable characters? Even if you can make a good argument for that, I fear you're fighting a losing battle.
Neither a superset or subset of a thing is the thing. Only the thing is the thing.
But when you combine units of language the result is not just the sum of the parts. word1 means X and word2 means Y but established phrase "word1 word2" rarely means X + Y. The result relates to X and Y but it has a life of its own that depends on how it's used.
Think of these and how they are more than sum of their parts. Demo scene. Serverless. Skyscraper. Information security. Artificial intelligence. Drawing board.
> However, ASCII is not a random ancient word, it’s a ratified standard
Even so, ask around and you'll find debates about which ASCII standard is the "right" and "true" one. Some argue only the initial standard is correct for ASCII art, you need to follow that, others say any of the versions are alright.
Hmm, the "With Expression" diagram on line 656 looks fine in emacs, but in chrome at that actual link, everything on the right is mangled. (The characters look fine, it looks like github's font choices do poorly with the "load bearing whitespace" for the extended bits...)
I think it's the ◀ character. It looks like Chrome (I'm on Windows) makes it wider than other Characters. I think ▶ has this same problem. But from a quick scan, I don't see any other place in the file where one of those characters is used in a way that it being extra wide would be noticable.
For web it'll really vary by font family availability and fallback. Personally I like the nerd don't variant for Inconsolata, Cascadia Coffee and Firs Code for fixed width usage.
I wish self packaging similar to how Google Fonts does it was easier to do. IE breaking up the don't into glyph segments to reduce unused characters for languages not used.
I've always wanted to try this but never had a reason: do emojis work on HN? I've never seen one and didn't know if it was just a culture thing or if it was enforced:
https://github.com/ivank/potygen/blob/main/packages/potygen/...
ASCII is just so versatile and allows you to put nice graphics in places where one does not expect, making things more easily understandable.