From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Alain Muls <alain.muls@telenet.be>
Cc: emacs list <help-gnu-emacs@gnu.org>
Subject: Re: Encoding of latex files
Date: Thu, 24 Jan 2008 14:36:28 +0100 [thread overview]
Message-ID: <C9847036-3ACD-4E3B-AA63-0BEFE9645980@Web.DE> (raw)
In-Reply-To: <47987D2D.1070002@telenet.be>
Am 24.01.2008 um 12:57 schrieb Alain Muls:
> Is there a way to have the files generated by the answer package be
> in UTF-8 and have the accented chars available
Are the LaTeX correctly encoded? The modeline gives a pointer near
its left edge. You can click on that marker with the mouse pointer ...
Is the LaTeX file's preamble correctly set up for UTF-8 or "utf8x"
input and T1 font encodings? I have not much experience with UTF-8
input encoding in LaTeX, and this experience is mostly bad, that I
keep using XeTeX, an UTF-8 native TeX system that can use TeX and
system fonts (http://scripts.sil.org/cms/scripts/page.php?
site_id=nrsi&item_id=XeTeX&). Have you thought of using the textcomp
package? Do you use babel?
I found LaTeX classes that have problems with some content. Switching
to modern T1 font encoding can be helpful, too. For a proof: try some
simple and basic report or article or book with just some paragraphs
of senseless text and many, many header and sub-header and sub-sub-
header lines with plenty of accented French characters. If you can't
achieve this basic task, then your TeX system is 15 or 20 years too
old or your preamble is bad. If you see all accented chars, then
answer.sty might be bad.
(I can send you privately a preamble that deals with pdfTeX, XeTeX,
DVI and PDF output and the proper UTF-8 input encoding.)
--
Greetings
Pete
The human animal differs from the lesser primates in his passion for
lists of "Ten Best."
– H. Allen Smith
prev parent reply other threads:[~2008-01-24 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 11:57 Encoding of latex files Alain Muls
2008-01-24 13:36 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C9847036-3ACD-4E3B-AA63-0BEFE9645980@Web.DE \
--to=peter_dyballa@web.de \
--cc=alain.muls@telenet.be \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).