AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]()
I need a blurred version of an image that I can include in a pdf document. I need to use xelatex as I am using an iOS font. ![]() #APPLE FIXES PREVIEW BUT PROBLEMS WITH PDFKIT MAC#However, as this problem only occurs if xelatex is used (works fine with pdflatex), I am hoping that someone here can help with some sort of workaround that allows this to work on a Mac with Apple pdfKit.Īs, I have encountered numerous problems with Apple's pdfKit ever since High Sierra, I can't really want to wait around for them to fix it. The only two real ways to get this looking right - besides maflynn's preferred method - is to flatten/rasterize the document for viewing by others (using the source application), or to use the Windows version of Acrobat DC to embed the relevant fonts in a document (which is what I do when I'm sending PDFs to others when keeping searchable/editable text is desired).This seems to be a bug in Apple's pdfKit. A workaround is to ensure all of the relevant fonts are in an accessible directory/folder (such as the system's Fonts folder) and rebooting, but there's no guarantee that all of your apps will recognize those fonts - OS X's licensed Visual Postscript has been doing a decent job over the years but IMHO the SIP restrictions may hinder efforts to get things looking as you want them to. Some PDF reader apps attempt to render font information/appearance - some do it better than others, and there's no cross-app means to get around this. In the last couple of OS X iterations fonts aren't all placed in a Fonts or user's Fonts directory, and some devs - using MS with their Office and OneNote apps are embedding fonts directly in an app's Contents>Resources>Fonts folder along with other font-related resources. One other "bit" that could be leading to this issue you're experiencing is how SL and EC place and handle fonts. Design for your consumers - I do, and have for 15 years. #APPLE FIXES PREVIEW BUT PROBLEMS WITH PDFKIT FREE#Don't blame Apple as even Adobe has cut its ties to "PDF" - lots of decent free viewers are available, and its a matter of time before Adobe's free options "suck". ![]() Adobe "abandoned" designing PDF for the future recently, Apple cut their ties a few years ago. Simply put, design for the final product. I downloaded one of their (relatively-massive) PDF files that took lots of time to load and render, then used my local installation of Illustrator to replace 305 specific fonts with System fonts and sent it to several of my friends/clients - my optimized file loaded in 3-4 seconds to load and panned around "?instantaneously" as opposed to the "laggy" panning experienced by the original file(s) (found here: ). Some of their PDF files have hundreds - not dozens, but hundreds - of non-standard fonts and non-system fonts. I picked on one of my former clients - Metro (in Portland OR), which has posted several bike route maps, created on Macs (I've been in their offices since the mid-90s, so I know.). Scour the forums for some of my posts related to PDF files. Picking on just the "current version" is easy - which "Version 1.7" (no offense, KALLT) Version 1.7, or Version 1.7 (Adobe Extension Level 8)? Anyone who offers otherwise is not - IMHO - following what "PDF" was/is designed for, which I've posted here in MR's Forums before. Preview works perfectly well, given the constraints of the file format the app was/is designed for. You're first "question" (there wasn't a question mark.) is that IMHO nothing's "happened". Click to expand.I cropped out most of the post I'm replying to. ![]()
0 Comments
Read More
Leave a Reply. |