links - test: https://arkenfox.github.io/TZP/tests/fontscripts.html - https://learn.microsoft.com/en-us/typography/fonts/windows_11_font_list - no mention of "Sans Serif Collection" - https://learn.microsoft.com/en-us/globalization/input/font-support - scroll down a little to `Windows 11` header, which then is ambiguous when it lists the table, saying "The following table lists scripts newly supported in Windows 10" - fyi: I have every windows system font, including all supplmental fonts and optional downloads STR (nightly 120), windows 11 - do not use ETP strict - start in normal mode - load test, check `all` and `max`, give it 2 seconds for any async char fallback, click run - open a PB mode window - redo the test results - normal mode, so no font protection, I get a tofu count of `[1437] 8.89%` - pb mode, so font vis = 2, I get a tofu count of `[3127] 19.35%` AFAICT, pretty much all the additional tofu can be avoided by adding "Sans Serif Collection" to out system fonts. [1] I am not 100% sure if this is available in Windows 10 (by default or supplemental or via updates over time etc), but we already have entropy in kLangPackFonts based on supplemental fonts (and various windows language install defaults) I think the benefit of an additional 25 scripts supported outweighs any potential entropy [1] Some scripts/blocks may not necessarily be widely used (e.g. I am not a script expert and although I tried to weed out archaic, this test also serves for some fingerprinting tests). Script support that gets added with this are (and seems to line up with the MS table) - African - mende kikakui - Brahmic - balinese - buhid - cham - dogra - hanifi rohingya - hanunoo - kaithi - kayah li - khojki - khudawadi - lepcha - limbu - mahajani - modi - mro - multani - pau cin hau - saurashtra - sundanese - sundanese supplement - takri - tirhuta - Semetic - mandaic - samaritan
Bug 1858357 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
links - test: https://arkenfox.github.io/TZP/tests/fontscripts.html - https://learn.microsoft.com/en-us/typography/fonts/windows_11_font_list - no mention of "Sans Serif Collection" - https://learn.microsoft.com/en-us/globalization/input/font-support - scroll down a little to `Windows 11` header, which then is ambiguous when it lists the table, saying "The following table lists scripts newly supported in Windows 10" - fyi: I have every windows system font, including all supplmental fonts and optional downloads STR (nightly 120), windows 11 - do not use ETP strict - start in normal mode - load test, check `all` and `max`, give it 2 seconds for any async char fallback, click run - open a PB mode window - redo the test results - normal mode, so no font protection, I get a tofu count of `[1437] 8.89%` - pb mode, so font vis = 2, I get a tofu count of `[3127] 19.35%` AFAICT, pretty much all the additional tofu can be avoided by adding "Sans Serif Collection" to out system fonts. [1] I am not 100% sure if this is available in Windows 10 (by default or supplemental or via updates over time etc), but we already have entropy in kLangPackFonts based on supplemental fonts (and various windows language install defaults) I think the benefit of an additional ~~25~~ 26 scripts supported outweighs any potential entropy [1] Some scripts/blocks may not necessarily be widely used (e.g. I am not a script expert and although I tried to weed out archaic, this test also serves for some fingerprinting tests). Script support that gets added with this are (and seems to line up with the MS table) - African - mende kikakui - Brahmic - balinese - buhid - cham - dogra - hanifi rohingya - hanunoo - kaithi - kayah li - khojki - khudawadi - lepcha - limbu - mahajani - modi - mro - multani - pau cin hau - saurashtra - sundanese - sundanese supplement - takri - tirhuta - warang citi // edited, missed one - Semetic - mandaic - samaritan