zlacker

<pre> works pretty reliably

>>Groxx+(OP)
For whitespace and for the simplest ASCII sure, but for anything a bit more complex you might have problems with

1. HTML reserved characters like < > and \.

2. overflowing content

3. displaying ASCII made with special encodings and characters sets, like code page 437

4. displaying nonprintable (control) characters

5. displaying colors

6. text preprocessors messing up the formatting

>>califo+S3
the Virtual terminal[1] from Asciinema[2] is what I use but that is a lot more difficult than just including a video of it. I got CMS from a very expensive CMS to support Asciinema but it was actually too much effort to be worth it I had to recompile some components make a editor interface etc etc.

[1]https://github.com/asciinema/avt

[2]https://docs.asciinema.org/how-it-works/

>>Groxx+(OP)
Pre differs browser to browser

>>pastag+s8
check out my website:

https://terminoid.com/discover/

i still need to add seeking and stuff, but it works. like asciinema but based on xterm.js

>>califo+S3
Most of those are solved with wrapping it in both <code> and <pre>, and #5 I don't think is even part of "ASCII art" anymore as it wouldn't be just ASCII anymore, but rich-text.

>>tetris+zf
Sure, they might not be pixel-perfect, but if you're doing ASCII art you aren't really aiming for pixel-perfectness anyways, then you'd chose a different medium. It's inherently a medium for the clients to render how they see fit.

>>diggan+Aw
What do you mean? Add far as I know <code><pre> doesn't help with any of those?

Color is very much a part of ASCII art, if we consider ASCII to mean a broader range of different technologies. Just check the stuff in the article, or the stuff on https://16colo.rs/ site.

>>califo+S3
Aaah. None of these fancier ones were loading for me earlier for some reason, all I got was the clearly-mono-spaced one in the header.

Yeah, for non-ASCII / more sophisticated stuff, images are kinda the only widely-compatible option without adopting a full terminal emulator worth of javascript.

>>califo+S3
None of these points seem to be relevant when it comes to the question about ASCII art as text in html vs image. Most of them feel to be no actual problems at all, but only someone vaguely mentioned some keywords in order to 'find' problems?