>> I second that. IMHO it's a very bad idea that we have to limit >> correct use of English due to restrictions in a program (which are in >> this case even non-existent)! > > I thought this was going to be a new feature of the next version > of texinfo.
Commas in section names? No, this was always possible. Commas in node names are still forbidden. > (do you have any clue when this will be? AFAIK the latest version > is 4.13a from 2008) Don't expect a release soon. It's still not really compatible to the good old makeinfo binary (and additionally at least 20 times slower). In particular, it's not possible yet to build lilypond's documentation with the CVS version of the makeinfo replacement, AFAIK. Do you want to try? It's probably worth to report all bugs to the texinfo people. >> What I can imagine is that node names get automatically derived >> from section names. For example, a script might check that, >> stripping off all texinfo commands and other forbidden characters >> like the comma. > > sure, we already have > scripts/auxiliar/node-menuify.py > that could be expanded to handle this. Aah, an almost completely undocumented script, lacking any source comments also :-) Werner _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel