Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: @documentencoding
Date: Thu, 04 Mar 2004 01:36:55 +0100	[thread overview]
Message-ID: <m3ptbth2hk.fsf@defun.localdomain> (raw)
In-Reply-To: <v9ishl7sdx.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 03 Mar 2004 18:27:38 +0100")

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> On Wed, Mar 03 2004, Jesper Harder wrote:
>
>> "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?
>
> In Emacs 21.3, `texinfo-format-buffer' doesn't have it

Ah, thanks.  That should be easy enough to fix in infohack.el.  Does
it work for you now Kevin?

>> It isn't really 8bit-clean either, so we should use the Texinfo
>> accents instead, @aa{} etc. `¬' isn't supported by Texinfo, though.
>
> I managed to produce dvi and info files with all Latin-1 except `¬'
> some hours ago (reverting the file back to Latin-1 and _with_
> @documentencoding.

Without changing the 8bit chars to Texinfo commands?  I don't think
that can work.

I've changed everything except `¬' now, and added --enable-encoding to
get the real characters in Info.



  reply	other threads:[~2004-03-04  0:36 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 ` @documentencoding (was: Changes committed gnus/texi (gnus.texi)) Jesper Harder
2004-03-03 17:27   ` @documentencoding Reiner Steib
2004-03-04  0:36     ` Jesper Harder [this message]
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=m3ptbth2hk.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).