ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Honza Hejzl <honza.hejzl@gmail.com>
Subject: Re: Font embedding
Date: Tue, 28 Feb 2012 21:11:57 +0100	[thread overview]
Message-ID: <4F4D350D.2040101@wxs.nl> (raw)
In-Reply-To: <CAG4oGFS2QLxVwzuVhB6X4EPAm+XMjCfmYxjC003N+zSmqpVErA@mail.gmail.com>

On 28-2-2012 19:08, Honza Hejzl wrote:
>> Check the yellow pages for a printing house that does not demand that. :-)
>>
>> Best
>>    Martin
>>
>>
> I am sorry, but that is absolutely typical demand, I have never seen at
> least one printing house which does not demand that... (And this is not a
> solution! :o))

Eh .. you mean that most printing houses demand *full* inclusion?

> PDF file must be version *1.3*

Hm ... reminds me of printing houses that convert the pdf to ps and use 
quark for imposition, don't want to update acrobat for a few hundred 
euro but expect their customers to invest a lot in them.

I'm curious what Luigi thinks of this (as he works at a lerge printing 
house).

> Embed the typeface in the document along with the image data. Avoid using
> OPI commentaries! The typefaces used may be of the following standards: *
> Type1*, *TrueType*, *and Opentype*. As a matter of principle, the data is
> provided as a composite (not separated). Formats other than PDF are
> accepted only after prior agreement.

I wonder what they mean with 'standards' ... take openstype: only some 
splines are included and some width information. So, say that they want 
zapfino to be fully included: they get megabytes of shapes, completely 
unorganized (apart from maybe the fact that one can tell what unicode or 
sequence of unicode it is). No feature data, no kerning, etc. So, this 
demand for 'full embedding' to me more sounds like weird.

> The PDF provided file should especially not contain any kind of
> meta-information, hypertext link, etc.

that's easy, although even a version 1.3 *only* viewer (if you can still 
find one) is supposed to ignore annotations it does not know

[i could imagine no objects streams but one can easilly convert a 1.X 
file into a 1.y file using acrobat]

> Everyone in printing industry *knows* what does it mean "to embed fonts",
> it is similar like when somebody wants pdf x-1a file (in printing industry
> the standard).

sure, but I'm not so sure if everyone expects one to embed all that 
unused information

(btw, so far we never had to provide a specific pdf/x version so there 
are printing houses that are flexible enough to deal with it)

> I am not a programmer, I don't know what does it mean in a code point of
> view. Trust me, embedding of fonts is the standard ("if you are not able to
> provide us the file as we need, your client should find another typesetter"
> - who typesets in InDesign). InDesign subsets typically just fonts used for
> texts where is not used 100 % of alphabet (pdf export settings).

it depends ...

- a typesetter produces a file
- in some kind of valid pdf
- that than can be converted by whoever gets that file

a printer might decide to drop features (because he cannot print it) or 
the publisher's prepress department can decide to downsample or convert 
to gray or ...

in your case the printing house does not like what indesign does by 
default, but often it's indesign that sets the standard of what to 
expect so it all depends ... everyone in the publishing chain who claims 
that 'this or that is the standard' is of course right in its own 
perception

anyway ... in your case you can say:

\setupbackend[format=PDF/X-1a:2001]

and get 1.3 (unless of course features are used cq. images included that 
demand otherwise)

and you can best also say

\nopdfcompression

just to be sure that the printing house cannot complain about compression

and then there is

\enabledirectives[fonts.embedall]

but that doesn't work unless you add line 205 in font-con.lua:

             tfmdata.embedding = embedding

(I'll add that line in the next beta)

which will embed a font (but of course still quite validly use a subset 
vector).

Graphics and other resources are completely out of context/luatex's 
scope as are all kind of other aspects,

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-02-28 20:11 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 [this message]
2012-02-28 20:23           ` Martin Schröder
2012-02-28 22:38             ` Henning Hraban Ramm
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=4F4D350D.2040101@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=honza.hejzl@gmail.com \
    --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).