Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: @documentencoding
Date: Wed, 03 Mar 2004 18:27:38 +0100	[thread overview]
Message-ID: <v9ishl7sdx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3oerdkgzi.fsf@defun.localdomain>

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, but in Emacs
21.3.50 (CVS) it works:

,----
| (defvar texinfmt-version "2.40 of  6 Dec 2002")
| [...]
| (put 'documentencoding 'texinfo-format 'texinfo-discard-line-with-args)
`----

> The only non-ASCII chars I could see are:
>   é à ê ç å ¬
> which are all Latin-1.

Correct.  But all non-ascii characters have been turned into
`eight-bit-graphic', now.

> 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.

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.  But I'm not able to reproduce it now (Dunno if
it's related to your changes.).  I will try look into this again
later.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2004-03-03 17:27 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   ` Reiner Steib [this message]
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=v9ishl7sdx.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).