Re: Postponed Bugs #83 and #297: a Someone Else Problem
2008/1/27, Juergen Reuter [EMAIL PROTECTED]:
The ligature events are implemented as 'command-event', like \bar and
\time, which fall in between the notes.This is inconsistent with
start/stop commands like [ ] , but I can't really judge if that is the
best way to do it.
Hmmh, I don't understand. In Lily 2.7.x, in define-music-types.scm,
LigatureEvent has (types . (general-music span-event ligature-event
event)), i.e. it is a SpanEvent, or am I missing something? In Lily
2.11.x, it is implemented as StreamEvent, due to Erik's changes. How is
this related to command-event (which, btw, I could not find in the
sources)?
this distinction is not in the music 'type-system', but rather how the
events are attached to other things. Beam/slur/etc. start/stop are
attached to the notes, so in
c4]
the ] starts at the beginning of the note. Commands like \bar , \clef
and \] are not attached to notes, so for
c4 \]
the event registers at the end of the note, at the start of the new time-step.
I don't know what the best solution is, but for consistency, it would
probably be best if they were attached to notes like beams. The
downside to attaching to notes is that you would not be able to do
ligs = { \[ s2 \] }
{ c8 d e f }
\ligs
and have the ligature enclose the 4 notes.
(Oh, you are right, it's difficult to find me on the web, since my old
home page unfortunately died a while ago; there is now a new one at
www.juergen-reuter.de).
maybe you can update the relevant web-pages? That would be a useful
exercise in git use :-)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Postponed Bugs #83 and #297: a Someone Else Problem
Am Sonntag, 27. Januar 2008 23:19 schrieb Han-Wen Nienhuys: For issue 297, I can change the formatting to end exactly on the last note; would that solve the problem? Juergen? I would be very happy if only this could be solved! However, there is one additional problem with ligature brackets: If they appear together with a suggestAccidental and Lyrics above, vertical spacing is broken, i.e. far too much space is inserted (example available on request). Again, I offer sponsoring these bug-fixes (or possibly re-writes?) and, in addition, I could supply test cases, feedback etc. Best regards, Robert -- Robert Memering Arbeitsbereich Linguistik, Universität Münster Hüfferstraße 27, D-48149 Münster, Germany Raum 01.85, Tel. +49-251-83-31958 http://santana.uni-muenster.de ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Postponed Bugs #83 and #297: a Someone Else Problem
Dear Lilypond developers, I am preparing some sophisticated scores of renaissance vocal music and I am severely affected by the problems with ligature brackets described in issue #83 and #297 of the bug tracker. (I can send examples much uglier than in the bug tracker if anyone is interested.) In #83 it says: Contibuted code by Juergen, ie. a 'Someone Else Problem'. Does this mean that it won't get fixed unless by Juergen? If this is the case, is there any chance I might sponsor fixing this bug? I am using Lilypond for a commercial job, and I'm afraid I cannot deliver the scores in the present state. However, I might be able to contribute a substantial amount of money if the issues could be fixed. And, by the way, as I haven't been involved in Lilypond development: Who is Juergen? Best regards, Robert -- Robert Memering Arbeitsbereich Linguistik, Universität Münster Hüfferstraße 27, D-48149 Münster, Germany Raum 01.85, Tel. +49-251-83-31958 http://santana.uni-muenster.de ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Postponed Bugs #83 and #297: a Someone Else Problem
Juergen (CC-d) is the person who wrote the ligature code, including the one for the brackets. I'm looking at the issues now, but there is something I don't understand. The ligature events are implemented as 'command-event', like \bar and \time, which fall in between the notes.This is inconsistent with start/stop commands like [ ] , but I can't really judge if that is the best way to do it. For issue 297, I can change the formatting to end exactly on the last note; would that solve the problem? Juergen? 2008/1/27, Robert Memering [EMAIL PROTECTED]: Dear Lilypond developers, I am preparing some sophisticated scores of renaissance vocal music and I am severely affected by the problems with ligature brackets described in issue #83 and #297 of the bug tracker. (I can send examples much uglier than in the bug tracker if anyone is interested.) In #83 it says: Contibuted code by Juergen, ie. a 'Someone Else Problem'. Does this mean that it won't get fixed unless by Juergen? If this is the case, is there any chance I might sponsor fixing this bug? I am using Lilypond for a commercial job, and I'm afraid I cannot deliver the scores in the present state. However, I might be able to contribute a substantial amount of money if the issues could be fixed. And, by the way, as I haven't been involved in Lilypond development: Who is Juergen? Best regards, Robert -- Robert Memering Arbeitsbereich Linguistik, Universität Münster Hüfferstraße 27, D-48149 Münster, Germany Raum 01.85, Tel. +49-251-83-31958 http://santana.uni-muenster.de ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Postponed Bugs #83 and #297: a Someone Else Problem
On Sun, 27 Jan 2008, Han-Wen Nienhuys wrote: Juergen (CC-d) is the person who wrote the ligature code, including the one for the brackets. Yepp, ages ago (around early 2002)... I'm looking at the issues now, but there is something I don't understand. The ligature events are implemented as 'command-event', like \bar and \time, which fall in between the notes.This is inconsistent with start/stop commands like [ ] , but I can't really judge if that is the best way to do it. Hmmh, I don't understand. In Lily 2.7.x, in define-music-types.scm, LigatureEvent has (types . (general-music span-event ligature-event event)), i.e. it is a SpanEvent, or am I missing something? In Lily 2.11.x, it is implemented as StreamEvent, due to Erik's changes. How is this related to command-event (which, btw, I could not find in the sources)? For issue 297, I can change the formatting to end exactly on the last note; would that solve the problem? Juergen? Probably yes, at least in many cases, as far as I understand. 2008/1/27, Robert Memering wrote If this is the case, is there any chance I might sponsor fixing this bug? Speaking for me personally, it's more a problem of time lacking rather than of sponsoring (I even did not yet get acquainted with the git versioning system)... But there may be other people interested. And, by the way, as I haven't been involved in Lilypond development: Who is Juergen? Me! :-) (Oh, you are right, it's difficult to find me on the web, since my old home page unfortunately died a while ago; there is now a new one at www.juergen-reuter.de). Greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
