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: Sat, 25 Oct 2008 20:18:47 +0200	[thread overview]
Message-ID: <49036307.8020106@web.de> (raw)
In-Reply-To: <72FF8678-F9E1-4C5F-BBD2-0C9E9C029340@trichotomic.net>

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).
> 
> Now as far as I can tell, fonts /are /embedded. It was made with context 
> MKII, using hz and hanging punctuation, etc. When I look at the document 
> in Adobe Acrobat, and check the document/font details, it gives a list 
> of embedded fonts only. 
> 
> I'm not certain that the printer is in the right, but how can I tell? Is 
> it possible that the pdf was altered when transferred from me to the 
> publisher then to the printer? That compression of the pdf (zip) had any 
> impact? Any other possibilities? What do you need to know to offer 
> advice? ---I can send the file or a part of it if it is needed.

Hi David,

if the printer didn't alter the file and the fonts were embedded in the 
original PDF document, they didn't vanished. The zip compression doesn't 
alter those things (AFAIK).

A way to check whether the fonts are embedded or not, you can download 
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.02pl2-dos6.zip (if you are using 
Windows) and run from the command-line

	pdffonts dissertation-filename.pdf

Replace dissertation-filename.pdf with the actual file name and pdffonts 
will display all font information.

If this is too complicated for you, send me the original file in a 
private reply and I will post the results.

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-25 18:18 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 [this message]
2008-10-26  2:27   ` David Wooten
2008-10-26  9:01     ` Pablo Rodríguez
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=49036307.8020106@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).