Re: Issue 872 in lilypond: Changes split-page has broken images

[Graham Percival]

On Wed, Nov 04, 2009 at 12:10:55PM +0100, Jan Nieuwenhuizen wrote:
> Op woensdag 04-11-2009 om 10:19 uur [tijdzone +0100], schreef John
> Mandereau:
> > Agreed, but who wants to hack Texi2HTML init files and/or
> > postprocess_html.py?  I mean, we have so many other problems that we
> > probably don't want to hack this right now.
> 
> I don't think so, as texinfo wants names to be normalized.  We can
> simply lowercase our short/file name entries in node menus that
> we use in general.*, I think.  See attached

It seems to work.  I had to change all the @ref{} in the text, but
it looks fine now.

> > Because "general" won't show up in the website (splitted HTML output),
> > and it's perfectly accurate for offline docs IMO; for PDF and
> > one-big-page output, well, Graham and me are probably tired by renaming
> > directories :-)
> 
> Yeah, laugh.  That's the reason why hardcoding names all over
> the place is so bad.

Totally agreed.  But right now, let's just say that making the
build system was a learning experience for everybody involved.
(I don't know who started hard-coding dir names, and I don't care)

> Renaming a directory should be a simple
> mv and M-x tags-search-replace.

NB: a simple replace **in the same directory**, no less.  Not some
kind of ../stepmake/stepmake/texinfo-targets.make or
../doc-i8n3d-targets.maek

> I'd rather rename directories once, in the source ball, than
> on the website.  We'll be stuck with /general fixups for
> eons to come.

Agreed -- but there's no /general dir in the output.
Documentation/GNUmakefile has:
  TOPDIR_MANUAL = general
which produces:
  Documentation/out-www/index.html
all other manuals produce:
  Documentation/out-www/manual-big-page.html
  Documentation/out-www/manual/index.html

it also creates
  lilypond-general.pdf
  lilypond-general.info
  lilypond-{manual}.pdf
  lilypond-{manual}.info
where {manual} are all the other manuals.  There's also a
special lilypond.info which goes directly to the command-line
options in lilypond-usage.info.


I'm open to renaming "general.tely", but nobody could think of a
better name last June or July when we were contemplating such a
change.  Note again that "general" does not appear in any html
URLs.

Cheers,
- Graham