0xA000 Font Family – A tile mastered font-family
pippin.gimp.org
pippin.gimp.org
Although it's possible that `contenteditable="false"` would trip them up even more, so good point.
https://html.spec.whatwg.org/multipage/interaction.html#attr... has the details. It comes down to the ability to specify contenteditable="false" within a contenteditable area, with the absence of a contenteditable attribute corresponding to the inherit state.
I had quite forgotten that it was possible to nest something non-editable within something editable. Fairly similar to user-select behaviour, really.
>If you really want to confuse those unfamiliar with boolean attributes, `contenteditable="false"` is editable
document.querySelector('.content > div').setAttribute('contenteditable',false)
and editing no longer works.I think it's even more interesting, as it will improve the textual rendition of graphics for people who can't use sixels.
See also Chafa https://hpjansson.org/blag/2021/09/16/chafa-1-8-terminal-gra... for more details, and sixel-tmux https://github.com/csdvrx/sixel-tmux to transform sixels into unicode if your terminal doesn't support sixels.
I'm waiting for 1FB00 support in Iosevka: https://en.m.fontke.com/font/131973120/charset/2201/
What does that mean? Aren't all fonts using grey pixels for AA while pixels are, well, squares (or close enough)? I know about "sub-pixel AA" done using colors but I don't think they're referring to this.
Or do they mean that the font has no AA at all and is just one using regular pixels, all of the same colors? (FWIW I'm using a version of the Terminus font that does just that: "pixel perfect" rendering at several sizes, no AA)
I think the default landing page is showing the original vector font from which the pixelated one are made
I quite like the final result. It's sorta like a bitmap font but with a more organic feel to it. I wouldn't want to code in it, but I'd add it to a image for instance