Opened 6 months ago
Last modified 6 months ago
#18914 new enhancement
CharacterMap: Show origin of fallback character
| Reported by: | humdinger | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Applications/CharacterMap | Version: | R1/beta4 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
If I'm not mistaken, Haiku transparently falls back on another font, if a character isn't part of the currently set font. It'd be nice to know which font provides the symbol.
In that case, maybe an "(origin: {NameOfFont})" could be added at the bottom, where it shows the selection's UTF-code etc.
Change History (2)
comment:1 by , 6 months ago
comment:2 by , 6 months ago
Ah, I see. Or don't, as it's completely transparent to a fault. Not trivial then... :)
I was wondering which font I'd have to depend-package with an app that uses a special character that is apparently not in our Noto font.
Note:
See TracTickets
for help on using tickets.
That transparency means the application is none the wiser. As things are now, it can't even ask if the character would be drawn without resorting to fallbacks. This will also need changes in app_server.