From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font embedding
Date: Tue, 28 Feb 2012 23:38:43 +0100 [thread overview]
Message-ID: <357A5FBE-5496-41E3-A363-00E983ADAF33@fiee.net> (raw)
In-Reply-To: <CAP7DCDdBM4xn=PSKR39-VPX5xHkOqoifWfBFbt=-=TpWb2v1Jw@mail.gmail.com>
Am 2012-02-28 um 21:23 schrieb Martin Schröder:
> 2012/2/28 Honza Hejzl <honza.hejzl@gmail.com>:
>> PDF file must be version 1.3
>
> Yellow pages. Now. Choose one that can handle PDF/X-4.
>
> PDF 1.4 was released in 2001. If they need 1.3, their software is
> probably a decade old.
No, they just keep to standards they can handle. There’s not so much
wrong about PDF/X-1 and -3.
I guess the "full font embedding" is just a misunderstanding. The
instructions Honza quoted didn’t say "full".
I experienced a lot of printshops whose instructions were for office-
type laymen and just utterly wrong for professionals*, e.g. to deliver
single page pdfs or to convert all fonts to curves. Other printshops
never learned anything in the last 20-30 years - they earned their
insolvence.
*) or, say, people who know stuff - most *amateur* (in the meaning of
the word) typographers are better than everyday professionals.
Honza, I guess you need only this information: ConTeXt embeds fonts
very well and standards compliant. If it doesn’t, it’s an error that
we can track (maybe missing or corrupt font on your system).
Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-28 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:39 Honza Hejzl
2012-02-28 14:48 ` Hans Hagen
[not found] ` <CAG4oGFTtx7CptROLoy7=fjdTrrtMpHpyWWdk0c4nWfZfUyUwvA@mail.gmail.com>
2012-02-28 15:13 ` Hans Hagen
[not found] ` <CAG4oGFTQ082S=c4gF4u15TZKv7VMT0m2Unr3rKTT0xnYwQi4dg@mail.gmail.com>
2012-02-28 18:08 ` Honza Hejzl
2012-02-28 20:11 ` Hans Hagen
2012-02-28 20:23 ` Martin Schröder
2012-02-28 22:38 ` Henning Hraban Ramm [this message]
2012-02-29 3:36 ` luigi scarso
2012-02-28 15:02 ` Martin Schröder
2012-02-28 17:38 ` Khaled Hosny
2012-02-28 20:22 ` Hans Hagen
2012-02-29 7:34 Honza Hejzl
2012-02-29 7:43 ` luigi scarso
2012-03-01 8:59 ` Hans Hagen
2012-02-29 11:08 Honza Hejzl
2012-02-29 11:43 ` luigi scarso
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=357A5FBE-5496-41E3-A363-00E983ADAF33@fiee.net \
--to=hraban@fiee.net \
--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).