There's a bizarre font bug in both #unscii and #funscii that I have fixed locally and have to push out. Half of the uppercase letters in one of the 8-bit fonts are off by one code point.

I spotted this when my Z shell prompt changed to "JdeBQ".

It does mean that that font is missing a letter. I tried to look for an authoritative original source to fill it in from, but couldn't find one.

@viznut

This gave me an idea. Although the 8×8 fonts cannot be synthetically obliqued and boldfaced, because they are square, rectangular Ubuntu Mono can be.

So I can use #unscii PET for upright medium, unscii #BBCMicro for upright boldface, and #UbuntuMono for the oblique medium and boldface.

It works out fairly well.

#nosh #VirtualTerminals #vtfont

The 8×8 #BBCMicro font from #unscii works rather better than Ubuntu Mono does, when rendering virtual terminals to the framebuffer with console-fb-realizer, I think. And the PET font from unscii works better still.

#nosh #vtfont #VirtualTerminals

slashpackage repository done.

So the next job is probably forking unscii so that I can get a BBC Micro overlay font in vt font format.

#FreeBSD #unscii #BBCMicro

Here is the Japanese language manual page for yash(1), the #Watanabe shell, displayed on #FreeBSD with three different framebuffer terminal emulators: jfbterm, zhcon, and console-fb-realizer (realizing a user-space virtual terminal onto the framebuffer) from the #nosh toolset.

The manual system itself is outputting a UTF-8 page, which zhcon clearly doesn't do by default. jfbterm looks like it just lacks CJKV fonts.

console-fb-realizer is using Viznut's #unscii font and Ubuntu Mono.

@viznut

I've had this test chart hanging around for some while, and I don't remember whether it was a modification to yours that I knocked together. Did you do a Mouse Text test? I suspect that it was me. (-:

#Unscii #MouseText

@asie

Stricly speaking, #Unscii isn't providing true italics here. It is, rather, being faked with an oblique slant, which isn't the same.

Notice how the transform used gives different heights to the letters 'n' and 'm', making the italicized word "filename" look uneven.

Oblique is an inferior substitute for a properly italicized font, where the italic letters actually have different shapes to the upright ones, and aren't simply toppled-over versions of them.

#MicrosoftTerminal

Switching Microsoft Terminal to #Unscii produces better results.

#MicrosoftTerminal allows me to pick Unscii 16, whereas MobaXTerm forced the use of Unscii 8 and didn't allow Unscii 16 as an option at all.

Microsoft Terminal also handles more text styles, including italics, invisible, and overline.

It even clearly distinguishes font weights in reverse video mode.

I changed the font in #MobaXterm from MobaTerm to #Unscii on a whim, today.

On the positive side, the distinction amongst boldface, normal, and faint is somewhat clearer with Unscii. Although neither is very good with faint and reverse video, which makes light mode problematic.

On the negative side, Unscii isn't using the whole of the available space, which stops block graphics from working. Something somewhere, from the placement of the strikethroughs, doesn't like Unscii's aspect ratio.