The attached patch lets me build xrefs by looking at
Documentation/*.tely
directly, instead of looking at the corresponding
Documentation/out-www/*.texi
files.
This would be very nice for the website, since we can't build all of
lilypond on the server. (the alternative is to generate the xrefs
locally, upload the .xref-map files, and hope that they don't change
very often... this isn't quite as terrible as it sounds at first,
since we need to do this for the examples and pictures anyway, but it
would still be nice to avoid this)
I tested it out, and it seems to work, but I don't particularly know
how xrefs work, so I thought I should ask if it's ok.
Cheers,
- Graham
From 1950c0500346b8a96658703880808a5cf4bbb789 Mon Sep 17 00:00:00 2001
From: Graham Percival <gra...@percival-music.ca>
Date: Sat, 26 Dec 2009 02:21:25 +0000
Subject: [PATCH] Doc build: allow xref-map creation from (i)tely.
This simplifies the special website target.
---
scripts/build/extract_texi_filenames.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/scripts/build/extract_texi_filenames.py b/scripts/build/extract_texi_filenames.py
index 5082df2..fda8fc1 100644
--- a/scripts/build/extract_texi_filenames.py
+++ b/scripts/build/extract_texi_filenames.py
@@ -86,7 +86,7 @@ if not os.path.isdir (outdir):
os.unlink (outdir)
os.makedirs (outdir)
-include_re = re.compile (r'@include ((?!../lily-).*?\.i?texi)$', re.M)
+include_re = re.compile (r'@include ((?!../lily-).*?\.i?te(xi|ly))$', re.M)
whitespaces = re.compile (r'\s+')
section_translation_re = re.compile ('^@(node|(?:unnumbered|appendix)\
(?:(?:sub){0,2}sec)?|top|chapter|(?:sub){0,2}section|\
--
1.6.0.4
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
