![]() ![]() ![]() Note: This Time Machine backup folder DID NOT have any "%3A" versions of the. ![]() (I put a duplicate copy of the current Sierra FontCollections folder on my desktop and placed the Time Machine FontCollections backup folder on my desktop just in case something went haywire - can't be too careful). Restore a Time Machine backup folder of (User > Library > FontCollections) from a date prior to the upgrade to Sierra. collection files in User > Library > FontCollections folder automatically update to reflect the new name as well (the corresponding example file would update to "web sans llection"). Open Font Book in Sierra and manually remove all the colons from the collection names within the Font Book application (e.g., "Web: Sans Serif" to "Web Sans Serif") so that all of their corresponding. I've been using Time Machine for backups since before my Sierra upgrade, and was personally able to remedy my issue using the following process (I deliberately overarticulated the steps, so as to make sure it's clear what's happening):ฤก. All the other collection files had only 1 corresponding file, so I surmised that the presence of the special character (in this case, the colon) in any of my font collection folder names must be the issue. I navigated to my FontCollections folder (User > Library > FontCollections), and I noticed that, in Sierra, all the Collection folders with names that included colons now had 2 corresponding files listed in the FontCollections folder - one that represented the colon with a "/" character (e.g., "web/ sans llection") and then another that used a "%3A" (e.g., "web%3A sans llection"). After upgrading to Sierra, I noticed that a similar issue was happening to all my font collections that had a colon in their names (e.g., "Web: Sans Serif"). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |