Hi Zoltan,
as far as I can see you are not missing anything.
It seems there is still work to be done to optimise the automatic
Dynamics placement between staves, see
http://code.google.com/p/lilypond/issues/detail?id=1127
From my experience it works quite well most of the times, you seem to
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1329 by lilyli...@googlemail.com: \afterGrace placement/behaviour
to be discussed
http://code.google.com/p/lilypond/issues/detail?id=1329
Original report by Dmytro O. Redchuk:
-
H
Hi Dmytro,
while I think the behaviour is (nearly) consistent with the
documentation I think it should be discussed.
Opened and commented as
http://code.google.com/p/lilypond/issues/detail?id=1329
Am 11.10.2010 14:02, schrieb Dmytro O. Redchuk:
Hi.
Playing with \afterGrace (rather simply "ty
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1330 by lilyli...@googlemail.com: adapt the \skip command to
automatically-aligned lyrics mode
http://code.google.com/p/lilypond/issues/detail?id=1330
NR 2.1.2 states that
"The \skip command must be followed by a num
Added as http://code.google.com/p/lilypond/issues/detail?id=1330
Best
Urs
Am 13.10.2010 16:58, schrieb Valentin Villenave:
NR 2.1.2 states that
"The \skip command must be followed by a number,
but this number is ignored in lyrics which derive their durations
from the notes in an associated melody
Comment #1 on issue 1329 by lilyli...@googlemail.com: \afterGrace
placement/behaviour to be discussed
http://code.google.com/p/lilypond/issues/detail?id=1329
AFAICS The behaviour is consistent with the documentation
(http://lilypond.org/doc/v2.13/Documentation/notation/special-rhythmic-conc
On Fri, Oct 15, 2010 at 10:06 AM, Urs Liska wrote:
> Added as http://code.google.com/p/lilypond/issues/detail?id=1330
Thanks!
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #4 on issue 376 by pkx1...@hotmail.com: tremolo beams can collide
with notes
http://code.google.com/p/lilypond/issues/detail?id=376
See attached - using 2.13.35
It seems to have moved that staff space lower.
Attachments:
Capture.PNG 3.9 KB
wrote in message
news:4-9567054385019064696-10086053899522727529-lilypond=googlecode@googlecode.com...
Comment #4 on issue 376 by pkx1...@hotmail.com: tremolo beams can collide
with notes
http://code.google.com/p/lilypond/issues/detail?id=376
See attached - using 2.13.35
It seems to hav
Sorry, I made a mistake and deleted the comment I made but too late.
James
On 15/10/2010 18:14, Phil Holmes wrote:
wrote in message
news:4-9567054385019064696-10086053899522727529-lilypond=googlecode@googlecode.com...
Comment #4 on issue 376 by pkx1...@hotmail.com: tremolo beams can
co
Updates:
Status: Verified
Labels: fixed_2_13_12
Comment #7 on issue 852 by v.villenave: stop google from indexing old docs
http://code.google.com/p/lilypond/issues/detail?id=852
I can confirm that old docs are no longer indexed: for instance, try the
following query string:
ht
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
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: Verified
Owner: ---
Comment #4 on issue 450 by v.villenave:
input/regression/tuplet-properties.ly
http://code.google.com/p/lilypond/issues/detail?id=450
Current output (version 2.13.36) looks perfectly acceptable to me. Closing.
Attachments:
tuplet-pr
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 #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 #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 #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 #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 #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 852 by markpolesky: stop google from indexing old docs
http://code.google.com/p/lilypond/issues/detail?id=852
v.villenave wrote:
I can confirm that old docs are no longer indexed:
for instance, try the following query string:
http://www.google.fr/search?q=tupletdown+site:lil
21 matches
Mail list logo
