From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: "B. T. Raven" <nihil@nihilo.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Encoding help
Date: Wed, 3 Jun 2009 19:58:39 +0200 [thread overview]
Message-ID: <2C10CD43-EC63-43A2-B5B6-B5BE08AC6C78@Web.DE> (raw)
In-Reply-To: <RMidnVZ31Y-uKbvXnZ2dnUVZ_rqdnZ2d@sysmatrix.net>
Am 03.06.2009 um 19:35 schrieb B. T. Raven:
> In the meanwhile I made a similar pdf with auctex and the .txt file
> produced by Adobe Reader is even more fragmented than the first
> one. I guess this is not surprising after the orginal .tex file
> goes through \usepackage[utf8x]{inputenc} and \usepackage{babel}.
As long as you're using pdfTeX you can be sure that the PDF file has
composed characters (input encoding plays no role, because it's just
an *input* encoding). With a CMAP (character mapping, see 'texdoc -s
cmap') and an 8 (or 7) bit font encoding (T1, T2A, T2B, T2C, T5, OT1,
OT1tt, OT6, LGR, LAE, LFE) the composed characters can be mapped to
the ready to use (pre-composed) Unicode characters.
The use of XeTeX might be another option (it's xdvipdfmx output
driver inserts CMAPs into the PDF file). Or another PDF viewer, one
that automatically reloads the updated PDF output file.
--
Greetings
Pete
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
prev parent reply other threads:[~2009-06-03 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 16:51 Encoding help B. T. Raven
2009-06-01 23:05 ` Eli Zaretskii
[not found] ` <mailman.8314.1243897564.31690.help-gnu-emacs@gnu.org>
2009-06-02 16:25 ` B. T. Raven
2009-06-02 22:58 ` Eli Zaretskii
[not found] ` <mailman.8392.1243983524.31690.help-gnu-emacs@gnu.org>
2009-06-03 17:35 ` B. T. Raven
2009-06-03 17:58 ` Peter Dyballa [this message]
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=2C10CD43-EC63-43A2-B5B6-B5BE08AC6C78@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=nihil@nihilo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.