Print -> pdf -> save as postscript not working

• Mar 12, 2015 - 06:47
S4 - Minor
needs info

The option to save a file as postscript on Mac OS X (via print dialog: Print -> PDF -> save as pdf) produces a tiny and invalid postscript file. (This is on Mac OS X Mavericks). It is not a problem with the OS -- for example if I print to pdf or export to pdf, open the pdf in Preview, and save to postscript via the print dialog there, it works fine.


What version of MuseScore? And what about exporting to PDF *directly* from MuseScore - using File / Export (Save As in 1.3) instead of the print dialog?


Many thank's for the RC version!

Same Bug on Release Candidate if you use print to a PDF printer.

Yes you can use export PDF, but it's better to solve this issue.


Adobe PDF trace

%%[ ProductName: Distiller ]%%
MScore not found, using Courier.
FreeSerif not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: show ]%%


%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%

I wonder, though - the error message seems pretty clear that Distiller can't find the fonts bu8ilt into MuseScore. That's not really all that surprising - the fonts are not installed on the system in the normal way. When printing to PDFCreator or another third party printer driver, the print system presumably sends the driver the necessary fonts somehow. But perhaps because Apple provides some sort of special built in PDF support (I'm assuming that is what "Print -> PDF" refers to), the problem might be inherent in MacOS, or how Qt interacts with this particular print system. That is, we simply might not be sending the built in Mac PDF facility the necessary fonts, meaning the fault isn't necessarily with Distiller itself. I'm just guessing, though.

"Adobe's PDF printer is just not up to the task, use one of the freeware..."

Crash also with Cute PDF and i use Windows 7

Update Cute to last version, work Now

This is on mac OS 10.9.5 Mavericks, running a nightly from earlier this week (3/10 or 3/11). The issue for me is NOT producing pdf, it is producing postscript (.ps). I wanted do do this to see if I produced ps and use another program to convert that to pdf I would wind up with a pdf smaller than musescore generates via export to pdf (those files seem unnecessarily big).