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

[codesite-noreply]

Comment #2 on issue 872 by percival.music.ca: Changes split-page has broken  
images
http://code.google.com/p/lilypond/issues/detail?id=872

We don't *have* to discuss it as a tracker issue, but I'm finding it  
alarmingly easy
for me to forget things these days.  I suppose I could keep my own personal  
lilypond
TODO list, but I figured I might as well use the tracker.  Also, this way  
all the
other developers could see that I already knew about the problem.

Maybe those aren't good reasons... I have no objection to keeping such TODO  
items to
myself in the future, if that's desired.


Anyway, for this specific issue: if changes.tely is a non-splitted manual,  
then the
html page from general/manual.itexi @section Changes  will overwrite the  
non-splitted
version of changes.itely.  I figured that the simplest way to fix this  
would be to
make Changes a split manual, thereby putting changes-one-page.html in the  
main doc
source output, and also giving us changes/index.html.

There was also an issue with the xref produced by @rchanges{Top,blah}  
inside general,
that has to do with the broken html refs that I'm avoiding with that  
disgusting find
| xargs sed trick.

In general (umm, I mean, "as a summary", not anything to do with  
general.texi), I'd
like to avoid manual-specific hacks; I like the idea of only having two  
types of
manuals: general.texi, which goes in the top output dir, and all the other  
manuals,
which are all treated the same.


Long-term, I think it would be nice to have the older Changes in the same  
document,
but I haven't thought through all the issues involved in doing this.    
(namely, what
happens if the syntax changes from 1.4 to 1.8, then again from 1.8 to 2.13  
-- how do
we generate the picture for the changes-1.8 page?)
Now that I think about it some more, I'm leaning towards abandoning the  
idea entirely.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings