Opened 17 months ago

Closed 4 months ago

#13810 closed bug (fixed)

NotoSansMono not recognized by Appearances

Reported by: humdinger Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: #10573 Blocking:
Has a Patch: no 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)

0001-Switch-default-fixed-font-from-NotoMono-to-NotoSansM.patch (2.7 KB) - added by humdinger 17 months ago.
Switch to NotoSansMono

Download all attachments as: .zip

Change History (8)

Changed 17 months ago by humdinger

Switch to NotoSansMono

comment:1 Changed 17 months ago by humdinger

Has a Patch: set

comment:2 Changed 17 months ago by humdinger

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:3 Changed 17 months ago by waddlesplash

Blocked By: 10573 added

adding ticket of that to Blocked

comment:4 Changed 15 months ago by pulkomandy

Has a Patch: unset

comment:5 Changed 15 months ago by pulkomandy

Has a Patch: unset

Patch migrated to Gerrit: https://review.haiku-os.org/48

comment:6 Changed 9 months ago by korli

Has a Patch: unset

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 Changed 4 months ago by waddlesplash

Resolution: fixed
Status: newclosed

It is now recognized, though not set as default.

Note: See TracTickets for help on using tickets.