From: Jesper Harder <harder@myrealbox.com>
Subject: @documentencoding (was: Changes committed gnus/texi (gnus.texi))
Date: Wed, 03 Mar 2004 17:55:29 +0100 [thread overview]
Message-ID: <m3oerdkgzi.fsf@defun.localdomain> (raw)
In-Reply-To: <E1AyNmY-0003DZ-00@quimby.gnus.org>
"Kevin Greiner" <kgreiner@xpediantsolutions.com> writes:
> * gnus.texi: Wrapped documentencoding inside of iflatex as
> documentencoding is not supported by infohack.
In texi2latex.el or somewhere else?
@documentencoding doesn't do anything inside @iflatex/@iftex -- it
only affects Info and HTML.
> Changed file's character coding to utf-8 as the file contains
> characters that can not be encoded using iso-8859-1.
The only non-ASCII chars I could see are:
é à ê ç å ¬
which are all Latin-1.
Anyway, Texinfo isn't multibyte-clean so we can't use utf-8.
It isn't really 8bit-clean either, so we should use the Texinfo
accents instead, @aa{} etc. `¬' isn't supported by Texinfo, though.
next parent reply other threads:[~2004-03-03 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AyNmY-0003DZ-00@quimby.gnus.org>
2004-03-03 16:55 ` Jesper Harder [this message]
2004-03-03 17:27 ` @documentencoding Reiner Steib
2004-03-04 0:36 ` @documentencoding Jesper Harder
2004-03-04 1:00 ` @documentencoding Kevin Greiner
2004-03-04 1:57 ` @documentencoding Jesper Harder
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=m3oerdkgzi.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).