#unscii — Public Fediverse posts

It doesn't look quite right on a 16:9 HDMI display with a 16 by 16 font. It lacks the pixellation and CRT blurring. And the cursor is wrong. So @ColinHaynes still has the better. (-:

But it's not bad for a non-X11 framebuffer Unicode-capable terminal emulator on a #RaspberryPi running #NetBSD with the #CommodorePET and BBC character sets.

#nosh #uservt #unscii

@ColinHaynes

From the looks of that, Unscii already has both of the glyph sets, and Markus Neeb's changes aren't adding any new glyphs (just putting some PET ones into the C64 set) so don't make a difference.

I'm already getting the text mode guttering by dint of the 7by7 font being rendered into 8by8 bitmaps. (-:

#PETSCII #CommodorePET #Unscii #nosh #uservt

I noticed yesterday from a Hacker News post that I hadn't checked in changes that I made to my fork of @viznut's #Unscii back in 2023. So I spent some hours sorting through them and checking them in.

All so that you can enjoy 16by16 script-upscaled and hand-rounded versions of the 8by8 BBC Micro and Commodore PET bitmap fonts. (-:

https://github.com/jdebp/unscii/blob/2.1.1f/src/font-bbcg16.txt

https://github.com/jdebp/unscii/blob/2.1.1f/src/font-pet16.txt

#uservt #BBCMicro #CommodorePET

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.

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.

I'm sick of the terminal login on my computer using "glass TTY" semantics from 1968, when cursor addressability for character mode terminals has been around since the 1970s and pseudo-graphics have been around since the 1980s (and have been in Unicode since 2020).

Yes, I intentionally ran the without-#PAM flavour. Yes, terminal emulators capable of UTF-8 have been around for decades. This is Microsoft Terminal with the #unscii font, as it happens.

#nosh #login #MouseText

@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