[Pkg-fonts-devel] Bug#1009198: fonts-droid-fallback: English text broken when running programs via wine that use both Japanese and Latin characters

[Konomi]

> To me this sounds like an issue in Wine, not in this font.

It might be that, I'm really not sure and I was hoping for someone who
is extremely knowledgeable with fonts or wine or both to chime in.

There is one thing I found during my testing, if you open
DroidSansFallbackFull.ttf with FontForge [FontForge.png] and do the
following: Element -> Font Info -> Unicode Ranges you'll see that the font
declares at least according to Font Forge that it does support Basic Latin
U+0020-U+007E/95. Double clicking these entries will jump to the relevant
characters and when I double click Basic Latin it obviously jumps to an
empty set of characters.

I noticed when I checked other ranges too such as Thai U+0E00-U+0E7F1/87
that
they too are missing their characters.

Considering Font Forge states: "This pane is information only and shows the
characters actually in the font..." is it possible that when Google removed
the extra characters in the commit I cited in my original report that they
failed to update what ranges the font supports or something along those
lines?

Again, I am no expert in fonts or FontForge but I hope this might be a
useful clue for someone that is.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-fonts-devel/attachments/20220409/808daadd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FontForge.png
Type: image/png
Size: 207764 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-fonts-devel/attachments/20220409/808daadd/attachment-0001.png>