My comment for issue 1004 (opened for this patch):
As release manager, I feel that I should reject the patches I'm
writing because they are, as "weegies" (people from Glasgow) would
put it, "utter pish". However, as overall manager, I want to let
doc writers and translators work on the website and see how it
really looks.
Given my doc roots, the doc side wins, so I'm hacking stuff. But
only with the promise that this item is High priority, and that
I'll work on it as soon as I've finished all Critical items. It
*will* be fixed before GLISS starts. GOP might start first, if
everything else is already in place.
if (defined $file) {
$href = &$default_external_href($node, $node_id, $node_hxmlt_id, lc($file));
remove_unneeded_anchor($href);
+
+ # TODO: very yucky, but will be fixed in issue 1004
+ if ($web_manual) {
+ my $only_web = $ENV{ONLY_WEB};
+ if ($only_web) {
+ $href = "../../doc/v2.13/Documentation/web/".$href;
+ }
+ }
+
return $href;
} else {
$href = &$default_external_href($node, $node_id, $node_hxmlt_id);
################################################################
OUT=out-website
-TEXI2HTML=TOP_SRC_DIR=$(top-src-dir) DEPTH=$(depth) PERL_UNICODE=SD $(TEXI2HTML_PROGRAM)
+TEXI2HTML=ONLY_WEB=1 TOP_SRC_DIR=$(top-src-dir) DEPTH=$(depth) PERL_UNICODE=SD $(TEXI2HTML_PROGRAM)
EXTRACT_TEXI_FILENAMES=python $(script-dir)/extract_texi_filenames.py
CREATE_VERSION=python $(script-dir)/create-version-itexi.py