You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will require some refactoring to the way mosaics are handled as the new code points do not define separate glyphs for solid and separated mosaics.
Experimental support is now available by running teletext -u <subcommand> (it must be before the subcommand). Separated glyphs are not yet supported. This will also affect HTML output and a font suitable for use with browsers is not yet available.
Using unicode to render teletext in terminals is currently not possible due to the lack of support for separated/solid mosaics. On hold until something happens on that front.
An update to the unicode spec has been proposed to add seperated and solid mosaics at different codepoints. It will be a few years until it is widely available.
ali1234
changed the title
Support new Unicode 13.0 Teletext code points
Support new Unicode 16.0 Teletext code points
May 8, 2024
This will require some refactoring to the way mosaics are handled as the new code points do not define separate glyphs for solid and separated mosaics.
Related links:
https://www.unicode.org/L2/L2019/19025-terminals-prop.pdf
https://gitlab.gnome.org/GNOME/vte/issues/189
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944609
The text was updated successfully, but these errors were encountered: