Text different in PDF export

[EJ]

Both files display identically on my system

Win2000. XaraX3.24. Adobe Reader 8.1.2.

Erik

[Colin Carpenter]

The attached PNG is what I actually see on my screen in Adobe Reade 8.1.2.

[steve.ledger]

First check you have all the standard WindowsXP fonts installed. If not, you can reinstall them from the XP CD

[amoore]

Both files look good ot me. WinXP SP2. Jaws PDF Editor v4.

[Colin Carpenter]

It's certainly curious, so I did another test.

I have a brochure that I created the other day, so I loaded it up in my registered version of Extreme Pro (V3.0 CD) and exported a page to a PDF. I then loaded the same file in the new trial version V4.0 and exported the same page to a PDF. Using PDFSAM I merged the two pages to create a 2 page PDF which I attach here. The first page is from V3.0CD and the 2nd is from V4.0 Trial.

I suspect that some folk will see them as the same, so I've also attached a screenshot showing the two pages side by side in Adobe Reader 8. They certainly look different to me.

Incidentally, I've never noticed a problem with Adobe Reader on anything else, so I figure I must be pretty up to dat with fonts et.

[Odat]

I just updated my linux reader to 8.12 and it still displays the same and I get the same error message. Attached is a smallish screen grab of what the text looks like for me.

[Colin Carpenter]

Curiouser and curiouser ... I just looked at the PDF on my laptop (XP Pro SP2 Adobe Reader 8.1) and both pages seem fine, yet my desktop shows the pages as shown on the screenshot.

[NeilH]

This may be something to do with a change we've made for 4.0. We no longer embed the 14 base fonts in PDF files, even if the embedding option is selected in export settings. However we do still embed the fonts for PDF/X export. To help us narrow this problem down can you try viewing the attached pdfx file (which has fonts embedded) to see if that displays ok? I removed the bitmaps leaving just the text by the way.

Thanks

Neil

[Charles Moir]

Works for me here. Mysterious. I suspect this may be font encoding problem. Can you please try this with v3.2 and let me know whether that works for you or not?