Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: @documentencoding, `makeinfo --enable-encoding' (was: Syncing some doc fixes to v5-10)
Date: Mon, 04 Oct 2004 20:11:57 +0200	[thread overview]
Message-ID: <v9hdpal5ea.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3sm9bv5le.fsf@defun.localdomain>

On Tue, Sep 21 2004, Jesper Harder wrote:

> Miles Bader <miles@gnu.org> writes:
>
>> Jesper Harder <harder@ifa.au.dk> writes:
>>
>>> Is it strictly necessary?  It doesn't really matter except for the
>>> hard-copy version.  And I'd rather not mess around with the Emacs
>>> Make/Automake files (which would be required).
>>
>> Are these changes that would be desirable in general for the emacs doc
>> Makefiles?
>
> I don't know ... if the Emacs docs contain many Texinfo-"encoded"
> Latin-1 chars, e.g. @aa{} and so on, I suppose it would be nicer to
> display them with the actual glyph, "å", rather than in an ASCII
> rendition, "aa".

Beside `gnus.texi', there are some other files in Emacs using
non-ascii characters (this list is most probably incomplete):

--8<---------------cut here---------------start------------->8---
emacs/man$ grep -ie '[äöüßáéíóúàèìòù¬]' -e '@aa{}' -e '@\"[aou]' *.texi
ack.texi:Torbj@"orn
emacs.texi:Dukhovni, John Eaton, Rolf Ebert, Stephen Eglen, Torbj@"orn Einarsson,
emacs.texi:Sebastian Kremer, Geoff Kuenning, David K@aa{}gedal, Daniel LaLiberte,
faq.texi:Roland Schäuble reports that Emacs 18.58 running on plain TOS and MiNT
gnus.texi:makes strings like @samp{déjà vu} look like @samp{d=E9j=E0 vu}, which
gnus.texi:@itemx ¬
ses.texi:Stefan Reichör @email{xsteve@@riic.at}@*
--8<---------------cut here---------------end--------------->8---

It becomes quite obvious that something is wrong when you look at the
info pages using...

LC_ALL=greek emacs -q -no-site-file --eval '(info "(efaq)Emacs for Atari ST")'

... or similar: You get "Schδuble" instead of "Schäuble".

IIRC, at least Latin-1 characters work correctly in info and dvi when
using --enable-encoding and @"a [1].

Bye, Reiner.

[1] http://search.gmane.org/search.php?group=gmane.comp.tex.texinfo.general&query=documentencoding+enable+encoding
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

      reply	other threads:[~2004-10-04 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 15:26 Syncing some doc fixes to v5-10 Reiner Steib
2004-09-20 21:14 ` Jesper Harder
2004-09-20 22:55   ` Miles Bader
2004-09-21 18:29     ` Jesper Harder
2004-10-04 18:11       ` Reiner Steib [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=v9hdpal5ea.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --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).