From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: how to avoid CID Identity-H encoding?
Date: Fri, 27 Jul 2012 11:50:09 +0200 [thread overview]
Message-ID: <50126451.5000009@wxs.nl> (raw)
In-Reply-To: <9F27E004-9100-47EF-AC99-7EBACE80A80D@st.estfiles.de>
On 27-7-2012 11:36, Steffen Wolfrum wrote:
>
> Am 26.07.2012 um 19:35 schrieb Hans Hagen:
>
>> On 26-7-2012 17:59, Steffen Wolfrum wrote:
>>> Hi Hans, hi friends,
>>>
>>> while the PDF that are produced by MkIV show no problems, some applications that use these PDF files for post-processing have big problems with CID/Encoding Identity-H.
>>>
>>> For example (as far as I have understood) german umlauts eg. "ä" are not recognized anymore but split in eg. "a" and diaeresis (with a space between?).
>>>
>>> I was told, that other PDF creators have an option to avoid using this kind of encoding.
>>>
>>> Is this also possible with MkIV?
>>
>> afaik context output the right tounicode info so i have no clue what goes wrong there
>
> me neither.
>
> the pdf produced with MkII never ran into this post-processing trouble.
> they had this font info, eg.:
>
> Type: Type 1
> Encoding: Custom
probably not always, i.e. when ttf fonts were used it would use those
and related embedding methods but hardly anyone uses ttf in pdftex
> while all fonts I have tested with MkIV result in this:
>
> Type: Type 1 (CID)
> Encoding: Identity-H
>
> and this double-byte encoding confuses the pdf-post-processing machines (I was told).
> therefore we are asked to change it.
you can try to send them ps (pdftops)
> is there a chance to do so?
they should update their machines (read: there is no way that luatex
will provide split into type1 functionality)
(Luigi and Martin probably can explain it better)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-27 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 15:59 Steffen Wolfrum
2012-07-26 17:35 ` Hans Hagen
2012-07-27 9:36 ` Steffen Wolfrum
2012-07-27 9:50 ` Hans Hagen [this message]
2012-07-27 10:49 ` Steffen Wolfrum
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=50126451.5000009@wxs.nl \
--to=pragma@wxs.nl \
--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).