ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Embedded fonts question
Date: Sun, 26 Oct 2008 10:01:06 +0100	[thread overview]
Message-ID: <490431D2.3090103@web.de> (raw)
In-Reply-To: <54F3AE97-94F9-4F2A-8C27-F06CDE051982@trichotomic.net>

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
___________________________________________________________________________________


  reply	other threads:[~2008-10-26  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 17:12 David Wooten
2008-10-25 18:18 ` Pablo Rodríguez
2008-10-26  2:27   ` David Wooten
2008-10-26  9:01     ` Pablo Rodríguez [this message]
2008-10-25 19:38 ` luigi scarso
2008-10-26 10:24 ` Mojca Miklavec
2008-10-26 11:32   ` luigi scarso
2008-10-26 12:33   ` Martin Schröder
2008-10-26 13:17     ` luigi scarso
2008-10-26 13:42   ` Alan BRASLAU

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=490431D2.3090103@web.de \
    --to=oinos@web.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).