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 for
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 them
Very nice, I like the structure and your explanatory add-ons! Just a
few nitpicking comments:
* 2.8.3 (Typesetting mensural music): There are no rests in Gregorian
chant notation; instead, it uses Divisiones. I would have expected this
statement to appear somewhere in 2.8.4 (Typesetting
On Wed, 24 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote:
I'm working on the docs for ancient music,
Nice to hear!
3. The form Episem is used, both as a lilypond command and in the
documentation text. Since it's not really a medieval concept at all, but a
term invented by the Solesmes
On Thu, 25 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote:
It is mentioned as one of the known issues in the ancient section of the
documentation that The episema line is not displayed in many cases. That
in itself does not make it very useful, but it's doubly bad when it doesn't
even show up
To all,
also my condolences to all of Rune's family and friends.
I fully agree with at least dedicating a lily version to him!
Sad greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On Mon, 11 Feb 2008, Robert Memering wrote:
Am Montag, 11. Februar 2008 16:36 schrieb Juergen Reuter:
IIRC, the spacing engine maintains a variable that keeps track of shortest
available duration in a peace in computes the ideal distance of larger
note values in a logarithmic scale based
Hi all,
as far as I understand, all problems with incipits boil down to the
following two major issues:
(1) horizontal spacing, and
(2) the system start delimiter.
Karl's solution unfortunately leaves horizontal space between the incipit
and the actual score; hence it does *not* solve
On Sat, 2 Feb 2008, Nicolas Sceaux wrote:
...
Anyway, wouldn't it be nicer to have some kind of scheme macro that expands
to code that prints an incipit? Your first clef could then be just part
of the incipit that the macro creates. And maybe the clef's name either
could passed as
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
On Sun, 28 Oct 2007, Paco Vila wrote:
El Sat, 20 de Oct de 2007, a las 11:45:28AM -0200, Han-Wen Nienhuys dijo:
IIRC the real problem is the limits that MIDI imposes (IIRC: you can
have only 15 channels/track);
They are 16, numbered from 1 to 16 (conventionally) but coded 0 to 15 in binary.
Hi,
by the way, when creating the ancient font many years ago, I added
documentation in a similar vein which is now at the top of the files
parmesan-clefs.mf and parmesan-heads.mf, but is also valid for the feta
font. I guess this docu could also be moved to the README file. However,
the
On Tue, 25 Sep 2007, Han-Wen Nienhuys wrote:
2007/9/25, Rune Zedeler [EMAIL PROTECTED]:
+ int octave_;
+ int notename_;
+ Rational alteration_;
Why don't you use a Pitch object for this combination? You would get
Scale* for free.
Primarily because the two values octave_ and has_octave_
On Fri, 21 Sep 2007, Graham Percival wrote:
I've updated the README.txt with more guidelines about writing/maintaining
documentation. I'll be asking the GDP Helpers to fix any Section organiztion
and Formatting issues, as well as any Readability or Technical writing issues
they feel
On Wed, 19 Sep 2007, Till Rettig wrote:
...
Sounds great! I am really unhappy with the German translation for the binary
(e.g. ligature is translated as Bindung (sic!)).
...
Ouch, I did not recognize that one yet! (Maybe that's why/because the
default language on my machine is set to
On Tue, 18 Sep 2007, Reinhold Kainhofer wrote:
...
Fortsetzung, die Finger kreuzen
Segmentation fault
By the way, I guess a proper translation of crossing fingers into
German would be something like Daumen druecken... Till, what do
you think?
Greetings,
Juergen
Just for the record:
Ancient notation _could_ be split genre-wise into two separate chunks
Gregorian Chant and Mensural Notation. However, for a _reference_
manual, I think it is ok as it currently is (e.g. having a single section
on ligatures rather than separate ones per genre). For a
On Fri, 14 Sep 2007, Jonas Nystr�m wrote:
As I reviewed the website, I thought that perhaps something as simple as
replacing the photograph of the pond with a beautifully-engraved piece of
complex music might improve the first impression.
Carl Sorensen
Exactly! The site should communicate
OK. This is a first draft. (but we can just use the character, as Rune
suggested)
Very nice! It's IMO the best choice for a lily logo that I have seen so
far.
Greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2007/9/11, Till Rettig [EMAIL PROTECTED]:
Hello,
For instance I could imagine
a chapter Ancient music, and one on educational subjects. At least I
don't see why Ancient is instrument specific, so why not put it in 7
from the current suggestion, right after educational and special noteheads.
On Mon, 10 Sep 2007, Graham Percival wrote:
To summarize some discussions:
...
- Does anybody _like_ the current layout? If so, speak up now or forever
hold your peace. :)
I am _fine_ with the current layout. However, I agree that for
global searching in the web browser, you need a
Hi all,
while you are at it (I mean, the placement/spacing code, though I am not
sure if this is anyhow related)...
I noticed that in Manual Sect. 7.7.10.2 (Gregorian square neumes
ligatures) the placement of the letters in the neumes table changes from
almost each version of the lily
On Fri, 17 Aug 2007, Elie Roux wrote:
Hello,
I'm the developper of gregorio (http://home.gna.org/gregorio/), a software under
GPLv3. I would like to integrate the font parmesan in it, and redistribute the
font under GPLv3. But I can't find in the site or in the source if the files are
GPLv2
From: Juergen Reuter [EMAIL PROTECTED]
Date: Thu, 2 Aug 2007 17:46:54 +0200
Subject: [PATCH] * Bugfix: correct order in accidentals glyph-name-alist
---
scm/output-lib.scm | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/scm/output-lib.scm b/scm/output-lib.scm
Sorry for this late answer, but I am still overloaded with work... :-(
On Wed, 11 Jul 2007, Joe Neeman wrote:
On Wednesday 11 July 2007 17:18, Werner LEMBERG wrote:
Joe,
your latest changes break the \augmentum stuff in Gregorian notation.
(Do a search for `augmentum' and compare the
FYI: There are vague chances, that in 2008 I will be able to schedule a
little bit more of my time for lilypond again. ;-)
Greetings,
Juergen
On Wed, 28 Mar 2007, Graham Percival wrote:
About six months ago, there was discussion about a priority level below
low; at the time I argued
On Mon, 19 Mar 2007, Kevin Dalley wrote:
...
The G clef is correct, if you change your interpretation a bit. It
confused me for quite a while also. The documentation needs to be
improved, but I haven't figured out exactly how.
The G-clef is centered around the G note. The center of the
Hi, all!
Just a few comments:
Actually, binding the origin to a staff line (e.g. the most lower staff
line) rather than to the center of the origin (as we currently do) would
solve the current problem that you have to design clefs explicitly either
for staves with an even number of staff
Hi, all!
What about unifying \paper and \layout into a single \layout
directive, such that in the input language there is no syntactical
difference any more between \paper and \layout block? (Of course, in the
implementation, the different scopes still could be kept.) Then the place
where
Nope, not a bug. The problem is that characters in http references
must be escaped (I think by amp;).
Greetings,
Juergen
On Thu, 1 Feb 2007, Bertalan Fodor wrote:
I think that's a bug in the validator :-)
Bert
Korneel írta:
This little note, only to say that your current homepage does
On Thu, 1 Feb 2007, Till Rettig wrote:
Hei,
I am slowly evolving in my ideas and trials on the ancient fonts for
lilypond. So far I have a couple of good scans from which I would like to
take the shapes. But how is the best to get them into metafont? I found
something about mfpic (probably
On Mon, 29 Jan 2007, Han-Wen Nienhuys wrote:
. So it seems that the use of Accidental #'style is deprecated and one
should set the alteration-alist directly. (But changing the style
property still works in v2.11.13, even if I don't know why, given that I
couldn't find the code handling it).
On Sun, 28 Jan 2007, Juergen Reuter wrote:
...
Unfortunately, the code for checking and handling the Accidental style
property is still hardcoded in lily/accidental.cc in method
string
Accidental_interface::get_fontcharname (string style, int alteration)
rather than being handled at runtime
On Tue, 16 Jan 2007, Till Rettig wrote:
Hei,
I was wondering if I could start some contribution to the medieval
notation support
That would be great!
via redesigning the fonts that in my opinion don't look
very good. Especially referring to the mensural notehead style (I think
the petrucci
On Thu, 21 Dec 2006, John Mandereau wrote:
...
doctype = '!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01
Transitional//EN\n'
s = doctype + s
Does the 'EN' means that the page language is English? If so, it should
be modified to handle pages of any language.
No. The
I don't know, if this matters, but in ancient notation, there definitely
is an ij ligature (as well as an IJ ligature) that is quite often
used as a textual repetition directive in lyrics. I hope the according
definitions at the very beginning of ly/gregorian-init.ly will still work
and
On Fri, 15 Dec 2006, Werner LEMBERG wrote:
I don't know, if this matters, but in ancient notation, there
definitely is an ij ligature (as well as an IJ ligature) that is
quite often used as a textual repetition directive in lyrics. I
hope the according definitions at the very beginning of
Actually, as far as I can see, it was not a repeat, but a delay of one
week. Maybe you were not subscribed to this list when you sent it, and it
was therefore sent to the list moderator for manual approval.
Anyway, it's nothing to worry about. ;-)
Greetings,
Juergen
On Thu, 7 Dec 2006, Monk
On Thu, 30 Nov 2006, Monk Panteleimon wrote:
On Thursday 30 November 2006 06:01, you wrote:
Hello, Panteleimon!
Hello, thank you for your response
I fear the task of fully implementing kievan chant notation is more than
just a question of adding thirteen glyphs.
recognize at least pes
Maybe the real point here is that for almost all glyphs we want to have a
_convex_ outline (such that e.g. stems do not extend into glyphs) rather
than a tight skyline?
On Tue, 14 Nov 2006, Han-Wen Nienhuys wrote:
Werner LEMBERG escreveu:
I'm not sure whether an automated process really
On Tue, 14 Nov 2006, Werner LEMBERG wrote:
...
I've already `converted' all symbols except the one for ancient
notation -- Jürgen, do you have time to work on improving the glyph
shapes of the ancient notation so that mf2pt1 produces sensible
results?
Mmmh, looks currently really bad: during
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
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,
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 with a
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 amp; or %26 (untested)?
Greetings,
Juergen
On Mon, 23 Oct 2006, Han-Wen Nienhuys wrote:
CVSROOT:/cvsroot/lilypond
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
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!
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:
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-expression (any
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'
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/bin/../share/lilypond
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
}
the
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 c c c c c c c c c c c
type.)
I guess, such a function 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
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
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
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 and
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, historically
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
for details
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
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 colliding
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,
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
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
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 gn =
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
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 second thought, not the u
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 (
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
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
___
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
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
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: Mats Bengtsson
Cc: lilypond-devel@gnu.org
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
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,
please note
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 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
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
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 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:
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?
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
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
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
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
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
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
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
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
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
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
1 - 100 of 301 matches
Mail list logo
