Updates:
Status: Verified
Comment #4 on issue 872 by v.villenave: Changes split-page has broken images
http://code.google.com/p/lilypond/issues/detail?id=872
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this i
Updates:
Status: Fixed
Comment #3 on issue 872 by percival.music.ca: Changes split-page has broken
images
http://code.google.com/p/lilypond/issues/detail?id=872
Jan fixed this by fixing the typo in
a91dd4c245aa148bf003b28f2990b1e45d62dcc9.
--
You received this message because you
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 p
Updates:
Status: Invalid
Comment #1 on issue 872 by john.mandereau: Changes split-page has broken
images
http://code.google.com/p/lilypond/issues/detail?id=872
This bug is easily fixed in postprocess_html.py, but I don't see why you
want to
produce both a splitted and a non-splitted
Status: Accepted
Owner: percival.music.ca
Labels: Type-Other Priority-High
New issue 872 by percival.music.ca: Changes split-page has broken images
http://code.google.com/p/lilypond/issues/detail?id=872
after I moved Changes to be a split-page manual, the images are fine in the
one-big-page vers
