Anybody feel like seeing a joke? Apply the attached patch and
make doc.
Does anybody have any clue why "texi2html --split=foo" results in
*nothing* being stored in $Texi2HTML::Config::SPLIT ? I'm quite
baffled. I'm even more baffled as to why it seems to work with
the other manuals, but not general.texi.
The attached patch doesn't completely fix the filenames; I still
need to remove the "don't split unnumbered nodes" stuff (since
everything in general.texi is unnumbered, but we want to split
everywhere... I wish we could just say --split=node, but
apparently that breaks the translation stuff.
Actually, maybe it would be easier to fix the translation stuff,
rather than redefining "--split=section" to mean
"--split=node --node-files".
Cheers,
- Graham
diff --git a/Documentation/web-texi2html.init b/Documentation/web-texi2html.init
index 2bc6275..45d6c73 100644
--- a/Documentation/web-texi2html.init
+++ b/Documentation/web-texi2html.init
@@ -124,9 +124,20 @@ $Texi2HTML::Config::SEPARATED_FOOTNOTES = 0; # Print footnotes on same page, not
# FIXME: creates duplicate anchors, which causes Opera to barf;
# should be fixed in lilypond-texi2html.init too
# Uhm, what about a bug report to Opera? We need sane names here.
-if ($Texi2HTML::Config::SPLIT eq 'section') {
+
+# FIXME: see the print
+print "*********** WHAT THE BLOODY MAO?!?! *****\n";
+print "the command contains --split=section. Don't take\n";
+print "my word for it; look at the maoing line above this in\n";
+print "the build log.\n";
+print "But now, look at \$Texi2HTML::Config::SPLIT:\n";
+print "$Texi2HTML::Config::SPLIT\n";
+print "... nothing?! It's magic!\n";
+print "What the mao? (using 1.82)\n";
+print "*********** (bloody mao end) *****\n";
+#if ($Texi2HTML::Config::SPLIT eq 'section') {
$Texi2HTML::Config::element_file_name = \&lilypond_element_file_name;
-}
+#}
$Texi2HTML::Config::element_target_name = \&lilypond_element_target_name;
$default_print_element_header = $Texi2HTML::Config::print_element_header;
$Texi2HTML::Config::print_element_header = \&lilypond_print_element_header;
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
