David Wooten wrote: > On Oct 25, 2008, at 11:18 AM, Pablo Rodríguez wrote: > >> David Wooten wrote: >>> Greetings all, >>> >>> A sad story: My context-typeset dissertation was printed/ >>> distributed by >>> a POD publisher with aweful typographical errors (like all commas >>> in the >>> main font being replaced by an ff ligature). Obviously the printer >>> didn't check their results. The file /reads/ fine both for me and the >>> publisher, but the printer let us know that the file is unprintable >>> due >>> to problems with fonts not being embedded (why they originally >>> printed >>> an "unprintable" file I'll never know). >>> >>> [...] > > Thanks, Pablo and Luigi, > > I was able to run pdffonts and check my file, it agrees with adobe > acrobat in saying that all fonts are embedded. So....I'm going to send > the publisher the current file and see what happens. I'm only 98% sure > that it's exactly the same as the original file I sent, so I am > slightly hopeful that it will work out better.
Hi David, I don't know whether this will work, but I think that the best option would be to try to get the PDF files both from the publisher and the printer and the check whether they are really the same (using md5sum or sha1sum) and then check the different file(s) with pdffonts. If the fonts are there, somehow the PDF interpreter that printed the dissertation wasn't able to read the font itself or its mapping. I hope it helps, Pablo ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
