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?
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
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,
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
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
==
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
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
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 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
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 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
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
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
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
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
[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
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
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
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 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
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
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,
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
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
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
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
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
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
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
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
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
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 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
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, 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
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
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
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
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 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
... 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
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
Ok, then I will apply your noteheads as "petrucci" style (hopefully, I
will be able to spend some time this evening). What about the remaining
durations (maxima, ...) for petrucci style? I guess, they should be the
same as for mensural style? Anyway, this can easily be changed in the
find-not
On Wed, 4 May 2005, Pal Benko wrote:
Hi Jürgen,
What I do not understand, if you want neo-mensural noteheads, why not just
doing "\override Voice.NoteHead #'style = #'neomensural"?
As far as I can see, the main difference between neomensural and mensural
notehead are (besides the different paramete
I think I already proposed this feature request, but anyway:
When \addlyrics or \lyricsto is used, but the user nevertheless provides
durations along with the lyrics, maybe lily should just spit out a warning
saying that the durations will be ignored.
Greetings,
Juergen
On Sat, 7 May 2005, Erik S
Hi, Pal!
On Wed, 20 Apr 2005, Pal Benko wrote:
Hi all,
attached is a patch with changed mensural noteheads.
...
fet_beginchar("Mensural open head","s0mensural")
- draw_diamond_head (staff_space#, 0.15, 0.30, 30, true);
+% draw_diamond_head (1.8 staff_space#, 0.15, 0.40, 30, true);
+
Hi, Benko!
I have finally (sorry for the extremely long delay!) applied your patch,
slightly modified, for using a constant thickness of horizontal lines in
flexa shapes (rather than using the thickness property). I still feel
somewhat uncomfortable with this solution, as the property thickness
Sorry, should now be more clearly separated:
2005-04-28 Pal Benko <[EMAIL PROTECTED]>
* lily/mensural-ligature.cc (brew_flexa): apply thickness property
only on vertical lines of flexa shape, and use a constant
thickness value for horizontal lines (patch slightly modified
Hi!
Just wondering: is there anyone else from this list except me going to the
Linux Audio Conference in Karlsruhe/Germany?
Greetings,
Jürgen
Citation from Linux Audio Developers List:
--
From: Frank Neumann <[EMAIL PROTECTED]>
Date: Tue Apr 12 2005 - 04:2
IIRC, volume is controlled on per-note basis (attack and release; passed
as value parameter to each note on/off command), such that this approach
would not impose any problems. However, almost all other parameters, such
as pitch bend (important for tuning of micro tones), are channel messages,
On Mon, 14 Mar 2005, Laura Conrad wrote:
"JR" == Juergen Reuter <[EMAIL PROTECTED]> writes:
JR> may I suggest to add a 'packed' option to lilypond-book? This could
JR> help enhancing some of the ancient notation examples in the
JR> documentation.
On Sun, 27 Feb 2005, Benkõ Pál wrote:
2005-02-27 Pal Benko <[EMAIL PROTECTED]>
* lily/mensural-ligature.cc (brew_flexa):
make flexa parts of ligatures look more similar to square parts
Hi, Pál!
Currently, the thickness property of the flexa shape aplies to all
segments of the out
Hi,
may I suggest to add a 'packed' option to lilypond-book? This could
help enhancing some of the ancient notation examples in the documentation.
Greetings,
JürgenIndex: ChangeLog
===
RCS file: /cvsroot/lilypond/lilypond/ChangeLog,
Hi, Pál!
I am sorry for responding so late: last week not only I was in bad health,
but also my (quite old) linux installation, which finally broke down, such
that I had to install a new distribution. I am still working on getting
things running again, but I am quite confident that I will be ab
This bug was fixed roughly a week ago before the release of 2.5.12, but
the lilypond web site often does not 100%ly reflect the version that it
shows in the green box on the bottom of the page (obviously, the
.ly-snippets of the web site are only partially recompiled for each new
release). Ho
Hi,
just noticed:
* buildscripts/mf-to-table.py contains the line:
name = re.sub ('-', 'M', name)
This substitution may be necessary for some parts of the backend,
but it is also applied to the font table in appendix C.3 of the manual,
which AFAICS is wrong (at le
On Mon, 21 Feb 2005, Giancarlo Niccolai wrote:
> ...
>
> However, (at least here in Italy), (X) note heads are also used in the voice
> line to express "parlato" (spoken) sections where the singer must follow a
> certain rythm, instead of just freely speak.
>
Not only in Italy. ;-) I have see
On Tue, 15 Feb 2005, Benkõ Pál wrote:
> ChangeLog:
> 2005-02-15 Pal Benko <[EMAIL PROTECTED]>
>
> * lily/mensural-ligature-engraver.cc:
> * lily/mensural-ligature.cc:
> * lily/include/mensural-ligature.hh: new algorithm implemented
>
> * scm/define-grob-properties.scm
Try "update -d".
Greetings,
Jürgen
On Sun, 20 Feb 2005, Pedro Kröger wrote:
>
> Hi,
>
> Any clues why "cvs up" doesn't create a ttftool directory?
>
> I have this in my ~/.cvsrc :
>
> log -N
> diff -u
> update -P
> checkout -P
> cvs -z3
>
> I checked out the code from scratch anyway, but
Maybe I am wrong, since I am not sure what SCM_ASSERT_TYPE does, but I
think there is a tiny bug (see attached patch).
Greetings,
JürgenIndex: lily/duration-scheme.cc
===
RCS file: /cvsroot/lilypond/lilypond/lily/duration-scheme.cc,
On Thu, 17 Feb 2005, Erlend Aasland wrote:
> On Thu, 17 Feb 2005 02:13:54 +0100, Han-Wen Nienhuys <[EMAIL PROTECTED]>
> wrote:
> > * I'd almost be tempted to either make a smob, or use a vector.
> Hmmm, I'll have to look more into smobs...
>
> > * don't forget about the svg and tex backends.
On Tue, 15 Feb 2005, Benkõ Pál wrote:
> ChangeLog:
> 2005-02-15 Pal Benko <[EMAIL PROTECTED]>
>
> * lily/mensural-ligature-engraver.cc:
> * lily/mensural-ligature.cc:
> * lily/include/mensural-ligature.hh: new algorithm implemented
>
> * scm/define-grob-properties.scm
On Sun, 26 Dec 2004, Werner LEMBERG wrote:
> > However, I suppose we will still need some glue scripting, though.
>
> What do you mean with `glue scripting'?
>
> > Also, I have the impression (not sure, though) that the parmesan
> > files will need a lot more work, since they use shaped pens.
Hi,
what about specifying paper size, layout, global staff size, etc. in a
separate file, say defs.ly, and \include it at the very beginning of the
actual score file? This file would then serve as a kind of (very
primitive) style sheet. You still could override e.g. global staff size
immedi
On Thu, 13 Jan 2005 [EMAIL PROTECTED] wrote:
> ...
> And another, section 5.16.3
>
> "Use the style property of grob Rest to select ancient accidentals."
>
> Surely you mean "rests" not "accidentals"?
Yes, good catch! Unluckily, I currently haven't access to a working
repository; so anyone
On Fri, 7 Jan 2005, Mats Bengtsson wrote:
> ...
>
> Now I realize that you did this to get an example of how to use \tag.
> Still, the problem is that it doesn't really show any advantage (as
> far as I can see). Can't we find a better example where the command
> gives a clearer advantage?
>
>
On Thu, 16 Dec 2004, Jan Nieuwenhuizen wrote:
> ...
> > What I am going to add in the next days is the tag (no
> > as MediaWiki doesn't support attributes for
> > extensions), and the support for more than one page of output.
>
> Is this the right approach? Maybe you could (still) try to dis
On Sun, 12 Dec 2004, Han-Wen Nienhuys wrote:
> --- lilypond/lily/vaticana-ligature-engraver.cc:1.32Fri Dec 10 23:16:22
> 2004
> +++ lilypond/lily/vaticana-ligature-engraver.cc Sun Dec 12 23:36:47 2004
> @@ -395,29 +395,29 @@
> String glyph_name;
> if (prefix_set & VIRGA)
>
On Sat, 11 Dec 2004, Han-Wen Nienhuys wrote:
> - Font_metric *f = 0;
> - if ((name.left_string (4) == "feta")
> + Font_metric *f = find_otf (name);
> +
> +
> + if (!f &&
> + (name.left_string (4) == "feta")
>|| (name.left_string (8) == "parmesan")
>|| (name.left_string
On Wed, 1 Dec 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Hi!
> >
> > Just wondering: wouldn't it me more consistent to rename "\line" into
> > "\row"? Then we have "\column" and "\row" as a complementary pair of
> > commands.
> >
> > Since there is currently a "word-space
Hi!
Just wondering: wouldn't it me more consistent to rename "\line" into
"\row"? Then we have "\column" and "\row" as a complementary pair of
commands.
Since there is currently a "word-space" property for "\line", maybe there
should be an according property for "\row" for vertical spacing.
Hi!
On the lilypond.org website, in section 5.11.7 of the notation manual,
version 2.5.2, ambitus does not show noteheads. Maybe, this is also
related to the introduction of the symmetric/up/down noteheads in 2.5.2?
BTW., not only my Latin dictionary, but also Webster's says that the
plural o
ximahead");
(i.e. "s" after "-"),
but also:
fet_beginchar("Mensural longa notehead", "s-2mensural", "mensurallongahead");
(i.e. "s" before "-").
So, what's the intended syntax?
Greetings,
Jürgen
On Sun, 28 Nov
The vertical line of the current G clef is slightly bent (as in 19th
century prints, AFAIK), while it was almost straight (as in modern prints)
in former versions of lily.
Greetings,
Jürgen
On Mon, 29 Nov 2004, Mats Bengtsson wrote:
> I can't see any difference compared to the default G clef
On Sat, 27 Nov 2004, Erik Sandberg wrote:
> On Friday 26 November 2004 23.11, Juergen Reuter wrote:
> > Hi!
> >
> > Hmmh, it seems something changed between 2.5.1 and 2.5.2 such that
> > ligatures are (once again) broken, see e.g. manual, sections 5.16.10.1 and
>
Hi!
Hmmh, it seems something changed between 2.5.1 and 2.5.2 such that
ligatures are (once again) broken, see e.g. manual, sections 5.16.10.1 and
5.16.11: some heads of the ligatures are missing. Maybe someone changed
something relevant in the parser?
Greetings,
Jürgen
_
Is the example in the user manual, section 5.16.13, sufficient?
See:
http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Figured-bass.html#Figured-bass
Greetings,
Jürgen
On Tue, 23 Nov 2004, Laura Conrad wrote:
> > "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
On Wed, 17 Nov 2004, Ralph Little wrote:
> ...
> However, I wholeheartedly agree with your assertion that the biggest
> bridge to cross is the non-mousey nature of the software, which is
> doubly large for non-techy musicians that have not encountered
> programming work. This could be tackled by
On Mon, 8 Nov 2004, Karl Hammar wrote:
> ...
>
> I have found a way to get rid of the errors.
>
> Previous run, lots of errors from make web:
>
> $ grep -i error log | wc -l
> 1359
> $
>
> New idea:
>
> $ (./autogen.sh --prefix=$HOME; make clean; make all install; .
> buildscript
Hi,
some general comments:
On Fri, 5 Nov 2004, Han-Wen Nienhuys wrote:
> ...
>
> COMMUNICATION
>
> The development team should be present at the 2005 Linux Audio
> Developers Meeting (april 2005) in Karlsruhe. This requires writing a
> paper, which I plan to do myself. Nevertheless, intereste
This is a known annoying problem (not only) with ancient notation, but
harmless. Just consider it as a reminder for the developers; see the
thread starting at:
http://lists.gnu.org/archive/html/lilypond-devel/2004-09/msg00073.html
Greetings,
Jürgen
On Sat, 6 Nov 2004, Karl Hammar wrote:
>
Hi,
IIRC, we agreed on 3 character indentation for .ly files, right? Looking
at examples.itely and notation.itely, this is currently quite
inconsistent. In particular, Werner, you have recently changed the
indentation of my mensural music transcription example in section 3.6.1
from 3 charact
On Mon, 1 Nov 2004, Carl Sorensen wrote:
> On Sun, 2004-10-31 at 16:20, Juergen Reuter wrote:
>
> > And, whenever changing feta-schrift, don't forget to clean the font such
> > that all font files will be rebuilt; otherwise, you will not see any
> > change, or t
2004, Nicolas Sceaux wrote:
> Nicolas Sceaux <[EMAIL PROTECTED]> writes:
>
> > Juergen Reuter <[EMAIL PROTECTED]> writes:
> >
> >> Hi!
> >>
> >> Maybe this is a silly question, but there is something that I do not quite
> >> underst
Hi!
Maybe this is a silly question, but there is something that I do not quite
understand. I am trying to create span events in a music function:
\version "2.4.0"
crescendo = #(def-music-function
(location music) (ly:music?)
(make-music 'SequentialMusic
If I understand you correctly, you want to add a new articulation script
(rather than patching the code for dynamic marks). That's quite easy, if
you are a little bit familiar with metafont. For that purpose, you should
* add the articulation sign to the feta font; see file mf/feta-schrift.mf
(oopsala, erroneously posted to lilypond-cvs instead of lilypond-devel;
hence here once again...)
-- Forwarded message --
Date: Fri, 29 Oct 2004 15:01:32 +0200 (CEST)
From: Juergen Reuter <[EMAIL PROTECTED]>
To: Han-Wen Nienhuys <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECT
Hi!
When using durations longer than 1 (such as \breve) in lyricmode, lily
produces illegal tex code.
Example .ly snippet:
myVoice = {
c1 c c c
}
myText = \lyricmode {
foo1 bar\breve foo1
}
\score {
<<
\context Voice = "lala" { \myVoice }
\context Lyrics = "l
Thanks, applied (since I raised the issue, I felt responsible to apply).
There still seems to be some lilypond-book problem in the input/test
directory, but at least the Documentation/user tree with your patch
compiles fine on my machine.
Greetings,
Jürgen
On Mon, 18 Oct 2004, Carl Sorensen
Hi!
In input/test/fret-diagram.ly, we have a nice fret diagram, but I can not
find any section in the manual about it (or did I miss something?). Since
the NEWS file advertises fret diagrams for the upcoming version of lily,
it would be nice to have a short section about frets in the user manu
Hi!
Seems like the current implementation of clusters is completely
incompatible with lyrics (I am not sure if my original implementation
was). For example:
\version "2.3.22"
myVoice = {
\transpose c' c'' {
\makeClusters {
}
}
}
myTex
On Mon, 27 Sep 2004, Ruud van Silfhout wrote:
> ...
> 1. In te section 'Orchestral music', subsection 'System start delimiters',
> the second example.It states there that the group is a StaffGroup, but the
> example code shows a GrandStaff.
> ...
That has been (hopefully) fixed a couple of days
Hi!
Once Score.SystemStartBracket #'transparent has been overridden to ##t, it
seems it is not possible to revert the effect. For an example, look at
section 3.4.2 in the manual (in recent CVS; this is not yet on the web
site) or, respectively, in the generated file
Documentation/user/out-www/
flex -Cfe -p -p -oout/lexer.cc lexer.ll
"lexer.ll", line 635: warning, -s option given but default rule can be matched
rm -f ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o"
g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include
-I../flower/./o
Hi!
The example templates in section 3 of the manual
(Documentation/user/examples.itely) currently contain a '\version
"2.3.16"' header. Shouldn't this header be automatically inserted when
dissecting the .itely file?
Greetings,
Jürgen
___
lilypon
On Tue, 21 Sep 2004, Han-Wen Nienhuys wrote:
> ...
> > Well, ...
> >
> > (1) There is no \unset command for grob properties (at least not that I
> > know of). Hence, I guess by "unset dash-fraction" you mean
> > "\override TextSpanner #'dash-fraction = #'()"? At least, this trick
>
Hi!
In section 5.3.8 of the manual ("Bar lines"), the last \mark in the second
figure (lily-1457749936.ly) does not show up: there should be a ":"
printed above the rightmost dotted bar line.
Greetings,
Jürgen
___
lilypond-devel mailing list
[EMAIL
On Tue, 21 Sep 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> >
> >
> > On Fri, 17 Sep 2004, Han-Wen Nienhuys wrote:
> >
> > > [EMAIL PROTECTED] writes:
> > > > else
> > > > {
> > > > return make_line (thick, from, to);
> > > > }
> > > >
> > > >
> > > > Are you
Section 7.1.5 ("Changing context default settings") contains twice the
line:
\override Stem #'thickness
I guess, this should be
\override Stem #'thickness = #2.0
or something alike, right?
Greetings,
Jürgen
___
lilypond-devel ma
On Fri, 17 Sep 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > else
> > {
> > return make_line (thick, from, to);
> > }
> >
> >
> > Are you sure that the "else" branch (i.e. making a solid line) should be
> > regardless of the "style" property entered only if "sc
101 - 200 of 402 matches
Mail list logo
