On Sun, 4 Jan 2009, Trevor Daniels wrote:
BTW, the term "accidental style" appears twice in the documentation with a
completely different meaning:
- in 1.1.3, meaning the way how to display and reset accidentals
In the detailed explanation they are named "rules" so I propose to
always call t
Hi, all!
The horizontal placing of breathing signs in Gregorian Chant is anyway
somewhat broken. Looking e.g. at the "Sanctus, Sanctus, Sanctus"
example in "2.8.4 Typesetting Gregorian chant", the distance for the
second divisio minima (after the second "Sanctus") is fine, while the
distance
Mats writes:
> > * Actually, the stroke does not strike the flag, but rather the whole
> > stem. Hence, it should not be called *flag*-style. In particular,
> > I think I have already seen a stroke being added to a crotchet,
> > which does not have a flag attached onto its stem (although I
Regarding the discussion of special neumes for Bistropha, Tristropha,
Oriscus, Pes quassus, Salicus, and Quilisma-Pes, I finally found a
(more or less) definitive answer ([1], pp. 235-237, 252-258):
The Editio Vaticana (VAT) from 1905 (Ordinarium Missae) / 1907
(Graduale) / 1908 (Antiphonale) is
Hi!
Below is a patch for 1.5.7 that introduces mensural flags. However,
there are some open issues:
* There is no mensural 32nd or 64th note, but only fusa (8th) and
semifusa (16th). For completeness, I have nevertheless tried to
design flags for 32nd and 64th, although they are my pure in
On Mon, 10 Sep 2001, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > + written for the GNU LilyPond music typesetter
>
> Yes, thanks. Integrated the patch into 1.5
>
Thanks, too!
> > + * moment of the second note. Actually, it should take the moment of
> > + * the first note.
> >
This is the second try for a porrectus engraver. Some issues from the
TODO list have been solved, but even more have been added. Hence,
there will be (at least) a third try...
The most important changes are:
* Syntax change: \porrectus -> \~, reflecting recent discussion with
Mark and Mats.
On Thu, 20 Sep 2001, Han-Wen Nienhuys wrote:
>
>
> [EMAIL PROTECTED] writes:
> > * New porrectus properties: porrectus-width, line-thickness.
>
> Please use simply "width" and "thickness" we want to keep the number
> of variables down.
>
I had a look at grob-property-description.scm. It a
Applied (in CVS).
Greetings,
Juergen
On Mon, 9 May 2005, Pal Benko wrote:
What about the remaining durations (maxima, ...) for petrucci style?
I guess, they should be the same as for mensural style?
Yes. These as well are quite close but not identical to those found
in Petrucci prints; they will d
... I would like to ask if the e-Mail addresses in the ChangeLog could be
either encrypted or replaced by e.g. http addresses.
From carefully analyzing some of the countless spam mails and delivery
failure notification mails, it looks like as if the ChangeLog file is one
of the major sources fo
On Fri, 20 May 2005, Graham Percival wrote:
...
diff -u lilypond/Documentation/user/programming-interface.itely:1.34
lilypond/Documentation/user/programming-interface.itely:1.35
--- lilypond/Documentation/user/programming-interface.itely:1.34Mon May
16 11:12:29 2005
+++ lilypond/Documenta
Han-Wen,
actually, I would strongly welcome to see some kind of formal definition
of the structure of lily music, maybe something analogous to an XML Schema
definition, but for guile/scheme instead of XML:
When implementing the "\ligature { }" command (see
ly/gregorian-init.ly), I finally f
On Sat, 4 Jun 2005, Graham Percival wrote:
The ancient notation template seems to be using a percussion staff. I can't
see anything obviously wrong in the template; could somebody familiar
with ancient notation look at it?
Indeed, the result looks quite broken. AFAICS, the template looks ok
Hi,
FYI: I just googled for "syntax diagrams" and "generate" and found this
page:
http://www.research.philips.com/technologies/syst_softw/elegant/
They offer a GPL'd tool for automatically generating syntax diagrams (in
PostScript format) for a given (E)BNF. There is a paper that documents
See, for example,
http://www.tigris.org/nonav/scdocs/ddCVS_cvscontributing.html#cvsresolving
Greetings,
Juergen
On Tue, 30 Aug 2005, Pocentek Gauvain wrote:
Hi,
I've just committed updated french files and get this:
cvs server: file `po/newweb.pot' had a conflict and
has not been modifie
On Tue, 25 Oct 2005, Matevz Jekovec wrote:
Hello to all!
I'm typesetting a few Gallus motets using the ancient.ly template for my
work. I encountered some problems:
Hello,
I think there is no ancient.ly file in the distribution, but I guess you
are referring to the mensural music transcript
I think the following does *almost* what you want (only almost, because
you get harmonic note heads instead of quarter note heads):
\version "2.7.17"
#(define-public (note-head::calc-glyph-name grob) "2")
barOne = { \once \override Staff.BarLine #'bar-size = #2
\bar "|" }
barTwo
On Tue, 15 Nov 2005, Juergen Reuter wrote:
I think the following does *almost* what you want (only almost, because you
get harmonic note heads instead of quarter note heads):
...
\override Staff.NoteHead #'style = #'harmonic
...
With attached patch, you can say
Here's what my approach, as described, yields (see attachment).
Greetings,
Juergen
On Tue, 15 Nov 2005, Michael Welsh Duggan wrote:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Michael Welsh Duggan wrote:
Mats Bengtsson <[EMAIL PROTECTED]> writes:
If you want to remove the stems completel
On Thu, 17 Nov 2005, Han-Wen Nienhuys wrote:
...
Ligature spacing: as has been mentioned before, coherent ligatures (at
least of the vaticana variety) should act like a single un-breakable
paper column, but should not receive extra spacing based on the number
of notes within the ligature. I am
Thanks, applied. If you want a quick response, next time you may want to cc:
any ancient notation related bug report directly to me, since I am reading
bug-lilypond slightly irregularly...
Greetings,
Juergen
Michael Welsh Duggan wrote:
Another patch, this one which fixes the addition of c
Vertical placement of scripts is broken as of current CVS. In particular, note
that the vertical placement does not monotonously increase with the pitch.
See attached png.
ly-file:
\version "2.7.16"
\score {
\transpose c c' {
\stemDown
e4\marcato
f4\marcato
g4\marcato
As of current CVS, tuning grob SpacingSpanner's properties
shortest-duration-space and spacing-increment gives weird results for
horizontal spacing. For example, with the below ly file, the first two lines
are widely spaced, while the remaining lines are tightly packed.
Greetings,
Juergen
On Sat, 19 Nov 2005, Han-Wen Nienhuys wrote:
Juergen Reuter wrote:
Vertical placement of scripts is broken as of current CVS. In particular,
note that the vertical placement does not monotonously increase with the
pitch.
thanks. Fixed. I guess that the proper placement for ^ is in the
similar to that in the example) could be solved by inserting
\break commands at proper places? I guess I should investigate further.
Greetings,
Juergen
On Sat, 19 Nov 2005, Han-Wen Nienhuys wrote:
Juergen Reuter wrote:
As of current CVS, tuning grob SpacingSpanner's properties
shortest-dur
By the way, on site/about/index.html you are linking to the LAD Booth @
LinuxTag 2003. This has indeed a nice photo, but it's somewhat outdated.
What about linking to one (or more) of the following more up-to-date
LAD-related sites?
http://lalists.stanford.edu/
(Mailing list archives of the
FYI, this bug might be related to the bug that I reported in
http://lists.gnu.org/archive/html/lilypond-devel/2005-11/msg00093.html
which is also still not solved.
Greetings,
Juergen
On Sun, 11 Dec 2005, Cameron Horsburgh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't know if t
Hi,
with current 2.7 CVS, I do not get the warning (though your .ly file needs
syntactically slightly be updated for 2.7.x; see attachment).
Greetings,
Juergen
On Tue, 13 Dec 2005, Erik Sandberg wrote:
On Monday 12 December 2005 21.56, Don Blaheta wrote:
This is 2.6.4 on a MacOS box. Inci
Hi, Elie!
Sorry for the late answer!
On Thu, 29 Dec 2005, Elie Roux wrote:
One of the aim will certaily be to make a standard for gregorian chant
representation, that will be under GPL, and that everyone will be able to
use, a bit like MusicXML is ; I think it is quite important that somethi
Hi, all!
As I remarked a couple of months ago, I had similar problems with ancient
notation. Typographically, to my experience, you will get by far the best
results by
(1) providing duration-independent notehead selection by patching
scm/output-lib.scm as follows:
Index: scm/output-lib.s
On Mon, 20 Feb 2006, Graham Percival wrote:
Does anybody know why this doc section exists? It introduces four
articulation marks that are covered in Articulation.
Hi!
Long time ago, when people where repeatingly asking for "contemporary
music notation" and when I also had the feeling that s
On Tue, 21 Feb 2006, Han-Wen Nienhuys wrote:
...
there is only 1 SpacingSpanner in the entire score. You can only override it
at the start.
Just a half-baken, weired idea (and not at all thoroughly thought
through): Are there much more examples of properties that can be
overridden only
On Wed, 22 Feb 2006, Erik Sandberg wrote:
Hi Juergen,
IIRC, mensural notation is contributed & supported by you. A regression test
is broken:
There seem to be some problems with regression/mensural-ligatures.ly. At least
two problems exist:
- Dots are handled incorrectly.
- Notes take up too m
Hi,
"regression test" is a technical term that is commonly used in the field
of software engineering; see for example:
http://en.wikipedia.org/wiki/Regression_test
The emphasis lies here on testing across different revisions of a piece of
software in order to ensure that bugs that previously
[CC-ing to lily-devel, since this discussion may also be of interest for
other developers; we are discussing here about manual Sect. 3.7.2]
On Mon, 20 Mar 2006, Geoff Horton wrote:
I have a revised template that I think works fairly well, plus a suggestion:
\include "english.ly"
\include "g
On Tue, 21 Mar 2006, Elie Roux wrote:
Hello,
I'm working on gregorian chant reprensentation for a project student in
a graduate ingeneering school in France, and I have had a lot of
discussion with a monk on it. My aim is to improve gregorian chant
representation in free softwares for monk to u
Yes, this looks better. Now, that we have "barAlways = ##t", we can also
drop these "dMinima" etc. definitions. I also set the \version to 2.8.0
(just looks nicer in the source). Result is attached. I think it's still
not perfect, but much better than what is currently in the docu.
Graha
Please note that the property name "style" currently (hopefully)
consistently denotes _font_ style. It is defined with this meaning for
noteheads, rests, accidentals, time signatures, flags, and custos.
Nowadays, that Lily supports subproperties (cp. manual Sect. 9.1.4 or
9.2.1), maybe, on
Hi,
indeed, this topic has been brought up at least in early 2003 (maybe even
earlier) and also went into Han-Wen's and Jan's XIV CIM 2003 paper (see
right column of page 4 in this paper). There _is_ already an implicit way
of writing style sheets (although somewhat limited), but let me expla
On Fri, 7 Apr 2006, Joe Neeman wrote:
[...]
OK, so the solution will always have a certain level of instability. Just to
put some idea of scale on my previous example graphs, it's possible that
LilyPond will be tossing up between using 5 systems and using 10 systems. 5
systems provides much bett
On Tue, 11 Apr 2006, Graham Percival wrote:
(this'll probably get lost while HWN is away, but anyway...)
From the docs,
"A hairpin starts at the left edge of the beginning note and ends on the
right edge of the ending note."
tupletFullLength (boolean)
If set, the tuplet is printed up
On Wed, 12 Apr 2006, Geoff Horton wrote:
And a similar thing for TextSpanner would probably fix the \episem, which
broke at some time during the 2.7 series (see manual Sect. 7.7.7).
I think \episem needs more work anyhow. It should be going in the next
staff space available above the notes, no
Hi,
maybe I should also comment on this topic, since I originally contributed
the whole polygon stuff in order to implement clusters, and thus still
feel (very) little responsible for it. ;-)
As for the triangle, yes, I also think it _is_ abuse to use the
blot-diameter in order to control th
On Tue, 11 Apr 2006, Graham Percival wrote:
...
TEMPLATES
Lilypond knowledge required: moderate
Estimated time: 5 hours
Do all the templates in chapter 3 work? I know that the "Jazz ensemble" one
is very old, and is generally icky. If nobody updates it, I think we should
just delete it. I
The introduction for the Gregorian transcription template currently says:
"This example demonstrates how to do modern transcriptions of Gregorian
music. Gregorian music has no measure, no stems; it uses only half and
quarter notes, and two types of barlines, a short one indicating a rest,
and
Hi,
considering the recent misreading of lily's Gregorian chant capabilities
that could be seen on this list, I would like to propose a minor update
with clarifications to Sect. 7.7.10.2. See attachment.
Greetings,
JuergenIndex: Documentation/user/instrument-notation.itely
==
Hi,
lyrics with non-latin characters, such as in input/sakura-sakura.ly,
basically compile fine on my machine without any error message, and the
output looks fine.
If, however, I replace one of the non-latin characters with an obviously
unavailable utf-8 code (at least with the fonts current
By the way, you may also be interested in the following related work from
a workshop on Braille Notation of Psalmodia and Gregorian Chant, held in
Marburg, Germany, on October 2-3, 2002:
http://www.sbs-online.ch/musik/conference/documents/gregor.pdf
In order to make Gregorian chant notation r
Hi,
I have been trying to fix the misplaced dot bug in Gregorian chant
notation -- without sucess:
void
Vaticana_ligature_engraver::add_mora_column (Grob *parent)
{
if (!parent) // empty ligature
return;
if (augmented_primitives_.size () == 0) // no dot for column
return;
Item *d
Hi,
just being curious: is it intended that these Autotester messages are sent
to lilypond-cvs rather than just to the author/committer of the changes?
Greetings,
Juergen
P.S.: By the way, what is the Autotester? Is it run upon every cvs
commit? Is a commit rejected, if the test fails?
On Tue, 30 May 2006, Francisco Vila wrote:
Also, after a '$ cvs co' my local copy has strange '<<'- and
'>'-filled lines surrounding some of my changes, don't know if
they have been applied or not. So I really don't know how to obtain a
second patch from this.
See:
http://www.tigris.o
Hi,
just a comment to Sect. 6.6.1 (Articulations):
IMHO, the signum congruentiae, all fermatas, the segno sign and the coda
signs are no articulation signs. Historically, they were put together
with the articulation signs into the same manual section, because their
implementation was based o
Hi,
Sect. 7.3.2 (Entering lyrics) of the manual says:
"In order to assign more than one syllable to a single note, you must
surround them with quotes or use a _ character between the syllables."
This works fine e.g. for:
\addlyrics { gran- de_a- mi- go }
However, neither
\addlyrics { gran- \
On Wed, 7 Jun 2006, Han-Wen Nienhuys wrote:
...
I changed this a bit. Now, you need to use
http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html
Maybe you should correct the broken link on http://lilypond.org/web/index ?
Greetings,
Juergen
_
Hi,
the white mensural ligature example lily-2147380820.ly in Sect. 7.7.10.1
collapses in the HTML manual to a width of a few pixels (see the _first_
(almost invisible) png image in
http://lilypond.org/doc/v2.9/Documentation/user/lilypond/White-mensural-ligatures.html).
However, in the PDF ma
Hi,
how many glyphs are you planning to add? If your project is going to
become a font with many dozens of glyphs over time, you could add new .mf
files, just as the parmesan font does for ancient notation. If you grep
for the string "parmesan" on all files in the mf directory, you will see
Hi all,
please note that \partial or \upbeat, whatever you call it, has
musicologically a special meaning: the first, incomplete bar, and the last
bar of a piece or of a major section of a piece (typically the bar before
the next "||" bar glyph) should sum up to a complete bar.
For example,
On Thu, 6 Jul 2006, Mark Van den Borre wrote:
Graham,
"General improvements to "working on lilypond files", focusing on
teaching users how to write files that are easier to update. Not that
it will do any good, since nobody reads the manual anyway."
I was not aware that you underestimate the
On Fri, 7 Jul 2006, Graham Percival wrote:
In my example, I _did_ state
\noTimeSignature
c4 c c c | d d d d \partial 4 d | c c c c
... and some contemporary music may want to change the number of beats in a
bar without changing the notated time signature. Whatever we think of that
practice
with prima/secunda volta). Currently, LilyPond
doesn't automatically take this into account. Of course, the best solution in
this situation would be if LilyPond treated the measure position correctly
for repeats.
/Mats
Quoting Juergen Reuter <[EMAIL PROTECTED]>:
Hi all,
pleas
middle of a bar when there is a major section
change, eg at the Trio. I've never come across a repeat in the middle of
a bar, though...
Cheers,
Wol
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
u.org] On Behalf Of Juergen Reuter
Sent: 07 July 2006 17:31
To
On Wed, 26 Jul 2006, Han-Wen Nienhuys wrote:
...
Index: lily/instrument-name-engraver.cc
===
RCS file: /cvsroot/lilypond/lilypond/lily/instrument-name-engraver.cc,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -b -r1.86
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a variable,
you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at a
Hi, Pal!
Nice to see you back on this list! Mmmh, do you know when Petrucci
engraved this piece of music? Petrucci is known to have started with
beautiful printings around 1600. At that time, he demonstrated what is
possible with printing as compared to manual writing, because he wanted to
Oh, sorry!
Please forget about my last mail; it's nonsense; I looked wrong at the
patch and thought you wanted to change c clefs, rather than adding 2 f
clefs. Your patch looks perfect! Maybe I have slept too little...
Greetings,
Juergen
___
li
a = re.sub ( '-', '- ', a)# split words with -
+a = re.sub ( ' - - ', ' -- ', a) # unless was originally " -- "
Just being curious:
Maybe I am totally wrong (since I do not know the abc format in detail),
but shouldn't this be rather something like
a = re.sub ( '([^-])-([^-
On Wed, 4 Oct 2006, Mats Bengtsson wrote:
If I remember correctly, it's not included when you have the default note
head
style, simply since there is not real established standard for the layout of
a longa
note in modern typesetting. However, if you use
\override NoteHead #'style = #'mensural
On Mon, 2 Oct 2006, Laura Conrad wrote:
I just tested it and in actual code, yours seems to do the same thing
mine does,
N.B.: There should be a minor difference in the handling of white space
before/after the hyphen, which however is not essential, I guess.
except I find it harder to read
On Wed, 4 Oct 2006, Juergen Reuter wrote:
That is, lily should take a longa from neo-mensural font. The real problem
is the 'u' in 'noteheads.u-2': The parmesan font defines a symmetric
'noteheads.s-2neomensural', but neither up/down specific heads.
On a se
Hi all,
the longa notes problem reduces to this piece of code in method
"internal_print (Grob *me, string *font_char)" in file lily/note-head.cc:
if (!scm_is_symbol (style))
style = ly_symbol2scm ("default");
[... snip ...]
if (style != ly_symbol2scm ("default"))
{
SCM
Hi all,
just for the record in expectation of lily 2.10, here is a summary report
of known _NEW_ bugs in ancient notation that were newly introduced in the
2.9.x series. I list them here as a collective todo list, for myself
remembering them easier, but also for anybody else interested in the
On Sun, 8 Oct 2006, Juergen Reuter wrote:
* Section 7.7.10.1, second figure: Ligature brackets are not at all
displayed anymore. Same problem also in the introductionary Section
7.7.10.
Should be fixed now in cvs. The adaption to the new stream event code was
incomplete.
Greetings
On Sun, 8 Oct 2006, Juergen Reuter wrote:
* Section 7.7.7: The "episem" articulation does not appear (there should
be a horizontal line above the three last noteheads). In 2.7.x, the
right ending was badly placed; now the episem is completely invisible.
Also, the text scripts are
On Mon, 9 Oct 2006, Geoff Horton wrote:
FWIW, I'm not sure that the horizontal episema is best done with a
TextSpanner anyhow. In Solesmes notation, at least, it goes right over
the notes, not over the staff.
Gepff
Right. But I vaguely remember (I may be wrong) that a long time ago,
spanne
Hi,
may I apply attached patch in order to fix the size/shape of dots for
ancient notation? This patch adds a "style" property to the "Dots" grob
and a new glyph to the parmesan font.
Greetings,
JuergenIndex: ChangeLog
===
RCS f
On Wed, 11 Oct 2006, Han-Wen Nienhuys wrote:
why not simply do
string style =""
if (scm_is_symbol (scm_style))
style = ly_symbol2string (scm_style);
string idx = "dots.dot" + style;
Because, historically, there is no difference in lily's behaviour between
setting style to #'default
On Wed, 11 Oct 2006, Han-Wen Nienhuys wrote:
Because, historically, there is no difference in lily's behaviour between
setting style to #'default and #'(). However, if you do not
that must have been a long time ago; I think I've tried to remove this
feature for some time now.
Ok.
+
On Wed, 11 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
On Wed, 11 Oct 2006, Han-Wen Nienhuys wrote:
why not simply do
string style =""
if (scm_is_symbol (scm_style))
style = ly_symbol2string (scm_style);
string idx = "dots.dot" + style;
Because,
On Sun, 8 Oct 2006, Juergen Reuter wrote:
* The "longa notes" bug (cp.
http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00022.html)
has been tracked down to a general problem in output-lib.scm (see
http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00050.html
f
Hi, all!
I would expect the following lily file:
\version "2.9.22"
dottedQuarter =
#(define-music-function (parser location note) (ly:music?)
(make-music
'NoteEvent
'duration (ly:make-duration 2 1)
'pitch (ly:music-property note 'pitch)))
\new Voice \transpose c c' {
f4 f \do
n would save lots of duplicated code used for
navigating through music expressions, right? Or do we already have such a
function?
Thanks & Greetings,
Juergen
On Fri, 13 Oct 2006, Nicolas Sceaux wrote:
Juergen Reuter <[EMAIL PROTECTED]> writes:
Hi, all!
I would expect the following
On Fri, 13 Oct 2006, Han-Wen Nienhuys wrote:
If you modify this font, you may
+extend this exception to your version of the font, but you are not
+obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
I.e., effectively, we change the licence for
On Fri, 13 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
On Fri, 13 Oct 2006, Han-Wen Nienhuys wrote:
If you modify this font, you may
+extend this exception to your version of the font, but you are not
+obligated to do so. If you do not wish to do so, delete this exception
IIRC, I have seen this error from the very beginning of the new "~"
feature for lyrics.
Greetings,
Juergen
Processing
`/home/reuter/project/lilypond-2.9/input/regression/out-www/lily-1431938706.ly'
Parsing...[/home/reuter/project/lilypond-2.9/out/bin/../share/lilypond/2.9.24/ly/init.ly[/ho
On Sat, 14 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
/home/reuter/project/lilypond-2.9/out/bin/../share/lilypond/2.9.24/scm/markup.scm:92:10:
In procedure string-append in expression (string-append make-name ": "
...):
/home/reuter/project/lilypond-2.9/out/bi
On Sat, 14 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
On Sat, 14 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
/home/reuter/project/lilypond-2.9/out/bin/../share/lilypond/2.9.24/scm/markup.scm:92:10:
In procedure string-append in expression (string-append make
Hi,
in the following file:
\version "2.9.24"
\context Voice \transpose c c'' {
c8 c4
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
}
th
On Sun, 15 Oct 2006, Han-Wen Nienhuys wrote:
Juergen Reuter schreef:
\version "2.9.24"
\context Voice \transpose c c'' {
c8 c4
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c c c c c c c c c c c c c
c c c c
On Sun, 15 Oct 2006, Nicolas Sceaux wrote:
Juergen Reuter <[EMAIL PROTECTED]> writes:
By the way, do we have a generic substitution function that you can
pass an event type and some replacement expression to? Maybe
something like
(replace-for-all-matches
#(define-matching-expressio
Hi,
in the online manual, Sect. 14.1 ("An example of a musicological
document"), in the "screech and boink" example, the piano brace is too
small. At least, I can not see in the .ly source any reason why the brace
should be printed smaller.
See:
http://lilypond.org/doc/v2.9/Documentation/u
FYI: After looking once more through a couple of files in the scm
directory, I finally found the shift-duration-log function that exactly
does what I wanted. For the moment, I take this one.
Thanks again,
Juergen
On Wed, 18 Oct 2006, Juergen Reuter wrote:
On Sun, 15 Oct 2006, Nicolas
Hi, Graham!
I had to make small updates to some of the ancient notation examples in
the docs to make them better reflect the current implementation.
Accordingly, I also updated tiny parts of the text refering to these
examples. I hope, that's ok? Of course, feel free to change my changes!
Right. Though, afterwards I noticed that the bug obviously had already
been fixed when I reported it; only the online Documentation is slightly
outdated. Sorry for the unnecessary uproar!
Greetings,
Juergen
On Mon, 23 Oct 2006, Phillip Kirlin wrote:
All,
Just thought I'd echo this senti
By the way, to make site/news.ihtml result in valid HTML 4.01 again, I
guess the unencoded "&" characters in the Bugfixes href attribute values
should be replaced with "&" or "%26" (untested)?
Greetings,
Juergen
On Mon, 23 Oct 2006, Han-Wen Nienhuys wrote:
CVSROOT:/cvsroot/lilypond
M
"elegant input format" and "hard for other programs to parse" sounds
somewhat like a contradiction. Maybe "sophisticated" instead of
"elegant" would be more appropriate?
I am not sure about capitalization in English language, but shouldn't
* all words in the headline except "than" start wit
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Werner LEMBERG escreveu:
Consider the test file apply-output.ly. During `make web', extended
debugging is active, and processing the file gives this warning:
programming error: Grob `NoteHead' has no interface for property `text'
continuing, cro
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Juergen Reuter escreveu:
One theoretical solution would be to introduce a new "ligatureheads.cc"
file instead of using the "noteheads.cc" functionality. However, it turned
out that almost all of the functionality of noteheads.
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
The formatting backend doesn't use subclassing at all, except for the spanner
vs. item distinction. Therefore, subclassing by definition is the wrong
approach. How to organize code should be decided by looking which code is
shared. This is easiest to
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Juergen Reuter escreveu:
Ok, this may work provided that there is no code elsewhere in lily that
receives grobs, looks into them and does some things if and only if this
grob is a NoteHead. Otherwise, this code would not apply to ligature
heads
On Mon, 6 Nov 2006, Juergen Reuter wrote:
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Without knowing the details, I think it is easiest to define a
LigatureNoteHead or XLigatureNoteHead, and a XxxxLigature in
define-grobs.scm. (X = Gregorian, Vaticana, Coherent, Mensural)
By
1 - 100 of 402 matches
Mail list logo
