From: Taco Hoekwater <taco@elvenkind.com>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unreadable characters in embedded PDF file
Date: Mon, 10 Jan 2011 09:19:14 +0100 [thread overview]
Message-ID: <4D2AC102.7090409@elvenkind.com> (raw)
In-Reply-To: <4D2ABE2B.9080909@gyza.cz>
On 01/10/2011 09:07 AM, Jaroslav Hajtmar wrote:
> Hello all,
> Often I include external PDF files into PDF document generated by ConTeXt.
> When I create a PDF document containing text in Scribus (or other
> application) and then I put it to my PDF file (generating by ConTeXt),
> then in final PDF document are unreadable characters.
>
> Is there a problem in Scribus character encoding or the fact that the
> fonts contained in the included PDF file ConTeXt unknown?
It is hard to debug this without an actual file, but it sound similar
to a problem we heard about a few weeks ago. Does this thread appear to
refer to the same problem you have:
http://tug.org/pipermail/luatex/2010-December/002354.html
If yes, then the fix is already in the luatex repository.
Best wishes,
Taco
___________________________________________________________________________________
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:[~2011-01-10 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 8:07 Jaroslav Hajtmar
2011-01-10 8:19 ` Taco Hoekwater [this message]
2011-01-10 9:00 ` Jaroslav Hajtmar
2011-01-10 9:05 ` luigi scarso
2011-01-10 9:05 ` Taco Hoekwater
2011-01-10 9:56 ` Jaroslav Hajtmar
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=4D2AC102.7090409@elvenkind.com \
--to=taco@elvenkind.com \
--cc=hajtmar@gyza.cz \
--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).