On Thu, Aug 2, 2018, 8:33 AM Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
wrote:
versions:Noto Mono is deprecated and was removed from Noto completely in latest
sane way,https://github.com/googlei18n/noto-fonts/issues/1000
They do not ship a truly monospace font anymore. Half-fixed is the only
with this?so apps should just support it. How many apps have an actual problem
font rendering.
Potentially every app which doesn't implement the single/double width
With this change, an application can't trust be_fixed_font to be a realfixed font anymore.
And no, "apps should just support it" doesn't work, because there ismuch work to do that, and
sometimes there is no need to do that.different flags.
There is a reason why B_FIXED_FONT and B_FULL_AND_HALF_FIXED are
Then we don't have a fixed font to ship at all. We currently use Noto Mono
but it is deprecated.
It is not 1990 anymore and we support localization. Yes, this means
monospace is more complex
than it used to be. But this is like saying "some applications don't
support UTF-8" and sticking
to ASCII.
If an application wants to optimize handling of fixed size characters, it
can still check the
B_FIXED_FONT flag and act accordingly. It can even check the characters it
needs, to make sure
none of them is double width. And if this isn't the case, it should fall
back to a more complex
and possibly slower drawing code. It should not chicken out and refuse to
render anything for
our Japanese users.
What should we do then? I don't think adding a "half fixed font" setting
in Appearance makes
sense. I don't think providing a font with only latin chars just for the
sake of having a
really monospace font makes sense either (an app which draws only latin
char can use a
full and half fixed font and never notice the difference anyways).
