#unifont — Public Fediverse posts

Interestingly, #Unifont 15 has an "_all" version with the same problem as #unscii "-full", and the additional problem that it has placeholder glyphs and is thus not suitable in any position other than final.

However, it does have a not "_all" alternative that breaks up its hex files by plane and doesn't have placeholders; and so doesn't hit #FreeBSD's vt font file limit if one does a 1-to-1 conversion.

Interestingly, #Unifont 15 has an "_all" version with the same problem as #unscii "-full", and the additional problem that it has placeholder glyphs and is thus not suitable in any position other than final.

However, it does have a not "_all" alternative that breaks up its hex files by plane and doesn't have placeholders; and so doesn't hit #FreeBSD's vt font file limit if one does a 1-to-1 conversion.

Interestingly, #Unifont 15 has an "_all" version with the same problem as #unscii "-full", and the additional problem that it has placeholder glyphs and is thus not suitable in any position other than final.

However, it does have a not "_all" alternative that breaks up its hex files by plane and doesn't have placeholders; and so doesn't hit #FreeBSD's vt font file limit if one does a 1-to-1 conversion.

Interestingly, #Unifont 15 has an "_all" version with the same problem as #unscii "-full", and the additional problem that it has placeholder glyphs and is thus not suitable in any position other than final.

However, it does have a not "_all" alternative that breaks up its hex files by plane and doesn't have placeholders; and so doesn't hit #FreeBSD's vt font file limit if one does a 1-to-1 conversion.

I was seeing bizarre effects in my framebuffer virtual terminals with some Unicode 13 tests, such as glyphs coming out as half-emoticon and half-hangeul.

It turns out that with the "-full" version of @viznut's #unscii I was hitting the 65535-glyph limit of #FreeBSD's vt font file format.

The not "-full" version of unscii has far fewer glyphs, and also means that I can use a more up-to-date #Unifont than what comes in unscii.

So I switched to that, and the half-and-half glyphs have gone away.

I was seeing bizarre effects in my framebuffer virtual terminals with some Unicode 13 tests, such as glyphs coming out as half-emoticon and half-hangeul.

It turns out that with the "-full" version of @viznut's #unscii I was hitting the 65535-glyph limit of #FreeBSD's vt font file format.

The not "-full" version of unscii has far fewer glyphs, and also means that I can use a more up-to-date #Unifont than what comes in unscii.

So I switched to that, and the half-and-half glyphs have gone away.

I was seeing bizarre effects in my framebuffer virtual terminals with some Unicode 13 tests, such as glyphs coming out as half-emoticon and half-hangeul.

It turns out that with the "-full" version of @viznut's #unscii I was hitting the 65535-glyph limit of #FreeBSD's vt font file format.

The not "-full" version of unscii has far fewer glyphs, and also means that I can use a more up-to-date #Unifont than what comes in unscii.

So I switched to that, and the half-and-half glyphs have gone away.

I was seeing bizarre effects in my framebuffer virtual terminals with some Unicode 13 tests, such as glyphs coming out as half-emoticon and half-hangeul.

It turns out that with the "-full" version of @viznut's #unscii I was hitting the 65535-glyph limit of #FreeBSD's vt font file format.

The not "-full" version of unscii has far fewer glyphs, and also means that I can use a more up-to-date #Unifont than what comes in unscii.

So I switched to that, and the half-and-half glyphs have gone away.