Opened 3 years ago

Closed 20 months ago

Last modified 4 months ago

#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


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 3 years ago.
Switch to NotoSansMono

Download all attachments as: .zip

Change History (9)

by humdinger, 3 years ago

Switch to NotoSansMono

comment:1 by humdinger, 3 years ago

patch: 01

comment:2 by humdinger, 3 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:3 by waddlesplash, 3 years ago

Blocked By: 10573 added

adding ticket of that to Blocked

comment:4 by pulkomandy, 3 years ago

patch: 10

comment:5 by pulkomandy, 3 years ago

patch: 0

Patch migrated to Gerrit:

comment:6 by korli, 2 years ago

patch: 0

The patch was applied in hrev52159 then reverted in 9a90ee3a38f7cf8ab7f06bf0062424d093560a29. This means this bug is invalid, see discussion on,2

comment:7 by waddlesplash, 20 months ago

Resolution: fixed
Status: newclosed

It is now recognized, though not set as default.

comment:8 by nielx, 4 months ago

Milestone: UnscheduledR1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.