collectorlobi.blogg.se

Fontbase file still present
Fontbase file still present












fontbase file still present

It appears that it is simply overloaded and can't handle any more input. Changes made just before the slowdown/freeze-up are there (eventually). Just gets to a point where I can't go any further and need to close the doc (waiting until it eventually closes) and reopen in order to proceed. I had thought it might have been an issue with 1.10.1, so tried the current beta for 1.10.2, but it does pretty much the same thing. The doc file size is only 7.4 MB with linked graphics.

fontbase file still present

I have 72 GB RAM, so not short on that, as well as a new iMac. The doc's single spread is 3748mm x 2280mm in 300dpi, cmyk (actual size trade show panel). I opened it for the first time in Publisher today for revision work from a newly done IDML export from the original ID CS5 file. Never had this issue working on several of the same files in ID CS5 many, many times. (This is the first time working on them since Publisher came out). Files are on a local drive (RAID5 Thunderbolt 3). I think I have the APub performance settings at about a max setting (see attached). Overall, the doc is not highly complex with only about 9 images/pics. Just physically large, but as I said, never once caused any slowdown in ID CS5 for the many, many revisions and working sessions in the past.Ĭan upload (with link) a package if needed. Just very difficult to work on this project in Publisher and hard to understand why.

#Fontbase file still present pdf#

I normally participate fairly deeply in the betas as these new features are added, but when PDF Passthrough happened, I was too busy to get more than superficially involved. Thus I missed the discussion on the ramifications for Preflight.Īlso seems odd that something so critical (the Preflight errors show virtually all the time due to the default being for an X-PDF) wasn't covered in the new video tutorial for the new PDF Passthrough/Placement. It would seem that most all users would get a preflight error after placing a PDF for passthrough since using PDF-x output isn't all that common except for users working with prepress requirements. I'm guessing most users simply ignore the errors (or don't use Preflight) because trying to find out the actual meaning of the preflight error is very difficult to ascertain. Perhaps it should be added to a Publisher FAQ section until it is better described in the Help. I watched the progress of PDF passthrough with great interest during the beta process since I used to have a background in print shops, newspapers, publications, etc. where it is a critical feature for modern publishing. I realize that it is still a work in progress with some rough edges still, so can understand how this might have been overlooked. Pretty simple to fix, assuming you know where to look!! □ Hoping at least the presence of this thread will help others who, like me, are initially baffled by the preflight error messages and can't find much of any info on the errors. Overall, Affinity apps just keep getting better and better.

fontbase file still present

A few bumps along the way, but so refreshing as compared to the old standard apps. I was an Aldus PageMaker v1 user and trainer, so it's been a long journey to get to this point. While Publisher still has some glaring missing things, it is today highly competitive with far greater customer support. Not sure how this got moved from Bugs to Questions. I've looked in the online Help for Publisher regarding the recent feature to Place PDFs as Passthrough, but I cannot see anything in the entire online Help that says what kind/type of PDF will actually passthrough without rasterizing on export (thus, not really passthrough).Īs per my original post, a PDF created in v1.10 of Designer apparently cannot be used for Passthrough in Publisher v1.10? That doesn't seem to make any sense, thus the question if this is a bug. Placing a Designer PDF shouldn't end up getting rasterized when exporting a PDF of the Publisher document, at least I wouldn't think so since that would be of little use. If Passthrough doesn't work with Designer-created PDFs, then how do I create a PDF that can be Placed for Passthrough in Pub? Right now, I cannot seem to locate any information of what is allowed to be Placed as a Passthrough PDF if I want to avoid the Preflight error message that it will be rasterized.














Fontbase file still present