Missing Unicode 13 "Symbols for Legacy Computing" characters #474

Closed
opened 6 months ago by dnkl · 5 comments
dnkl commented 6 months ago
Owner

The Symbols for Legacy Computing block covers the range U+1FB00 - U+1FBF9.

Foot currently render:

  • U+1FB00 - U+1FB3B ("sextants")
  • U+1FB70 - U+1FB8B ("eighths blocks")

For the rest, we fall back to font glyphs.

While I don't think we need/should implement all of these (or should we?), a few more is probably a good idea. But which ones?

  • The shades?
  • The various combinations of diagonal lines?
  • Triangles?
  • The weirdly shaped blocks in U+1FB3C - U+1FB6F?
The [_Symbols for Legacy Computing_](https://en.wikipedia.org/wiki/List_of_Unicode_characters#Symbols_for_Legacy_Computing) block covers the range U+1FB00 - U+1FBF9. Foot currently render: * **U+1FB00 - U+1FB3B** ("sextants") * **U+1FB70 - U+1FB8B** ("eighths blocks") For the rest, we fall back to font glyphs. While I don't think we need/should implement **all** of these (or should we?), a few more is probably a good idea. But which ones? * The shades? * The various combinations of diagonal lines? * Triangles? * The weirdly shaped blocks in U+1FB3C - U+1FB6F?
dnkl added the
enhancement
label 6 months ago
Poster
Owner

Perhaps @dankamongmen has some input to help us prioritize?

Perhaps @dankamongmen has some input to help us prioritize?
Collaborator

It looks like chafa added support for the "legacy computing" symbols just yesterday.

It looks like `chafa` [added](https://github.com/hpjansson/chafa/commit/a8c78d2f286dc61893bfd5604eccf32320bc6c81) support for the "legacy computing" symbols just yesterday.
Poster
Owner

While not strictly necessary, we should take a look at applying antialiasing, given the number of diagonal lines in the remaining glyphs...

See #279.

This would also need support from fcft; we currently don't have enough information to reliably decide whether a font is antialiased (and if so, with which subpixel mode?). This fcft PR adds the necessary information: dnkl/fcft#24

While not strictly necessary, we should take a look at applying antialiasing, given the number of diagonal lines in the remaining glyphs... See https://codeberg.org/dnkl/foot/issues/279. This would also need support from fcft; we currently don't have enough information to reliably decide whether a font is antialiased (and if so, with which subpixel mode?). This fcft PR adds the necessary information: https://codeberg.org/dnkl/fcft/pulls/24

Notcurses doesn't use any of these other than the sextants and eighths, though there is talk of using the wedges, primarily in a plotting context.

Notcurses doesn't use any of these other than the sextants and eighths, though there is [talk](https://github.com/dankamongmen/notcurses/issues/1199) of using the wedges, primarily in a plotting context.
Poster
Owner

Note to self: pixman_composite_triangles() on a PIXMAN_a8 buffer does grayscale antialiasing for us.

Note to self: `pixman_composite_triangles()` on a `PIXMAN_a8` buffer does grayscale antialiasing for us.
dnkl added a new dependency 6 months ago
dnkl closed this issue 3 months ago
dnkl referenced this issue from a commit 3 months ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Depends on
#25 2.4.0
dnkl/fcft
Loading…
There is no content yet.