Copy link to clipboard
Copied
A notice flashed on my screen today that said Acrobat Pro DC had been updated and that a system restart was required to use it. I ignored it at that moment because I wasn't ready to print anything, then forgot about it until I tried to print from Firefox and got the following:
%%[ ProductName: Distiller ]%%
Lato-Regular not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: xshow ]%%
Stack:
[72 75 75 33 75 70 35 32 76 34 79 78 78 0]
(
)
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
_____________
Oh, yeah, that update thing ... so I rebooted. But I'm still getting the same message. I can actually open Acrobat Pro DC, and I can print to it from my regular softwares; but from Firefox, I'm getting this error message, and I do a LOT of printing from Firefox, so I need this solved. Anyone have any ideas? Thanks much in advance.
Copy link to clipboard
Copied
Am I correct to understand you are printing to paper from Firefox, but you are receiving a Distiler error message instead?
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Firefox has nothing to do with Acrobat Pro DC in this regard.
But out of curiosity, is this happening also with any other web browsers?
And the main question is, did this problem still manifested after a restart? Every update always requires restarting a computer (at least on MS Windows, mostly).
Because if that's the case then it really deserves attention from Adobe.
Unless you were using the Acrobat PDF Maker extension in Firefox, for which Mozilla discontinued its support, I don't think there's a lot that Adobe can do about that.
If you had that extension before in Firefox, and you also updated Firefox, that extension is not supported by Mozilla anymore until further notice. You'll need a Chrome-based web browser like the new Micrososft Edge web browser, Chrome web browser, and / or Internet Explorer 11 to be able to use that extension.
However, that doesn't seems to be the issue on your end. I just added that info to rule out what could be wrong.
In my humble opinion, I think the problem was that you have set your default printer to Adobe PDF in your operating system, or , you manually chose that printer option from Firefox.
If yes, consider that using Adobe PDF as default printer uses UTF-8 for character encoding. And if you're on a MS Windows 10 machine, windows supports UTF-16 for character encoding natively. This means that a lot of API's will have to translate back and forth between UTF-8 and UTF-16 character encoding between applpications. If you didn't restart after the update took place, this could've triggered the problem.
If my suspicion is correct :
Copy link to clipboard
Copied
Please ignore my long reply.
Seems that we were typing at the same time.
Now I feel really dum after posting all of that unnecessary geeky vomit.
Copy link to clipboard
Copied