Is anyone else having prints show up with weird results? When I print from Logos, numbers especially come out looking horrible. I've attached a PDF that I made, and it actually looks like the hard copy the printers produce (tried it on multiple printers).8231.Psalms 1–72_ An Introduction and Commentary.pdf
Yeah, I've been putting up with this throughout most of the beta, but never got round to filing a bug report. It's a real pain.
Hmmm... could it have something to do, perhaps, with your own computer's fonts, i.e. your own computer doesn't have the font that Logos is using, so when it comes to print, it has to use the substitute that you wind up with in your printout?
Just a thought...
The really odd thing is that it was happening to me both before and after I installed the font Athelas on my computer. (I liked the font so much, I have started using it at our church)
This still occurs in 4.5 beta 9, though it's not as bad as it used to be:
4263.Psalms 1–72_ An Introduction and Commentary.pdf
Yes - numbers are the worst in the printing.
I am unable to reproduce this issue with 4.5 Beta 9. What steps and/or programs are you using to create PDF's from the Windows version of Logos?
What steps and/or programs are you using to create PDF's from the Windows version of Logos?
This occurs when I print to a PDF, or when I print to the printer - any printer.
I did some testing, but for me it occurred only when the font was set to "Default".
I have been able to reproduce the issue and have written a case for our Development Department.
Here is a workaround - using the Default Font, export the file as an XPS Document (instead of Printing to a PDF), and then open the XPS Document in Microsoft's XPS reader and print it from there. The printed output should exactly match the screen rendering in Logos.
Kevin,
Can you also check this issue? Whenever I try and print directly to Adobe PDF, I get a version of the following error:
===
%%[ ProductName: Distiller ]%%
00nnvjc not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: xshow; ErrorInfo: CharOffsets ¤e
)
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
Whenever I try and print directly to Adobe PDF, I get a version of the following error
Fred, this should solve it: http://community.logos.com/forums/p/24126/180325.aspx#180325
If not, there are two other threads that may help:
Thanks, Mark. I was able to create with Acrobat. But I still have the issue with the numbers.0486.English Standard Version.pdf
Fred,
Printing to a PDF directly is not a native Windows function but involves third party applications which we cannot support. The PDF documents linked in thisthread were created by three different applications - pdfFactory Pro, GPLGhostscript, and Acrobat Distiller. Thereare many such applications; PDF Writer, PDFlite, CutePDF, PrimoPDF, PDFCreator,PDF-Printer, Win2PDF, etc. Each of these might create slightly different looking output and some might work better than others, but we have no control over that. Saving the document to an XPS file is however supported and printing from there is your best bet until the printing (to a printer) issue is fixed.
Is anyone who is experiencing this bug (weird fonts in print) running Windows Vista? Preliminary testing here indicates that this is a bug only on Windows 7 (not Vista). If you do have this problem on Windows Vista, please let us know. (Please include whether the problem happens with a "real" printer, or a "Print to PDF" printer, or both.)
If you're experiencing this on Windows 7, you don't need to post; we're able to reproduce the problem in-house and are looking into it.
So either no one is having printing problems on Windows Vista, or no one is reading this thread. [:)]
The printing problems on Windows 7 should be resolved in the next 4.5 beta.
Geeks might like to read the Logos blog on how this bug was fixed:http://code.logos.com/blog/2011/12/printing-from-net35-in-windows7.html
It might also provide useful insight for others on the process of bug-fixing and workarounds. I'm impressed that Logos persevered with this one, particularly given that it's not a fault with Logos but with the underlying framework.
