From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Syncing some doc fixes to v5-10
Date: Tue, 21 Sep 2004 20:29:01 +0200 [thread overview]
Message-ID: <m3sm9bv5le.fsf@defun.localdomain> (raw)
In-Reply-To: <87r7ow1rfp.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "Tue, 21 Sep 2004 07:55:22 +0900")
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".
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-09-21 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 15:26 Reiner Steib
2004-09-20 21:14 ` Jesper Harder
2004-09-20 22:55 ` Miles Bader
2004-09-21 18:29 ` Jesper Harder [this message]
2004-10-04 18:11 ` @documentencoding, `makeinfo --enable-encoding' (was: Syncing some doc fixes to v5-10) Reiner Steib
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=m3sm9bv5le.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).