Embedded Fonts Issue?

cpuetz · Post by **cpuetz** » Fri Jul 06, 2007 2:06 pm

New user to PDF Xchange Viewer - When sharing a completed pdf (or even opening it in Adobe Reader myself) and trying to print, Adobe Reader can't print due to an error that it cannot extract the embedded font. When I look at the document properties in Xchange, there is one encoding for some of the fonts (WinAnsiEncoding) and another encoding for others (Identity-H). It seems the encoding used by Xchange is Identity-H as using a new font embeds the font in the document with that encoding.

So, how can I go about using the software but share the PDFs I create with people who don't have it (other than telling them to use Xchange that is)?

Thanks.

Fri Jul 06, 2007 2:09 pm

Can you send us sample file which causes troubles ?
I'm afraid trouble isn't with encoding, but with the font.

cpuetz · Post by **cpuetz** » Fri Jul 06, 2007 2:16 pm

I downloaded the most recent Adobe reader (v 8.1) and everything seems to work fine. I think the other folks are using v 7.0. I can't send the actual file because it contains confidential information, but I will create another file, confirm the error is happening, and send that. It will be a little bit, however.

cpuetz · Post by **cpuetz** » Fri Jul 06, 2007 2:35 pm

Apparently there are bigger issues with my system (and quite possibly the reason for the problem). Now any pdf I create with Xchange ends up being damaged and unable to be opened either in Adobe or Xchange. I had this error with the previous version from time to time, but the upgrade seemed to fix this.

So, at this point I've got some cleaning and reinstalling to do. I will report back if/when I'm able to recreate this error. Otherwise just mark it up to a fluke system issue.

Thanks for the prompt attention though!

---Additional----
I have uninstalled and reinstalled both Xchange and Adober Reader (to v.7) and the problem has disappeared (but the fonts still show the encoding as Identity-H).

I have, however, determined that if I use "Save As" to save the pdf, I end up with a corrupted file that can't be opened by Xchange or Reader. Using "Save Copy As" the first time (so I don't overwrite the original pdf) works.

Thanks again!

cpuetz · Post by **cpuetz** » Mon Jul 09, 2007 6:57 pm

I wanted to follow up on my posting. Even though reinstalls on my system seemed to work, it turns out I misunderstood the error that was seen by the other user. They were able to open the PDF, but when they went to print, the error about "unable to extract font" came in. Please note the other users are using Adobe v7.09 and I cannot force them to use PDFXchange just for my submission.

I've changed the contents of the file to delete confidential information. This is a PDF that comes from the state agency in a form that cannot be filled in, so I'm using the typewriter function of PDFXchange to type the information on the form.

In addition - I have confirmed through repeated testing that when I use "Save As" rather than "Save" or "Save Copy As", the resulting PDF is corrupted. For review purposes, I've attached the PDF as received from the State Agency, my "john doe" one that won't print and finally the resulting corrupt PDF when using "Save As".

Thanks for any examination of these items you make.

Tue Jul 10, 2007 7:21 am

Thanks for files. Looking now on this and will let you know when the trouble will be fixed.

Thu Jul 12, 2007 8:25 am

Do you use any AV software? If yes, can you say which one (including version number) and its settings ?

cpuetz · Post by **cpuetz** » Thu Jul 12, 2007 4:31 pm

Yes - I use AVG Anti-Virus. Version 7.5.476.

As for what settings you are looking for, I'm not sure what you mean. The scan takes place weekly, the email protection is also enabled and updates are checked daily.

Curtis

Thu Jul 12, 2007 5:04 pm

I'm asking because our method of working with files (via CreateFileMapping, MapViewOfFile, etc. API functions) cause troubles with some AV programs (for example McAfee).

Can you check with turned off AV?

contact2oli · Post by **contact2oli** » Sat Mar 22, 2008 11:53 am

Hello,

I have exactly the same problem with portable version.

I open a PDF file with Acrobat Reader 5.0 => OK
I open it with PDF-XChange Viewer Build 2.035, add a text zone and 'save as'.
I open the new file -> acrobat reader says it's corrupted.
But PDF-XChange Viewer doesn't complain -> it can open it.

I have same problem if I modify the pdf and try to print it with a pdf printer.

I also have AVG antivirus. I try after quitting the application -> unsuccesful...
I try to add attachment but it was not allowed (extension forbidden)

Bhikkhu Pesala · Post by **Bhikkhu Pesala** » Sat Mar 22, 2008 11:59 am

contact2oli wrote:I try to add attachment but it was not allowed (extension forbidden)

Allowable extensions = 7z ace gtar gz rar tar zip
7-Zip will provide slightly better compression than ZIP for most file types, and much better for some (e.g. TTF or TXT).

PS Build 2.036 is now available (check for updates).

contact2oli · Post by **contact2oli** » Sat Mar 22, 2008 4:22 pm

I have 0036 version (I didn't check and simply copy the version given in 'Important warning .txt' file

I made some tests:

Adobe Reader can't open file modified with Xchange Viewer.
Sumatra Reader can read them but the added texts don't appear.

I made a mistake in the previous post:
using a pdf printer works: the added text appears
-> but not a the simple solution (a pdf printer is not always installed when we use a portable application)

Post by **John - Tracker Supp** » Sat Mar 22, 2008 5:47 pm

The file has been written to PDF format 1.7 which requires a later version of Adobe Reader (8) then you currently have installed.

I suspect Sumatra also does not support the later PDF format - so you need to update to later releases of Adobe and Sumatra also.

contact2oli · Post by **contact2oli** » Sun Mar 23, 2008 9:46 am

OK, thanks.
I notice that Sumatra have an option to change the rendering and it displays well the modification.

But I don't understand your remark about version 1.7 of PDF.
Both files (original one and modified one) uses 1.7 version (I check by editing them in Notepad). So why acrobat reader v5 can read the first one and not the modified one ?

Sun Mar 23, 2008 10:24 am

Actually, original file is created using spec version less than 1.5 - it does not use Object Stream and XRef Stream features, so it can be opened in most pdf readers, even they do not support files with spec version 1.5 or higher. Updated file use both Object Stream and XRef Stream, so it can be only opened with readers which support at least spec version 1.5.