Comment #7 on issue 569 by frederic...@m4x.org: Consistency in property
names: beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Sorry for that. As soon as the tests passed I though it was OK. Can you
give me some
directions on where are the files I have to change? Then
Comment #6 on issue 569 by n.puttock: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Frédéric, the convert rule is for the wrong version (2.13.1). I've moved
it to the
end of the rules for 2.13.4 and added a description.
There are sti
Updates:
Status: Fixed
Labels: fixed_2_13_4
Comment #5 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Oops -- sorry for doing it wrong. I think it's right now
--
You received this message
Updates:
Status: fixed_2_13_4
Comment #4 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Thanks to Frederic for his work!
--
You received this message because you are listed in the owner
or CC field
Dear developers,
as I quite often engrave Rock Riffs I discovered that it is
comparatively complicated to typeset chord slides (using hidden
voices and spacer notes). From my point of view it would be more
intuitive if it were possible to set glissandi in chords just the way
ties are set,
Dear developers,
thank you all for Lilypond! I'm very fond of it.
While trying to engrave a piece with polyphonic elements both
"traditionally" (with noteheads) and with tablature I found out that
it is not possible to get the tablature right with the following code:
\version "2.13.3"
poly
2009/8/12 Ian Hulin :
> There's a restriction with the gs back-end. Marek asked abourt this and
> Han-Wen confirmed that's why we're restricted to ujsing the ASCII set for
> filenames. So we'll have to stick to work-rounds like "Floete" and
> "Hoerner" in the suffix names.
Could this be related t
Status: Accepted
Owner: v.villenave
Labels: Type-Task Maintainability
New issue 830 by v.villenave: Task: rename feta filenames in English
http://code.google.com/p/lilypond/issues/detail?id=830
Mark Polesky has suggested that the following filenames should be
translated:
feta-eindelij
Updates:
Status: Invalid
Comment #1 on issue 829 by v.villenave: split Metafont output into smaller
units
http://code.google.com/p/lilypond/issues/detail?id=829
Invalid as requested by Werner:
http://lists.gnu.org/archive/html/lilypond-devel/2009-08/msg00599.html
--
You received this
