“Subfont”.tff fallback doesn't work in (infrequently) description and (mostly in) comments

[idontveapc]

App uses two fonts for regular typeface. I believe “Subfont”.ttf is used for fallback for missing characters in regular font.(or other) To test if you can get missing character/s you could check the fallback.

In my test, i used a font file with zero characters which when you use instead the regular font; (latin) characters fallback to system not subfont.

[prateekmedia]

We use NotoSans as primary font, can you clarify your statement more by a screenshot?

[idontveapc]

Yup, in the new version (beta) subfont isnt used. So, illustrations below are from the previous version (nightly).

Now i just want to prove it by the “,” ("comma"). The SysSans fallback (font) has comma that looks different in Subfont. The comma fallback is mostly present in search bar and (channel) home:

But not in comments and descriptions (mostly but not always) –here commma in search bar is different than in video title. In the second image description;

also has comma from SysSans:

The SysSans fallback isn't too bad, but it's enough bad. Because it covers mostly CJK characters; charactors like: ’(single quote), ”(double quote) are badly spaced. As they are as “fullwidth” in the font.

Though all the latin characters don't fallback to Subfont at all.