#13810 closed bug (fixed)
NotoSansMono not recognized by Appearances
| Reported by: | humdinger | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Servers/app_server | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | #10573 | Blocking: | |
| Platform: | All |
Description
This is hrev51598.
I've build the new Noto font HPKG (noto-20171026.recipe) which has the old "NotoMono" font removed, which was replace by "NotoSansMono".
The Appearances prefs don't find the new NotoSansMono font, however.
After replacing all "Noto Mono" with "Noto Sans Mono" in the code (see attached patch), clicking "Defaults" picks up the first font it finds (which isn't even a fixed-width).
Attachments (1)
Change History (9)
by , 7 years ago
| Attachment: | 0001-Switch-default-fixed-font-from-NotoMono-to-NotoSansM.patch added |
|---|
comment:1 by , 7 years ago
| patch: | 0 → 1 |
|---|
comment:2 by , 7 years ago
PulkoMandy's explanation from IRC:
it not showing in appearance is because we still don't implement BFont::IsFullAndHalfFixed
NotoMono was really monospace (no japanese support), Noto Sans Mono is "full and half", that is, japanese characters are 2x as wide as normal ones
comment:4 by , 7 years ago
| patch: | 1 → 0 |
|---|
comment:6 by , 6 years ago
| patch: | → 0 |
|---|
The patch was applied in hrev52159 then reverted in 9a90ee3a38f7cf8ab7f06bf0062424d093560a29. This means this bug is invalid, see discussion on https://www.freelists.org/post/haiku-commits/haiku-hrev52159-srcserversappfont-docsinterface-guidelines-srckitsnetworklibnetapi-srcserversapp,2
comment:7 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It is now recognized, though not set as default.
comment:8 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Switch to NotoSansMono