1795460 - font visibility = 1: auto include preferred language from kLangPackFonts

Status: UNCONFIRMED

(Core :: Layout: Text and Fonts, enhancement)

Description

[Thorin [:thorin]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

Similar to Bug 1670199, but this is to improve usability

kBaseFonts is rather discriminatory to users of kLangPackFonts, so for example a user requesting pages in Korean is going to get broken unicode (IIUIC)

I propose that if navigator.language (and the first language in accept headers) meets a certain list, we include the relevant kLangPackFonts

So for example, if the first language requested is ko-* or ko, on windows, we also allow GulimChe (monospace) and Batang (serif). Note: Malgun Gothic is already part of kBaseFonts

This shouldn't affect entropy, as the user would be expected to have those fonts (why else would they be requesting korean web content?) and they are already requesting Korean

I do not know how feasible this would be, and while I wouldn't expect users to change preferred language mid-session, it would reflect globally in already open tabs/windows, not per eTLD+1 + scheme

Comment 1

[Thorin [:thorin]]

tom, didn't you open a similar issue for FPP - if so , close this.

Comment 2

[Tom Ritter [:tjr]]

I don't think there's a different bug... FPP includes language packs entirely so this specific idea wouldn't be it. We had theorized that maybe we could restrict the language pack list in this way but I don't think I put it in a bug so much as a speculative idea if we find that it would be the best thing to do to reduce entropy in practice. (Using the forthcoming measurement data vs just guessing.)

Comment 3

[Thorin [:thorin]]

We had theorized that maybe we could restrict the language pack list in this way

that's what I meant .. that FPP would be tightened but not (hopefully) break "localized" content