Darryl> [ I'm not sure where to send this, and so I'm sending it Darryl> here. Should I Good choice. Darryl> submit a formal report (e.g., w/Installation, etc.), Darryl> even though this is documentation-related? ] Not for me. It should be independent of your installation, right? Bug reports are most useful to narrow in on a problem, but this problem seems to be obvious. Darryl> In man/lispref/packaging.texi, node names like the following exist: Darryl> The User's View Darryl> The Library Maintainer's View Darryl> Unfortunately, texinfo has the strange requirement that node names Darryl> cannot have apostrophes; from the texinfo manual: Darryl> * You cannot use commas or apostrophes within a node name; these Darryl> confuse TeX or the Info formatters. Good golly! What a GNUisance (sorry, I couldn't resist). Darryl> I also suspect that this limitation also applies to Darryl> chapter and section (etc.) names, as I'm getting TeX Darryl> errors when trying to format the lispref manual. Hmmh, that requirement is nowhere to be found in the texinfo manual. I'll take a look at this for 21.5 since it may fix some HTML manual breakage, as generated by texi2html. Best regards, Adrian Darryl> -- Darryl> Darryl Okahata Darryl> darrylo(a)soco.agilent.com Darryl> DISCLAIMER: this message is the author's personal opinion and does not Darryl> constitute the support, opinion, or policy of Agilent Technologies, or Darryl> of the little green men that have been following him all day. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

APPROVE COMMIT 21.5 RECOMMEND 21.4 Reviewers note Reply-To directed to xemacs-beta. Darryl> There's nothing in the manual regarding chapter and Darryl> section names, but the node name issue (no apostrophes) is Darryl> documented in the texinfo node, "Node Line Requirements". My bad. Fixed in CVS or use the following patch: Index: man/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v retrieving revision 1.155 diff -u -U0 -r1.155 ChangeLog --- man/ChangeLog 2002/02/16 07:25:39 1.155 +++ man/ChangeLog 2002/02/28 03:52:54 ＠＠ -0,0 +1,5 ＠＠ +2002-02-28 Stephen J. Turnbull <stephen(a)xemacs.org&gt; + + * lispref/packaging.texi (The User View, The Library Maintainer + View, The Package Release Engineer View): Remove apostrophes. + Index: man/lispref/packaging.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/packaging.texi,v retrieving revision 1.4 diff -u -r1.4 packaging.texi --- man/lispref/packaging.texi 2002/02/13 13:06:53 1.4 +++ man/lispref/packaging.texi 2002/02/28 03:53:00 ＠＠ -97,14 +97,14 ＠＠ ＠xpms{} provides to ensure that a package satisfies them. ＠menu -* The User's View:: -* The Library Maintainer's View:: -* The Package Release Engineer's View:: +* The User View:: +* The Library Maintainer View:: +* The Package Release Engineer View:: ＠end menu -＠node The User's View, The Library Maintainer's View, , Package Overview -＠section The User's View +＠node The User View, The Library Maintainer View, , Package Overview +＠section The User View ＠strong{N.B.} Much of the discussion in this section undoubtedly belongs elsewhere, ＠ref{Packages,,,xemacs}. ＠＠ -239,8 +239,8 ＠＠ receiving a ＠code{load-path} initialized to the core Lisp directories. -＠node The Library Maintainer's View, The Package Release Engineer's View, The User's View, Package Overview -＠section The Library Maintainer's View +＠node The Library Maintainer View, The Package Release Engineer View, The User View, Package Overview +＠section The Library Maintainer View From the library maintainer's viewpoint, the advantages to the ＠xpms{} stem from the convenience to the user of installation and upgrade. ＠＠ -272,7 +272,7 ＠＠ * Obtaining:: Obtaining the ＠xpms{} and required utilities. ＠end menu -＠node Infrastructure, Control Files, , The Library Maintainer's View +＠node Infrastructure, Control Files, , The Library Maintainer View ＠subsection Infrastructure In order to get the greatest benefit from the ＠xpms{}, a library ＠＠ -355,7 +355,7 ＠＠ package and are discussed in the next section, ＠ref{Control Files}. -＠node Control Files, Obtaining, Infrastructure, The Library Maintainer's View +＠node Control Files, Obtaining, Infrastructure, The Library Maintainer View ＠subsection Control Files Each package source must contain a number of control files in the ＠＠ -405,7 +405,7 ＠＠ ＠end table -＠node Obtaining, , Control Files, The Library Maintainer's View +＠node Obtaining, , Control Files, The Library Maintainer View ＠subsection Obtaining the ＠xpms{} and Required Utilities Currently both the infrastructure for creating XEmacs packages and the ＠＠ -417,8 +417,8 ＠＠ build packages. -＠node The Package Release Engineer's View, , The Library Maintainer's View, Package Overview -＠subsection The Package Release Engineer's View +＠node The Package Release Engineer View, , The Library Maintainer View, Package Overview +＠subsection The Package Release Engineer View The XEmacs Package Release Engineer is responsible for keeping the system coherent. The changes to ＠file{packages/package-compile.el} and -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.

Darryl> Anyway, I don't consider this to be a "must-fix" Darryl> problem, as I can just manually change "＠xpms" to the Darryl> correct expansion before running pdftex (ugly, but I can Darryl> live with this workaround). I just thought you'd like to Darryl> know, though. ;-) Thanks. I think the thing to do is have a macros.texi file. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp&gt; wrote: I can't tell from your post (and perhaps you already know this), but a macros.texi will only work if it's \input *BEFORE* texinfo.tex (which is currently on the very first line of lispref.texi). This is because it is texinfo.tex that processes the table of contents, where the macro is referenced. I don't remember if texinfo has any requirements that "\input texinfo.tex" be the very first line of a texinfo file. If "\input macros.texi" occurs before texinfo.tex, then this also means that you'd have to use TeX macros in macros.tex (and not texinfo macros), as texinfo.tex has obviously not yet been loaded. ;-( ;-( ;-( -- Darryl Okahata darrylo(a)soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day.