https://bugs.documentfoundation.org/show_bug.cgi?id=153905
--- Comment #6 from Callegar <sergio.calleg...@gmail.com> --- As a final note, I would like to report that if you take the PDF file produced by LibO and you process it using `ghostscript` on a system that has the needed fonts, e.g. using gs -q -dNOPAUSE -dBATCH -dPDFSETTINGS=/prepress -sDEVICE=pdfwrite -sOutputFile=output.pdf input.pdf then the PDF file obtained by ghostscripts gets the fonts re-embedded as: name type encoding emb sub uni object ID ------------------------------------ ----------------- ---------------- --- --- --- --------- AKSFEQ+DummyName Type 1C Custom yes yes no 7 0 FNPCHA+DummyName Type 1C Custom yes yes no 9 0 LKVFDZ+ArialMT TrueType WinAnsi yes yes yes 11 0 UNQEAT+DummyName Type 1C Custom yes yes no 13 0 TFLMGS+DummyName Type 1C Custom yes yes no 15 0 Once this is done, the PDF file prints perfectly. So, I would tend to think that there is an issue in how LibO embeds the fonts in the PDF file when it exports it. -- You are receiving this mail because: You are the assignee for the bug.
