Quoting astian (2020-11-12 16:58:00)
> Jonas Smedegaard:
> > Quoting astian (2020-11-11 21:31:00)
> >> With version 20200323-1, when attempting to render code points such
> >> as 0x3001 and 0x3002, fontconfig would choose "Noto Sans CJK JP"
> >> [0] as fallback for "Monospace". This was
astian:
> - Bug in fonts-noto-core: Either the glyphs don't belong or there is
> some incorrect metadata or configuration, or bad interaction with
> other fonts, or any combination thereof, which causes FC to
> correctly (in technical terms) change the fallback selection in
>
Jonas Smedegaard:
> Hi astian,
>
> Thanks for a detailed bugreport!
>
> Quoting astian (2020-11-11 21:31:00)
>> With version 20200323-1, when attempting to render code points such as
>> 0x3001 and 0x3002, fontconfig would choose "Noto Sans CJK JP" [0] as
>> fallback for "Monospace". This was
Hi astian,
Thanks for a detailed bugreport!
Quoting astian (2020-11-11 21:31:00)
> With version 20200323-1, when attempting to render code points such as
> 0x3001 and 0x3002, fontconfig would choose "Noto Sans CJK JP" [0] as
> fallback for "Monospace". This was expected behaviour, I want to
Package: fonts-noto-core
Version: 20201109-1
Severity: normal
Dear Maintainer,
With version 20200323-1, when attempting to render code points such as
0x3001 and 0x3002, fontconfig would choose "Noto Sans CJK JP" [0] as
fallback for "Monospace". This was expected behaviour, I want to see
5 matches
Mail list logo
