>I still don't plan to do that. There are other nodes in the >documentation that don't make sense without the dot. > >~ace/doc % grep '^@node.*\.' autoconf.texi >@node Writing configure.ac >@node configure.ac Layout >@node config.status Invocation >@node Obsolete config.status Use >@node acconfig.h >@node Autoconf 2.13 >@node AC_LIBOBJ vs. LIBOBJS >@node Writing testsuite.at
Yes, but all the others have the dot in the middle of a word and work fine (although still violate the rule that you should not put a '.' in node names). I don't mean to harp on this, but is it too much to change this one instance so that the documentation actually works? It seems to me to be poor software engineering practice to deliberately violate a documented exclusion (not using '.' in node names) because it happens to work in one implementation. But that's all I'll say on the matter. I'll leave the question of whether you are prepared to ship stuff in a known broken state to you. -- Dean Povey, |em: [EMAIL PROTECTED] | JCSI: Java security toolkit Senior S/W Developer |ph: +61 7 3023 5139 | uPKI: Embedded/C PKI toolkit Wedgetail Communications |fax: +61 7 3864 1282 | uSSL: Embedded/C SSL toolkit Brisbane, Australia |www: www.wedgetail.com | XML Security: XML Signatures _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
