hyphenation

2018-02-09 Thread Richard Stallman
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

Please insert   @hyphenation{auto-ma-ti-cal-ly}
in texinfo.tex.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.




Misleading Warning about Node Names

2018-02-09 Thread Rical Jasan
Hi,

In the glibc manual, we have some @*refs to the GCC manual; e.g.:

@xref{Debugging Options,, Options for Debugging Your Program or GCC,
gcc.info, Using GCC}

When running `make info', there are the following warnings:

./creature.texi:11: warning: @xref node name should not contain `.'
./string.texi:1089: warning: @xref node name should not contain `.'
./stdio.texi:1810: warning: @xref node name should not contain `.'
./stdio.texi:2732: warning: @xref node name should not contain `.'
./stdio.texi:3480: warning: @xref node name should not contain `.'
./stdio.texi:4035: warning: @ref node name should not contain `.'

The warnings are not present when running `make html'.

In all of these cases, it seems to be due to the "." in the
info-file-name argument and not the node-name argument (they all have
"gcc.info" and changing it to "gcc" makes the warnings go away).

It seems that makeinfo is reporting the wrong argument as having bad syntax.

I also noticed while addressing this that in PDF output, the link
changed from "gcc.info.pdf" to "gcc.pdf", so it also seems that the
info-file-name argument is used for more than just info files.

Thank you,
Rical

[0]
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Cross-Reference-Parts.html