3:15 p.m.
Latest CVS snapshot of Xemacs-21.4 (windows-21-4).
failed to create lispref.info files with makeinfo v.4.0 (from cygwin
distribution).
NMAKE log:
cd c:\software\SRC\xemacs-21.4\nt\..\man\lispref
c:\software\cygwin\bin\makeinfo.exe lispref.texi
' in ＠synindex.: Unknown index `cp' and/or `fn
' in ＠synindex.: Unknown index `vr' and/or `fn
' in ＠synindex.: Unknown index `ky' and/or `fn
' in ＠synindex.: Unknown index `pg' and/or `fn
' in ＠synindex.: Unknown index `tp' and/or `fn
./glyphs.texi:1431: warning: `.' or `,' must follow cross reference, not f.
Extents'.exi:1547: Cross reference to nonexistent node `Mapping Over
Specifiers'.:62: Cross reference to nonexistent node `Image
makeinfo: Removing output file `../../info/lispref.info' due to errors; use --force to
preserve.
NMAKE : fatal error U1077: 'c:\software\cygwin\bin\makeinfo.exe' : return code
'0x2'
Stop.
-------------------------------------------------------------------------------
XEmacs Build Report generated by emacs-version
21.4 (patch 6) "Common Lisp (Windows)" XEmacs Lucid
with system-configuration
i586-pc-win32
follows:
Contents of c:\software\SRC\xemacs-21.4\Installation:
(Output from most recent run of ./configure)
OS version:
Microsoft Windows 2000 [Version 5.00.2195]
OS: Windows_NT
XEmacs 21.4.6 \"Common Lisp (Windows)\" configured for `i586-pc-win32'.
Building XEmacs in \"c:\\software\\SRC\\xemacs-21.4\\nt\".
Using compiler \"cl -nologo -W3 -Od -Zi -ML\".
Installing XEmacs in \"c:\\Program Files\\XEmacs\\XEmacs-21.4.6\".
Package path is \"~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program
Files\\XEmacs\\xemacs-packages\".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Compiling in extra debug checks. XEmacs will be slow!
c:\software\SRC\xemacs-21.4\nt\xemacs-make-install.err not found!
c:\software\SRC\xemacs-21.4\nt\xemacs-make-check.err not found!
c:\software\SRC\xemacs-21.4\nt\xemacs-make-check-temacs.err not found!
c:\software\SRC\xemacs-21.4\nt\xemacs-make-all.err not found!
c:\software\SRC\xemacs-21.4\nt\beta.err not found!
5:01 p.m.
>>>> "Nick" == Nick V Pakoulin
<npak(a)ispras.ru> writes:
Nick> Latest CVS snapshot of Xemacs-21.4 (windows-21-4). failed
Nick> to create lispref.info files with makeinfo v.4.0 (from
Nick> cygwin distribution).
Thanks for the report.
The warning at glyphs.texi:1431 is genuine, and is now fixed in my
workspace. The others are Cygwin bogosity, I would guess. Apparently
Cygwin's makeinfo doesn't consider ASCII 13 whitespace in macro
arguments. Note the funky way all the allegedly erroneous text wraps
to the beginning of the same line. You could try reformatting those
lines so that line breaks don't occur in a ＠ref argument and with
extra whitespace padding the ends of the synindes lines.
------------------------------------------------------------------------
NMAKE log:
cd c:\software\SRC\xemacs-21.4\nt\..\man\lispref
c:\software\cygwin\bin\makeinfo.exe lispref.texi
' in ＠synindex.: Unknown index `cp' and/or `fn
' in ＠synindex.: Unknown index `vr' and/or `fn
' in ＠synindex.: Unknown index `ky' and/or `fn
' in ＠synindex.: Unknown index `pg' and/or `fn
' in ＠synindex.: Unknown index `tp' and/or `fn
./glyphs.texi:1431: warning: `.' or `,' must follow cross reference, not f.
Extents'.exi:1547: Cross reference to nonexistent node `Mapping Over
Specifiers'.:62: Cross reference to nonexistent node `Image
------------------------------------------------------------------------
--
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.
6:30 p.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>> "Nick" == Nick V Pakoulin
<npak(a)ispras.ru> writes:
Nick> Latest CVS snapshot of Xemacs-21.4
(windows-21-4). failed
Nick> to create lispref.info files with makeinfo v.4.0 (from
Nick> cygwin distribution).
Stephen> Thanks for the report.
Stephen> The warning at glyphs.texi:1431 is genuine, and is now
Stephen> fixed in my workspace. The others are Cygwin bogosity, I
Hi Stephen,
I looked into this too (in r21-4-6rc1 though) and this is what I came
up with:
man/ChangeLog addition:
2001-11-27 Adrian Aichner <adrian(a)xemacs.org>
* lispref\glyphs.texi (Glyph Examples): Use ref instead of xref.
xemacs-21.4 Patch (cvs -f -z3 -q diff -u man/lispref/glyphs.texi):
Index: man/lispref/glyphs.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/glyphs.texi,v
retrieving revision 1.3.14.1
diff -u -r1.3.14.1 glyphs.texi
--- man/lispref/glyphs.texi 2001/11/21 07:56:50 1.3.14.1
+++ man/lispref/glyphs.texi 2001/11/27 16:25:49
＠＠ -1428,8 +1428,8 ＠＠
To programmatically query whether or not a particular file format is
supported, you can use the ＠code{featurep} function, with one of:
＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm}, ＠code{xbm},
-＠code{png}, or ＠code{xface}. ＠xref{Image Specifiers} for an up-to-date
-list. Example:
+＠code{png}, or ＠code{xface}. For an up-to-date list see ＠ref{Image
+Specifiers}. Example:
＠example
;; Returns `t' if TIFF is supported:
Does it look like the right fix?
Best regards,
Adrian
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
7:06 p.m.
[ xemacs-buildreports deleted from the cc: list. ]
Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
To programmatically query whether or not a particular file format
is
supported, you can use the ＠code{featurep} function, with one of:
＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm}, ＠code{xbm},
-＠code{png}, or ＠code{xface}. ＠xref{Image Specifiers} for an up-to-date
-list. Example:
+＠code{png}, or ＠code{xface}. For an up-to-date list see ＠ref{Image
+Specifiers}. Example:
＠example
;; Returns `t' if TIFF is supported:
Does it look like the right fix?
If I'm reading the texinfo docs correctly, I think the right fix is
to keep everything the same, except add a comma after the ＠xref closing
brace ("}"), like:
＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm}, ＠code{xbm},
＠code{png}, or ＠code{xface}. ＠xref{Image Specifiers}, for an up-to-date
list. Example:
(I think I need to update my copy of texinfo; makeinfo didn't complain
about the missing comma.)
--
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.
7:15 p.m.
>>>> "Darryl" == Darryl Okahata
<darrylo(a)soco.agilent.com> writes:
Darryl> [ xemacs-buildreports deleted from the cc: list. ]
Darryl> Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
> To programmatically query whether or not a particular file format
is
> supported, you can use the ＠code{featurep} function, with one of:
> ＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm}, ＠code{xbm},
> -＠code{png}, or ＠code{xface}. ＠xref{Image Specifiers} for an up-to-date
> -list. Example:
> +＠code{png}, or ＠code{xface}. For an up-to-date list see ＠ref{Image
> +Specifiers}. Example:
>
> ＠example
> ;; Returns `t' if TIFF is supported:
>
> Does it look like the right fix?
Darryl> If I'm reading the texinfo docs correctly, I think
Darryl> the right fix is
Darryl> to keep everything the same, except add a comma after the
Darryl> ＠xref closing brace ("}"), like:
Does the comma belong there, according to grammar rules?
Gotta find my "Elements of Style" again.
Best regards,
Adrian
Darryl> ＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm},
Darryl> ＠code{xbm}, ＠code{png}, or ＠code{xface}. ＠xref{Image
Darryl> Specifiers}, for an up-to-date list. Example:
Darryl> (I think I need to update my copy of texinfo; makeinfo
Darryl> didn't complain about the missing comma.)
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/
7:25 p.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
Darryl> If I'm reading the texinfo docs correctly, I
think
Darryl> the right fix is
Darryl> to keep everything the same, except add a comma after the
Darryl> ＠xref closing brace ("}"), like:
Does the comma belong there, according to grammar rules?
The comma belongs there according to texinfo rules ;-). From the
texinfo manual:
*Please note:* A period or comma *must* follow the closing brace
of an `＠xref'. It is required to terminate the cross reference.
This period or comma will appear in the output, both in the Info
file and in the printed manual.
--
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.
9:05 p.m.
>>>> "Darryl" == Darryl Okahata
<darrylo(a)soco.agilent.com> writes:
Darryl> Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
Darryl> If I'm reading the texinfo docs correctly, I think
Darryl> the right fix is
Darryl> to keep everything the same, except add a comma after the
Darryl> ＠xref closing brace ("}"), like:
>
> Does the comma belong there, according to grammar rules?
Darryl> The comma belongs there according to texinfo rules
Darryl> ;-). From the
Darryl> texinfo manual:
Darryl> *Please note:* A period or comma *must* follow the
Darryl> closing brace of an `＠xref'. It is required to
Darryl> terminate the cross reference. This period or comma
Darryl> will appear in the output, both in the Info file and
Darryl> in the printed manual.
Yep, I have read that when I was trying to fix the problem earlier.
The real question is whether the resulting document is what you want.
I haven't found the correct use of references starting with "See
... bla bla." in my "Element of Style".
Either way, we have two options now to fix the problem.
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/
10:13 p.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
The real question is whether the resulting document is what you want.
It should be. The info version looks like:
===============================================================================
To programmatically query whether or not a particular file format
is supported, you can use the `featurep' function, with one of:
`gif', `tiff', `jpeg', `xpm', `xbm', `png', or `xface'.
*Note
Image Specifiers::, for an up-to-date list. Example:
===============================================================================
The formatted version looks even better (see attached gif).
--
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.
10:25 p.m.
>>>> "Darryl" == Darryl Okahata
<darrylo(a)soco.agilent.com> writes:
Darryl> Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
> The real question is whether the resulting document is what you
want.
Darryl> It should be. The info version looks like:
Darryl>
===============================================================================
Darryl> To programmatically query whether or not a particular file format
Darryl> is supported, you can use the `featurep' function, with one of:
Darryl> `gif', `tiff', `jpeg', `xpm', `xbm', `png', or
`xface'. *Note
Darryl> Image Specifiers::, for an up-to-date list. Example:
Darryl>
===============================================================================
I don't think
"*Note Image Specifiers::, for an up-to-date list."
complete sentence nor proper punctuation :-)
But it's probably not worth spending more time on this.
Darryl> The formatted version looks even better (see attached gif).
That looks nice, yes.
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/
11:30 p.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) wrote:
I don't think
"*Note Image Specifiers::, for an up-to-date list."
complete sentence nor proper punctuation :-)
Well, phrases like that are rampant in virtually all *.info
documentation. I don't like it either (;-), but that's what the texinfo
folks did. It's not very good English, but it's passable.
But it's probably not worth spending more time on this.
Yes. You'd have to change virtually every manual if you wanted to
change that.
--
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.
8396
days inactive
8396
days old
9 comments
4 participants
participants (4)
-
Adrian Aichner -
Darryl Okahata -
Nickolay Pakoulin -
Stephen J. Turnbull