Hello,
three patches: modified convert-ly, the defaults for dashed/dotted
slurs, and the doc. (Created against HEAD)
Bert
? slur-dash-patch2
Index: Documentation/user/notation.itely
===
RCS file: /cvsroot/lilypond/lilypond/Documentat
Thanks. I'm very happy :-)
However, the best default for \slurDashed will be something else
(smaller period, like 0.8). I'll have to create some test to find the best.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mail
Han-Wen Nienhuys writes:
> Can someone tell me when I should release another 2.4 - eg. for cygwin
> or tetex-3?
Cygwin can be packaged from CVS, maybe better to use that to hammer
out the final tetex-3 problems?
Alternatively, if you feel like release early, release often, now
might be a good ti
[EMAIL PROTECTED] writes:
> > I've attached a sample image: the new output of (the new)
> > input/slur-dash.ly
> > True that it's too simplistic, but better than it was.
>
> It looks fine. I've applied it to 2.4, although it is probably more
> of a new feature than a bugfix. Maybe that was a sil
[EMAIL PROTECTED] writes:
> I've created the patches for the 2.4 branch. What do you say?
applied to 2.5
> Should convert-ly also be modified?
Yes please!
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilyp
Bertalan Fodor writes:
> I've created the patches for the 2.4 branch. What do you say?
> Should convert-ly also be modified?
If you can, it should. Otherwise check for #'dashed and raise an error.
> I've attached a sample image: the new output of (the new)
> input/slur-dash.ly
> True that it's
I've created the patches for the 2.4 branch. What do you say?
Should convert-ly also be modified?
I've attached a sample image: the new output of (the new)
input/slur-dash.ly
True that it's too simplistic, but better than it was.
Bert
Index: input/test/slur-dash.ly
===
[EMAIL PROTECTED] writes:
> OK, I've tried and succeeded. Now I have dash-fraction and dash-period
> working for dashed slurs. Should my patches be created for the latest
> CVS? That would be problematic for me, because I've developed for my
> working 2.4.2 version. Or could I send patches for 2
OK, I've tried and succeeded. Now I have dash-fraction and dash-period
working for dashed slurs. Should my patches be created for the latest
CVS? That would be problematic for me, because I've developed for my
working 2.4.2 version. Or could I send patches for 2.4.2 CVS and you
merge them into
However, for dashed/dotted slurs to be really nice, the current
builtin postscript dashing is too simplistic.
Yes, you're right. But it is better to have a not perfect but tweakable
feature, than to not have a perfect. :-)
What is it exactly that you need to know. What do you miss when
looki
Bertalan Fodor writes:
> I've found that dashed slurs are quite ugly. That's because
> output-ps.scm sets the dash length to the property Slur.dashed, but
> the gap between dashes is set to 10*slur.thickness, that is not
> good. I've found that changing output.scm's
> So it is obvious there shoul
Hello, I wanted to contribute a patch for nicer slurs, but I don't
really know how to do it.
I've found that dashed slurs are quite ugly. That's because
output-ps.scm sets the dash length to the property Slur.dashed, but the
gap between dashes is set to 10*slur.thickness, that is not good. I've
12 matches
Mail list logo
