From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Use of @insertcopying breaks gnus-manual*.ps.gz
Date: Wed, 01 Sep 2004 09:08:52 +0900 [thread overview]
Message-ID: <b9yvfeyyhnv.fsf@jpl.org> (raw)
In-Reply-To: <v9hdqji10m.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9hdqji10m.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:
> the use of @copying and @insertcopying in gnus.texi breaks the built
> of gnus-manual-a4.ps.gz and gnus-manual-standard.ps.gz.
> Probably texi2latex.el has to be adjusted, but I couldn't figure out
> how.
> Could someone please look into this?
Although I'm not troubled with it because of using Emacs CVS, I
noticed `@copying' is not supported by texinfmt.el in Emacs 21.3
and lesser and XEmacs.
configure
cd texi
make MAKEINFO=no EMACS=emacs-21.3
[...]
Formatting Info file: gnus
Converting gnus.texi to Info format...
Reading included file: gnus/texi/gnus-news.texi
Reading included file: gnus/texi/gnus-faq.texi
@copying is not handled by texinfo
make: *** [gnus] Error 255
It may not be a real problem since most people seem to have the
makeinfo command.
(I'm translating the Gnus manuals into Japanese. Using
texinfmt.el is the only way to format them, though.)
In addition, I'm using makeinfo v4.6 and it complains as follows:
gnus.texi:8543: warning: eacute is an invalid ISO code, using '.
gnus.texi:8543: warning: agrave is an invalid ISO code, using `.
gnus.texi:15714: warning: ecirc is an invalid ISO code, using ^.
gnus.texi:24829: warning: ccedil is an invalid ISO code, using ,.
gnus.texi:24846: warning: invalid encoded character `aring'.
gnus.texi:24936: warning: ccedil is an invalid ISO code, using ,.
emacs-mime.texi:1131: warning: iuml is an invalid ISO code, using ".
emacs-mime.texi:1144: warning: iuml is an invalid ISO code, using ".
emacs-mime.texi:1159: warning: iuml is an invalid ISO code, using ".
So far I don't know what causes them.
next prev parent reply other threads:[~2004-09-01 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:02 Reiner Steib
2004-09-01 0:08 ` Katsumi Yamaoka [this message]
2004-09-01 2:06 ` Katsumi Yamaoka
2004-09-02 14:34 ` Reiner Steib
2004-09-03 2:07 ` Katsumi Yamaoka
2004-09-20 12:14 ` Reiner Steib
2004-09-21 0:45 ` Katsumi Yamaoka
2004-09-21 8:21 ` Reiner Steib
2004-09-01 4:33 ` Katsumi Yamaoka
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=b9yvfeyyhnv.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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).