Updates:
Status: Verified
Comment #24 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Looks good, thanks.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
Updates:
Labels: fixed_2_13_50
Comment #23 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
h
Updates:
Status: Fixed
Comment #22 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
postprocess_html.py updated, patch pushed. Can't find any other references
to the old CSS files.
___
Updates:
Status: Accepted
Comment #21 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
Francisco Vila reported:
Still some references left to the old lilypond-mccarty.css file:
python/auxiliar/postprocess_h
Comment #20 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
The idea wasn't to do a complete merge; only to share any common features.
For example, do we really want a different style of hyperlinks between the
website and do
Comment #19 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
And, yes, merging lilypond-website.css with lilypond-manuals.css would be
difficult.
There's only so much we can do when we're using one texi2html init file...
The same HTM
Comment #18 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
IIRC, text-to-speech.css was an experimental CSS file from the web-gop
branch... We can delete this one.
Unless the CSS stylesheets are completely redone, the lilypond-ie-fix
Comment #17 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
I've had a quick look at the 2 primary CSS files we now have, and it won't
be possible to blindly merge same or similar styles - there is very little
in
Updates:
Status: Fixed
Labels: Patch-review
Comment #15 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
Patch emailed to Graham to fix this - we now just have 3 CSS files -
lilypond-manuals.css, lily
Updates:
Labels: -Patch-review
Comment #16 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
There's no patch to review, because I pushed the patch.
Technically, I'd say that this "topic" isn't finished yet -- it would be
Comment #14 on issue 1105 by Carl.D.Sorensen: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
One could also delete the alternate style sheets, and if anybody
complained, add them back.
___
bug-lilypond mailing list
Comment #13 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
lilypond-texi2htmlinit is the only way of generating html docs.
I see little benefit to having alternate style sheets, although you might
want to ask once on -user ju
Comment #12 on issue 1105 by PhilEHolmes: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
I had thought of searching all the html files for their stylesheet refs,
but it seemed quicker to ask in the first instance. If
lilypond-texi2html.init is the _only_ way
Comment #11 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Looks at lilypond-texi2html.init, and/or the source of the various web
pages. hint: if a .css file isn't included in any html file, then it's not
used.
_
Comment #10 on issue 1105 by PhilEHolmes: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
So, looking at the current stylesheets, we have:
lilypond-blue.css
lilypond.css
lilypond-ie-fixes.css
lilypond-mccarty.css
lilypond-web-alt1.css
lilypond-web-alt2.css
lilypond
Comment #9 on issue 1105 by v.villenave: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
No, what I should have said is "I hope that whatever you implement (add) in
the future to texi2html-init (or elsewhere) may make it easier for me to
implement a new alterna
Comment #8 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
err... are you asking if "you ALL may help me in doing so", or "has Graham
posted any information that might be helpful in me solving 860" ? I mean,
did you make a t
Comment #7 on issue 1105 by v.villenave: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Actually, I stumbled upon this while trying to address issue 860. Any
chance whatever you add may help me in doing so? :-)
___
Comment #6 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Well, the "trivial" first step to 2) is to have three files:
docs.css
web.css
both.css
Move any shared definitions into both.css. Move any definitions which only
Comment #5 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
I suppose lilypond-web.css is a copy of the previous lilypond-mccarty.css
stylesheet, right?
Unfortunately, no. This issue is challenging, especially because we are
using a
Comment #4 on issue 1105 by reinhold.kainhofer: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
I suppose lilypond-web.css is a copy of the previous lilypond-mccarty.css
stylesheet, right?
However, for non-web builds, it looks like there really is no stylesheet
Comment #3 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Valentin: your patch removes the default docs stylesheet
(lilypond-mccarty.css) too. :(
___
bug-lilypond mailing list
bug-lilypond
Updates:
Status: Accepted
Comment #2 on issue 1105 by v.villenave: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
Any news from William?
Attached is a patch that makes alternate stylesheets no longer available in
texi2html. We currently have two alterna
Updates:
Status: Started
Owner: tdanielsmusic
Comment #1 on issue 1105 by tdanielsmusic: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
William Bajzek is looking into this. I'll take ownership as his mentor.
Trevor
Status: Accepted
Owner:
Labels: Type-Other Priority-Low website Frog
New issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
We have a bunch of CSS files. AFAIK use two or three. Figure out what we
use and get rid of the rest. A
25 matches
Mail list logo
