Hi Karl, * Karl Berry wrote on Sat, Mar 28, 2009 at 11:25:26PM CET: > * Unfortunately, you cannot use periods, commas, colons or > parentheses within a node name; these confuse the Texinfo > processors. Perhaps this limitation will be removed some day, too. > > Oh yeah :). > > Well, the situation is that in practice, periods only cause trouble in > unusual circumstances. Like a cross-manual reference to the node from > another manual? And even then it often works. To be honest, I don't > remember the exact problematic case(s).
Ah, ok. Thanks. > Colons, on the other hand, are definitely troublesome, even in regular > menus they can break. OK. I will leave both out, also for consistency: the Autoconf manual also has a "FOO vs BAR" node without a period in the node name. > | * Future Directions for Dependencies:: Languages Automake does not know > What is unusual about it? > > Just that "languages" and "dependencies" sound like quite different > things, even though they're not in this case, exactly. I think it's ok. Good. > Thanks, here you go. > > Nothing jumped out at me. What were the "close" introductory names you > were concerned about? `The Two Parts of Install' and `Two-Part Install'. Oh well, they do have the same topic, and the latter even links to the former. > All I noticed were several that need capitalization fixes: > > * Length limitations:: Staying below the command line length limit > * Macro search path:: How aclocal finds .m4 files > * Public macros:: Macros that you can use. > * Obsolete macros:: Macros that you should stop using. > * Private macros:: Macros that you should not use. > * Program variables:: Variables used when building a program > * Built sources example:: Several ways to handle built sources. > > Maybe something like grep '^...@node .* [a-z]' would help for a quick > check. (It'll get false matches too, but anyway.) OK thanks, I will fix them before I push. Thanks again! Ralf