> /System/Library/Assets/com_apple_MobileAsset_Font3/3abf40766b4cf50b77ebd28e6affbd1849ea61c6.asset/AssetData/Baoli.ttc > /System/Library/Assets/com_apple_MobileAsset_Font3/.asset/AssetData/ > in directory hierarchies with random-like paths (or maybe checksum-based), one for each font file, of the form > /System/Library/Assets/com_apple_MobileAsset_Font3/ > - When asked for, the fonts are downloaded from. > /System/Library/Frameworks/amework/Frameworks/ATS.framework/Support/FontSubsets/ > - Font stand-ins (used probably for the greyed-out samples in Font Book) are installed with the OS at > The way this seems to work is as follows: > Opening a Pages document (from a previous macOS version) with text in a downloadable font causes the font to be downloaded without asking for the user's permission first. > Similarly, a XeTeX document calling a downloadable font produces a request like > My first encounter with downloadable fonts was when launching Mozilla Thunderbird and Adobe Illustrator CC for the first time after installing Sierra: for Thunderbird, a message popped up requesting approval for downloading and installing Osaka for Illustrator, the same occurred for LiHei Pro, Hei and STHeiti. > The situation is described in greater detail in Apple's list of Sierra fonts at. > These fonts are listed in Font Book, which shows them greyed out and provides links to download them: > The most significant change in Sierra font-wise, is the introduction of "downloadable font assets": fonts which are referenced in the OS but aren't installed with it, and instead are downloaded individually at will from the Apple servers. The immediate incentive came from last week's TeX Live update of jfontmaps into ptex-fontmaps: among the changes was the mention of Sierra Japanese fonts toppanbunkyu-sierra. I'd been hoping to prepare it ever since Sierra went to Public Beta, but couldn't find the time. > As a New Year treat, here is an update of my macOS font catalog for Sierra. There is absolutely no need to answer this message, and I won't have the time nor opportunity to pursue the matter anyway. I'm forwarding this in case it can be useful to you at some point. In texmf.cnf then running "luaotfload-tool -update -force" allows LuaTeX to use them. OSFONTDIR=/System/Library/Assets/com_apple_MobileAsset_Font3 They are then installed (on my setup at least) inside /System/Library/Assets/com_apple_MobileAsset_Font3/. They are downloaded from Apple when requested by the user or by an app. Sierra introduces a new "downloadable font asset" category, of fonts which are referenced by the OS but not installed. With 2.7, only two fonts crash it, and these are malformed. With 2.6, a number of fonts crashed LuaTeX. As a rule, luaotfload v2.7 fares much much better with the macOS fonts than v2.6. Two conclusions in it are of direct relevance to luaotfload, and I thought might interest you: It's mostly about a systematic testing of the fonts in macOS 10.12 (Sierra) with both XeTeX and LuaTeX. Messages sorted by: įollowing is a message I posted a few days ago to the MacTeX list (private, for the group of people preparing the MacTeX distribution every year). LuaTeX and macOS Sierra (was "Re: Removed support of dfont format in luaotfload") Bruno Voisin bvoisin at LuaTeX and macOS Sierra (was "Re: Removed support of dfont format in luaotfload")
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |