Re: Merging dev/texi2html [was: Re: Clean history]

[John Mandereau]

2008/8/19 Reinhold Kainhofer <address@hidden>:
> Am Dienstag, 19. August 2008 schrieb John Mandereau:
>> I'd like to
>> rename some files (add_html_footer.py -> postprocess_html.py,
>> doclang-*.make -> doc-i18n-user-*.make) and enable PDF generation fr
>> the IR and the Spanish bigpage LM, which will be easier for me if we
>> use texi2html on master.

Done in dev/texi2html.  Don't ask me to hack translated docs makefiles
and HTML postprocessing until dev/texi2html is merged into master.


> That's kind of a deadlock: We don't wan to merge before 1.79 is released on
> the one hand, while on the other hand, once 1.79 is released and we find
> problems in texi2html (which happened quite frequently, as the lilypond docs
> are pushing anything to its absolute limits ;-) ), we are stuck with them...

Texi2html people can do bugfix or pretest releases, can't they?


>> * make rules are forbidden in {fr,es,de}/*GNUmakefiles, only variables
>> specific to each language are allowed there;
>
> That was the only way I saw to force creation of the .xref-map files...
>
> I had
> local-WWW-1: $(MASTER_TEXI_FILES) $(PDF_FILES) $(XREF_MAP_FILES)
> in  make/doclang-targets.make and
> XREF_MAP_FILES := $(TELY_FILES:%.tely=$(outdir)/%.xref-map)
> in make/doclang-vars.make, but for whatever reason, the .xref-map files were
> not generated, so I had to hardcode them in the {fr,es,de}/user/GNUmakefile.

The variable definition with ":=" looks like the culprit.  If you have
this kind of prblems, it's a good idea to check which assignation type
to use --"=" or ":=" -- you can usually verify the variable you define
is non-empty by echoing it in whatever rule.


>> * IMHO symlinking .xref-map files is a bit messy, it's cleaner to
>> write them in a toplevel directory e.g.
>> XREF_MAPS_DIR=(top-build-dir)/out/xref-maps and add
>> --I=$(XREF_MAPS_DIR) to texi2html command line.
>
> Actually, this will not work, since the English, German, French and Spanish
> documentation all will have e.g. a file named lilypond.xref-map, each with
> its own translated node names... The only reason why symlinks are needed is
> that the snippets are completely out of the doc tree and the IR is available
> only in english and thus not in the languages' directories.

This works after I've hacked the init file a little (my first real
hack in Perl :-)


> BTW, looking at Documentation/user/GNUmakefile, I'm wondering why the
> lilypond-internals.texi rule uses --verbose. This prints about 2 pages of
> path information during the build...

I usually redirect "make ewb" output to a file, so I don't see the problem.


> Feel free to do anything you like with dev/texi2html

Done!

Cheers,
John