dazel VS derasterize

My goal was to build a Bazel workspace that's not dependent on the system's OS, so I developed a docker container that should take care of it (There's a cool open source project, dazel, but I couldn't get it to work).

Far far better than caca.

The subset of usable characters (glyphs) roughly defines how accurate the picture can be represented: if all you have is - and _ and you want to represent an horizontal pipe, it'll be ugly.

Of course it's more complicated than that, but caca uses ascii, while chafa uses a larger unicode range.

The example is illustrated in picture on https://github.com/csdvrx/derasterize where the left is the original basicidea.c using only unicode halfblocks, and the right has more candidate of different shapes.

Derasterize lets you select the width of the range you want to use, to improve encoding time say for video - but ideally, you would be able to test that whatever font you are using contains the glyphs you want.

She's not only done work with sixels but she's the maintainer of the highest quality tool for rendering images as unicode blocks. https://github.com/csdvrx/derasterize

On the application side, there is as yet exactly one terminal multiplexer that can handle images inside multiple terminals, but someone (saitoha?) did make a dev branch of tmux that could do it. /u/csddvx has I think the most recent version of that ; and her derasterize can make sixel work with non-sixel terminals which is a really neat trick.

For better quality, check https://github.com/csdvrx/derasterize

Example in Windows Terminal: