3 ms·
Maybe one should encourage OP to turn this into an actual "Show HN" by uploading screenshots and the browser's devtools open on the computed style tab, scrollin
by DemocracyFTW2 3y ago
Maybe one should encourage OP to turn this into an actual "Show HN" by uploading screenshots and the browser's devtools open on the computed style tab, scrolling all the way down where they display the actual font(s) used to render the element in question. In my case that turns out to be TakaoPGothic, which is not found in the respective style rule (apparently chosen by the OS then).
The sad state of affairs is that at a point where it matters most—displaying intricate, somewhat region-sensitive CJK glyphs—the technology to do so necessitates downloading comparably big files. IOW if my content is in English and I want a fancy font, small file and if it fails, well, you still can correctly read [a-zA-Z]. But if I do the same in Chinese or Japanese, tough luck, except I put in a lot of work to build an optimized font for the content du jour, else it will be easily 10MB for one font alone.
- johncoltrane 3y agoMacOS and Android both handle this flawlessly out of the box, though. They don't require any additional download and the website in question doesn't even use webfonts anyway. PEBKAC, as always.
- DemocracyFTW2 3y agoWhere Android doesn't or at least didn't when I last checked (years ago) is CJK beyond U+xffff (CJK ext B and beyond). You can't just install fonts on Android as a user so web pages that need to display some of those characters (a minority of which is not extremely rare) do need to include a webfont. The same goes for cuneiform and hieroglyphs. Not mainstream concerns but still.