From the tutorial example showing the key signature, accidentals and
ties in action:
\score {
\notes {
\time 4/4
\key g \minor
\clef violin
r4 r8 a8 gis4 b
g8 d4.~ d e'8
fis4 fis8 fis8 eis4 a8 gis~
gis2 r2
}
\paper { }
}
The result from debian package lilypond-2.1.0-2
Status: Accepted
Owner: jameseli...@googlemail.com
Labels: Priority-Regression
New issue 890 by jameseli...@googlemail.com: Chords and Lyrics under 2.13.6
http://code.google.com/p/lilypond/issues/detail?id=890
Chords and lyrics don't mix well in 2.13.6
\paper { indent = 0\mm }
\version 2.13.6
Comment #1 on issue 890 by jameseli...@googlemail.com: Chords and Lyrics
under 2.13.6
http://code.google.com/p/lilypond/issues/detail?id=890
(No comment was entered for this change.)
Attachments:
chords and lyrics.png 12.8 KB
--
You received this message because you are listed
Updates:
Summary: Chord names collide with staff on second system when lyrics are
present
Labels: Type-Collision
Comment #2 on issue 890 by Carl.D.Sorensen: Chord names collide with staff
on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id
Comment #3 on issue 890 by jameseli...@googlemail.com: Chord names collide
with staff on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
No worries. Also, on some music that I have, with multiple verses and
different kinds
of chords, I don't get
Comment #4 on issue 890 by jameseli...@googlemail.com: Chord names collide
with staff on second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
No worries. Also, on some music that I have, with multiple verses and
different kinds
of chords, I don't get
Status: New
Owner: percival.music.ca
Labels: Type-Review Priority-Medium
New issue 891 by percival.music.ca: test of review request, ignore
http://code.google.com/p/lilypond/issues/detail?id=891
This is a test of the review request thingie.
--
You received this message because you
Updates:
Status: Invalid
Comment #1 on issue 891 by percival.music.ca: test of review request, ignore
http://code.google.com/p/lilypond/issues/detail?id=891
Nope, we don't want do use this.
--
You received this message because you are listed in the owner
or CC fields of this issue
Status: Accepted
Owner: neziap
CC: xmichae...@web.de
Labels: Type-Enhancement
New issue 892 by neziap: Request for Patch review: Twoside mode
http://code.google.com/p/lilypond/issues/detail?id=892
Original Message (Michael Käpler):
http://lists.gnu.org/archive/html/lilypond-devel/2009-10
Updates:
Summary: Patch: Twoside mode (different margins on odd and even pages)
Status: Started
Labels: Patch
Comment #1 on issue 892 by v.villenave: Patch: Twoside mode (different
margins on odd and even pages)
http://code.google.com/p/lilypond/issues/detail?id=892
Comment #2 on issue 892 by percival.music.ca: Patch: Twoside mode
(different margins on odd and even pages)
http://code.google.com/p/lilypond/issues/detail?id=892
Looks good. It's been a few days, and nobody made any replies about the
code, so
it's definitely a good time to add
Comment #3 on issue 892 by n.puttock: Patch: Twoside mode (different
margins on odd and even pages)
http://code.google.com/p/lilypond/issues/detail?id=892
The replies are here:
http://lists.gnu.org/archive/html/lilypond-devel/2009-10/msg00305.html
If comments are made on Rietveld, a new
Comment #4 on issue 892 by gpermus: Patch: Twoside mode (different margins
on odd and even pages)
http://code.google.com/p/lilypond/issues/detail?id=892
Oops, sorry. I think that as long as we know that Rietveld makes a new
thread, it
should be fine.
--
You received this message because
Status: Accepted
Owner: jameseli...@googlemail.com
Labels: Priority-Regression Type-Defect
New issue 893 by jameseli...@googlemail.com: rehearsal marks
http://code.google.com/p/lilypond/issues/detail?id=893
Rehearsal Marks should be placed below the system, not the first
staff:
\version 2.13.4
Comment #1 on issue 893 by jameseli...@googlemail.com: rehearsal marks
http://code.google.com/p/lilypond/issues/detail?id=893
Note, there is a workaround here: and a caveat for using the workaround
later in the
thread, here:
http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00033
Updates:
Summary: rehearsal marks with direction DOWN should go below the system
Status: Fixed
Labels: fixed_2_13_8
Comment #2 on issue 893 by joeneeman: rehearsal marks with direction DOWN
should go below the system
http://code.google.com/p/lilypond/issues/detail?id
Comment #1 on issue 871 by marnenlk: support for MacOS X 10.6 snow leopard
http://code.google.com/p/lilypond/issues/detail?id=871
Whether the main developers have Snow Leopard or not, this is a
high-priority issue, since it effectively
renders the program nearly unusable on Mac OS X. It does
Updates:
Status: Fixed
Labels: fixed_2_13_7
Comment #2 on issue 871 by percival.music.ca: support for MacOS X 10.6 snow
leopard
http://code.google.com/p/lilypond/issues/detail?id=871
Before criticizing, learn what the Priority means to us. It means should
we delay a
stable
Comment #3 on issue 871 by marnenlk: support for MacOS X 10.6 snow leopard
http://code.google.com/p/lilypond/issues/detail?id=871
Yes, I just discovered that build, and it appears to fix the problem.
Thanks!
--
You received this message because you are listed in the owner
or CC fields
Comment #4 on issue 871 by marnenlk: support for MacOS X 10.6 snow leopard
http://code.google.com/p/lilypond/issues/detail?id=871
percival.music.ca wrote:
Our guideline for a stable release is does it work
better than the previous version.
But...no, 2.13.6 did not work better than
Comment #5 on issue 871 by percival.music.ca: support for MacOS X 10.6 snow
leopard
http://code.google.com/p/lilypond/issues/detail?id=871
marnelk wrote:
Our guideline for a stable release is does it work
better than the previous version.
But...no, 2.13.6 did not work better than
Status: Accepted
Owner: jameseli...@googlemail.com
Labels: Type-Defect Priority-Medium
New issue 896 by jameseli...@googlemail.com: When used after \tag,
\partcombine may fail to print notes
http://code.google.com/p/lilypond/issues/detail?id=896
\version 2.13.6
music = {
\set
Updates:
Status: Accepted
Labels: Type-Defect Priority-Regression OpSys-Windows lilypond-book
Comment #1 on issue 895 by v.villenave: lilypond-book fails on Windows due
to missing time.dll
http://code.google.com/p/lilypond/issues/detail?id=895
Thanks, marking as Accepted
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 897 by v.villenave: key signatures should be inherited by all
Voices (no matter their accidental style)
http://code.google.com/p/lilypond/issues/detail?id=897
In the following example, no natural sign
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Medium Engraving-nitpick
New issue 898 by v.villenave: Enhancement: rests should be taken into
account when determining beaming intervals
http://code.google.com/p/lilypond/issues/detail?id=898
The attached example shows
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Regression Engraving-nitpick
New issue 899 by v.villenave: full-measure-extra-space should be more
flexible
http://code.google.com/p/lilypond/issues/detail?id=899
New report from Trevor D.:
Between 2.11.9 and 2.11.10 (see
Status: Accepted
Owner: v.villenave
CC: joeneeman
Labels: Type-Collision Priority-Regression
New issue 900 by v.villenave: Wrong chords and lyrics spacing may cause
collisions
http://code.google.com/p/lilypond/issues/detail?id=900
In the following example, the spacing is intentionally tight
Updates:
Status: Verified
Comment #5 on issue 892 by v.villenave: Patch: Twoside mode (different
margins on odd and even pages)
http://code.google.com/p/lilypond/issues/detail?id=892
OK, the patch has been merged as a7f5c5abf97ad7c54122dac22cc9574ce082e3d9.
Closing.
--
You
Comment #1 on issue 900 by jameseli...@googlemail.com: Wrong chords and
lyrics spacing may cause collisions
http://code.google.com/p/lilypond/issues/detail?id=900
This is the same as http://code.google.com/p/lilypond/issues/detail?id=890
--
You received this message because you are listed
Updates:
Cc: joeneeman
Comment #5 on issue 890 by v.villenave: Chord names collide with staff on
second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
Issue 900 has been merged into this issue.
--
You received this message because you
Updates:
Status: Duplicate
Cc: -joeneeman
Mergedinto: 890
Comment #2 on issue 900 by v.villenave: Wrong chords and lyrics spacing may
cause collisions
http://code.google.com/p/lilypond/issues/detail?id=900
Indeed. Marking as duplicate.
--
You received this message
Comment #2 on issue 800 by organsnyder: Melismas extenders are broken when
there's another staff
http://code.google.com/p/lilypond/issues/detail?id=800
Patch that fixes this and issue 786 is available on Rietveld:
http://codereview.appspot.com/150067
--
You received this message because you
Comment #6 on issue 786 by organsnyder: Extenders in lyrics stop
prematurely if a single underscore is found
http://code.google.com/p/lilypond/issues/detail?id=786
Patch that fixes this and issue 800 is available on Rietveld:
http://codereview.appspot.com/150067
--
You received
Comment #6 on issue 871 by fodber: support for MacOS X 10.6 snow leopard
http://code.google.com/p/lilypond/issues/detail?id=871
the (dreadful) jEdit LilyPondTool
I hope you are joking.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #3 on issue 800 by organsnyder: Melismas extenders are broken when
there's another staff
http://code.google.com/p/lilypond/issues/detail?id=800
Nevermind about that patch - it was the wrong approach. I'm working on
determining
the correct one.
--
You received this message because
Comment #2 on issue 887 by pnorcks: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
So, if I understand correctly, the URIs should be using percent escape
codes for all
non-ASCII characters
Comment #3 on issue 887 by harmathdenes: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
Yes, I think that would be correct.
--
You received this message because you are listed in the owner
or CC
Updates:
Status: Fixed
Owner: ---
Comment #2 on issue 513 by reinhold.kainhofer: abc2ly tempo mark and typos
http://code.google.com/p/lilypond/issues/detail?id=513
First issue (Q: only converted to some midi settings, but not to \tempo) is
fixed
with commit
Updates:
Status: Fixed
Owner: ---
Comment #2 on issue 512 by reinhold.kainhofer: abc2ly church modes
http://code.google.com/p/lilypond/issues/detail?id=512
Fixed in commit ba4589749d489baf05866ec282d7f7e0177c3bff
The main problem was that the comparison was done without
Updates:
Owner: percival.music.ca
Comment #3 on issue 450 by reinhold.kainhofer:
input/regression/tuplet-properties.ly
http://code.google.com/p/lilypond/issues/detail?id=450
in 2.13.7, the tuplet number is above the note in the second tuplet... I'm
not sure
what the preferred
Updates:
Owner: percival.music.ca
Comment #1 on issue 471 by reinhold.kainhofer:
explicitKeySignatureVisibility shouldn't be necessary here
http://code.google.com/p/lilypond/issues/detail?id=471
In 2.12 and 2.13.7, I can't see any different with and without the
\once\set...
What's
Updates:
Status: Fixed
Labels: fixed_2_13_7
Comment #1 on issue 866 by percival.music.ca: gub should use a real
buildnumber
http://code.google.com/p/lilypond/issues/detail?id=866
Fixed in 2.13.7.
--
You received this message because you are listed in the owner
or CC fields
Comment #2 on issue 471 by percival.music.ca:
explicitKeySignatureVisibility shouldn't be necessary here
http://code.google.com/p/lilypond/issues/detail?id=471
Great example of the badness of having no attached png! :(
I _think_ the problem is the very right-hand side of the staff
Updates:
Status: Invalid
Comment #1 on issue 894 by percival.music.ca: lilypond-book fails from the
command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
I'm sorry, but I'm marking this as invalid unless somebody can replicate it
with a
clean OSX system
Status: Accepted
Owner: percival.music.ca
Labels: Type-Defect Priority-Low OpSys-Windows
New issue 901 by percival.music.ca: gub: lilypad.exe has a 40% chance of
being included
http://code.google.com/p/lilypond/issues/detail?id=901
lilypad.exe is not always copied into the tarball
Comment #2 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
How do you define clean?
--
You received this message because you are listed in the owner
or CC fields of this issue
Comment #5 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
The only change that's been made here is to lilypond-book, to have it point
to the
newer python version shipped with LilyPond
Comment #6 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
I should note that this is also the same error reported if, rather than
change
lilypond-book, the PATH is changed to put
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #6 on issue 890 by joeneeman: Chord names collide with staff on
second system when lyrics are present
http://code.google.com/p/lilypond/issues/detail?id=890
(No comment was entered for this change.)
--
You received
Comment #1 on issue 861 by reinhold.kainhofer: website contains bad html
http://code.google.com/p/lilypond/issues/detail?id=861
Fixed in commit b7bc9a032c8504d34d5600b21c25920947a60e92
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #4 on issue 800 by organsnyder: Melismas extenders are broken when
there's another staff
http://code.google.com/p/lilypond/issues/detail?id=800
Sorry for the noise, but the patch referenced above is valid again, and
appears to
properly fix this bug.
--
You received this message
Comment #2 on issue 861 by percival.music.ca: website contains bad html
http://code.google.com/p/lilypond/issues/detail?id=861
Great! Could we get it in web-texi2html.init as well, then mark it as
fixed?
--
You received this message because you are listed in the owner
or CC fields
Comment #2 on issue 847 by percival.music.ca: python scripts should add an
autogenerated marker
http://code.google.com/p/lilypond/issues/detail?id=847
I think the idea is that if a script adds/changes something in HTML, it
should add
something like
-- generated from scripts/build/www
Comment #2 on issue 818 by reinhold.kainhofer: Bus error when adding
Instrument_name_engraver to StaffGroup and outputting MIDI.
http://code.google.com/p/lilypond/issues/detail?id=818
The file compiles just fine with 2.13.7 and 2.12.2 under Linux (Kubuntu)
--
You received this message
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #5 on issue 800 by n.puttock: Melismas extenders are broken when
there's another staff
http://code.google.com/p/lilypond/issues/detail?id=800
(No comment was entered for this change.)
--
You received this message because
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #7 on issue 786 by n.puttock: Extenders in lyrics stop prematurely
if a single underscore is found
http://code.google.com/p/lilypond/issues/detail?id=786
(No comment was entered for this change.)
--
You received
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #2 on issue 895 by percival.music.ca: lilypond-book fails on
Windows due to missing time.dll
http://code.google.com/p/lilypond/issues/detail?id=895
I think this is fixed.
--
You received this message because you are listed
Updates:
Status: Fixed
Labels: fixed_2_13_5
Comment #7 on issue 764 by percival.music.ca: convert-ly does not work in
the lilypad for OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=764
I believe this is fixed. NB: this is when invoking convert-ly **from
Updates:
Status: Fixed
Owner: percival.music.ca
Labels: fixed_2_13_4
Comment #1 on issue 402 by percival.music.ca: osx intel app lists itself
as ppc
http://code.google.com/p/lilypond/issues/detail?id=402
I believe this was fixed.
--
You received this message because
Updates:
Labels: OpSys-OSX
Comment #7 on issue 894 by percival.music.ca: lilypond-book fails from the
command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
Don't change anything inside the App bundle. Try setting $PYTHONHOME to
point to
somewhere inside
Comment #8 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
I feel like I'm going to have to re-write the set up for Mac OSX portion.
--
You received this message because you are listed
Comment #10 on issue 894 by percival.music.ca: lilypond-book fails from the
command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
you still get this message?
Could not find platform independent libraries prefix
Could not find platform dependent libraries
Status: Accepted
Owner: lemzwerg
Labels: Type-Enhancement
New issue 902 by lemzwerg: Support for primo and secondo page layout
http://code.google.com/p/lilypond/issues/detail?id=902
`Classical' layout of four-handed piano music positions the staves for the
left player (`secondo') on the left
Comment #11 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
Exactly. I don't have clue #1 where else to set PYTHONHOME to, other than
the
location of the python executable (LilyPond.app
Comment #12 on issue 894 by percival.music.ca: lilypond-book fails from the
command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
James, I'm sorry, but there's so many demands on me right now (both
lilypond and
otherwise), so my sanity can't afford to have me
Updates:
Status: New
Comment #13 on issue 894 by jameseli...@googlemail.com: lilypond-book fails
from the command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
Until someone else who's smarter than I, and has more time than you can
take a look
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #1 on issue 768 by nicolas.sceaux: Enhancement: syntax shortcut for
repeated chords
http://code.google.com/p/lilypond/issues/detail?id=768
(No comment was entered for this change.)
--
You received this message because you
Updates:
Status: Accepted
Comment #14 on issue 894 by v.villenave: lilypond-book fails from the
command-line in OSX 10.4
http://code.google.com/p/lilypond/issues/detail?id=894
James, if you're reopening this as a bug meister (not a simple user), the
correct
status should
Status: Accepted
Owner: v.villenave
CC: percival.music.ca
Labels: Type-Enhancement Usability Priority-Medium OpSys-All
New issue 903 by v.villenave: Enhancement: a more user-friendly way to
specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
Currently
Comment #5 on issue 887 by pnorcks: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
Also, I'm not sure how Latin-2 fits into this issue. Isn't Latin-2 a
single-byte
ASCII extension? \303\241
Comment #2 on issue 865 by tdanielsmusic: Enhancement: ancient tablatures
support
http://code.google.com/p/lilypond/issues/detail?id=865
I've decided to make a start on this. Not sure how far I'll be able to get
though.
I'll report progress on the tablature list.
--
You received
Comment #2 on issue 836 by i...@hulin.org.uk: Enhancement: output-suffix as
a (Score) context property
http://code.google.com/p/lilypond/issues/detail?id=836
I wasn't able to implement output-prefix and filename as contexts to
\book easily,
so we now have
\bookOutputSuffix newsuffix
Comment #1 on issue 903 by veryfurryfur: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
The fact that it cannot be used in safe mode is only one manifestation of a
more
fundamental issue. \include italiano.ly
Comment #2 on issue 903 by Carl.D.Sorensen: Enhancement: a more
user-friendly way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
In keeping with LilyPond style we should use
\language italiano or
\noteLanguage italiano
We should not use
\lang
because
Comment #3 on issue 903 by fodber: Enhancement: a more user-friendly way to
specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
It doesn't need a new command, only a bit of reorganization.
The command is there:
#(ly:parser-set-note-names parser
Comment #7 on issue 887 by fodber: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
Dénes, the jpedal is actually broken: the new String(uriDecodedBytes) is
made using
platform-specific encoding
Updates:
Status: Fixed
Comment #3 on issue 628 by percival.music.ca: Regression: markup \note
doesn't work as a TimeSignature stencil
http://code.google.com/p/lilypond/issues/detail?id=628
Ok, so we think it's fixed?
Bug people, please check with 2.13.7.
--
You received
Comment #4 on issue 628 by reinhold.kainhofer: Regression: markup \note
doesn't work as a TimeSignature stencil
http://code.google.com/p/lilypond/issues/detail?id=628
No, it doesn't work with 2.13.7. The note in the denominator is simply not
printed
(but there is also no warning/error
Updates:
Status: Accepted
Comment #5 on issue 628 by percival.music.ca: Regression: markup \note
doesn't work as a TimeSignature stencil
http://code.google.com/p/lilypond/issues/detail?id=628
Ok, I misread Patrick's comment. But why does the title say regression,
when the
actual
Comment #6 on issue 628 by pnorcks: Regression: markup \note doesn't work
as a TimeSignature stencil
http://code.google.com/p/lilypond/issues/detail?id=628
I should have said that using \numericTimeSignature is a workaround (last
time I
checked). Apparently it worked in 2.8, so I assume
Status: Accepted
Owner: v.villenave
Labels: Priority-Regression Type-Defect
New issue 904 by v.villenave: Regression: partially-tied chords may look
wrong when the tie flips
http://code.google.com/p/lilypond/issues/detail?id=904
\version 2.12.0 % or 2.13.7
% When two chords are tied
Comment #5 on issue 746 by v.villenave: Automatic code indentation
improvement (and replacing tabs with spaces)
http://code.google.com/p/lilypond/issues/detail?id=746
Please also have a look at Graham's howto on
http://lists.gnu.org/archive/html/lilypond-devel/2009-11/msg00357.html
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Encoding
New issue 905 by v.villenave: LilyPond should accept UTF-8 BOM signatures
even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Currently, LilyPond fails to parse UTF-8 files
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Jail
New issue 906 by v.villenave: gs fails in jail mode unless run separately
with sudo (error 32512)
http://code.google.com/p/lilypond/issues/detail?id=906
New report from Bertalan:
\version 2.13.7
I set up
Comment #10 on issue 573 by frederic...@m4x.org: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Graham said: I think we just need a few words or a snippet or something to
close this.
Can anybody tell me what to do?
What do we
Comment #5 on issue 903 by n.puttock: Enhancement: a more user-friendly way
to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
I broadly agree with Carl's comments.
I'm not fussed about having block scope, since it's easy enough to
implement
Comment #11 on issue 573 by percival.music.ca: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Valentin said that we needed a new snippet or changing an old one. Neil
said that it
should be a new snippet. I thought this was clear
Updates:
Status: Fixed
Labels: fixed_2_13_8
Comment #2 on issue 676 by reinhold.kainhofer: unterminated ties should not
be rendered in MIDI
http://code.google.com/p/lilypond/issues/detail?id=676
Fixed in latest git master (commit 1216caa5de472f1324fbcc0a5e08b560389307e7
Comment #12 on issue 573 by n.puttock: score-final mark mangles score-final
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
I'm now not so sure adding a snippet is the right approach here, since this
seems to
be the same bug as #492 (see my comments in this thread
Comment #6 on issue 903 by veryfurryfur: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
As for the syntax, my choice would be
\language italiano
because it's simpler, quicker and we don't need to change it in case
Comment #7 on issue 903 by percival.music.ca: Enhancement: a more
user-friendly way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
My only caution is that we might want to save this change until 3.0. That
said, it
should be relatively easy to do
Comment #2 on issue 854 by percival.music.ca: lilycontrib.tcl
http://code.google.com/p/lilypond/issues/detail?id=854
Later versions of this script can be found on the Frogs mailist:
http://frogs.lilynet.net/
--
You received this message because you are listed in the owner
or CC fields
Comment #1 on issue 838 by percival.music.ca: Inconsistency in tests output
size
http://code.google.com/p/lilypond/issues/detail?id=838
More info here:
http://lists.gnu.org/archive/html/lilypond-devel/2009-11/msg2.html
--
You received this message because you are listed in the owner
Updates:
Status: Fixed
Cc: -gpermus
Labels: fixed_2_13_8
Comment #2 on issue 837 by pnorcks: Unnecessary empty dirs in Win32 builds
http://code.google.com/p/lilypond/issues/detail?id=837
Fixed by this GUB commit:
http://github.com/janneke/gub/commit
Comment #8 on issue 903 by veryfurryfur: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
I really cannot see any risks involved to warrant waiting for a major
release. If you
disagree, please come forward
Comment #9 on issue 903 by d...@gnu.org: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
A major change in general input syntax, even optional, should be
accompanied by a
noticeable version number change.
--
You
Comment #1 on issue 898 by d...@gnu.org: Enhancement: rests should be taken
into account when determining beaming intervals
http://code.google.com/p/lilypond/issues/detail?id=898
It would also make sense to have an option to allow automatic beaming
across rests
when a note instead
Comment #10 on issue 903 by veryfurryfur: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
I don't mean it in a confrontational way, but may I ask what the rationale
is please?
--
You received this message because
Comment #11 on issue 903 by d...@gnu.org: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
Tool x can process Lilypond files of version y or later - that's sensible
for an
announcement.
convert-ly also has to work
Comment #12 on issue 903 by hanwenn: Enhancement: a more user-friendly way
to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
Would the language feature be feasible to implement as a music function
with no
arguments?
(the function implementation has
1 - 100 of 12581 matches
Mail list logo
