Posts

Post not yet marked as solved
0 Replies
470 Views
I take these websites to test COLR/CPAL(v0) format color font: https://yoksel.github.io/color-fonts-demo/ https://pixelambacht.nl/chromacheck/ In my iOS 17 device, both websites show unsupported of COLR/CPAL (v0) color font, however, on my other iOS 16 devices, it is supported. COLR/CPAL (v0) color font format is widely supported on mainstream browsers currently, from Blink (Chrome) to WebKit (Safari desktop), why does iOS deprecate it?
Posted
by chingru.
Last updated
.
Post not yet marked as solved
0 Replies
691 Views
Hi all, In macOS Ventura, the Font Book application has a new feature that it can sort fonts by different language in sidebar, such like English, Japanese, Tranditional Chinese, Korean and so on. (not Smart Collection / Collections which can be customized, it's a built-in feature) The built-in fonts has be classified into correct language, however, the user installed font doesn't, even it is a Japanese / Chinese font, the Font Book still clssify it into English category. I'm confuse about the mechanism. In macOS Monterey, there's a "LanguageAlphabets.plist" file in Font Book package to recognize the language of font by matching the glyphs whether the font file contains or not. However, in Ventura, the Font Book application has been redesigned and i can't find the *.plist file anymore. Here's my question, What is the mechanism of language category in Font book? Does it depends on the font file (.otf/.ttf) itself, or macOS has a matching table for glyphs (similiar to *.plist file in Monterey) or other mechanism? If it depends on the font file itself, what is the tag or value in *.ttx (the depackage of font file from .otf/.ttf to XML) I should set? If the macOS has a matching table for glyphs or other mechanism, how can I find the detail between differnet language that I can set my font file in the correct language. Thank you very much.
Posted
by chingru.
Last updated
.