Re: skyline vs. y-aligned-side
On 1/27/07, Johannes Schindelin [EMAIL PROTECTED] wrote: Hi, Sorry, I missed that question. The easiest solution is: git commit --amend This command allows you to edit the command message. If you forgot a file, you can add it with: git commit --amend file NOTE NOTE NOTE! You must not do this when you pushed out that commit (before amending it) to the public git repository. It disrupts the commit history, i.e. you can no longer fast-forward the public branch to the new tip. Consequently, git-fetch and git-pull would fail for tracking parties. BTW I'd be interested to know how you could commit without a message, since git-commit does not allow that... How did you do it? Thanks, I'll try that. I managed to do it because I still use cogito for committing (although I've switched to git for almost everything else) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Questions regarding creation of a new glyph (was: White diamond, black diamond, and possible small sponsorship?)
Am 23. Januar 2007, 23:55 Uhr (+0100) schrieb Han-Wen Nienhuys: A harmonic head is slightly bigger so it protudes through the staff lines, if printed in a space. AFAIK, they only exist in the open form, and Trevor's use of the black form is not canonical. There are many things not canonical in notation after the beginning of the 19th century. Therefore it's always better to have the option to use black harmonic heads (as I do all the time). -- Orm ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: proposal: second style for quartertone accidentals
Am 27. Januar 2007, 15:33 Uhr (+0100) schrieb Ole Schmidt: Hi, I did not understand if these accidentals are already implemented so that I can use them? If not, I'am interested strongly in using them, they are indeed much easier to read and to handle... No, They aren't implemented yet. This was more a poll, how many people would be interested in it, as I find the current quarter note glyphs impractical. It was also meant as a question to the developers what they think about implementing it. I don't think it is very hard to implement. -- Orm ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: proposal: second style for quartertone accidentals
On 1/27/07, Orm Finnendahl [EMAIL PROTECTED] wrote: Hi, for a while I wanted to suggest adding the option of using a different style for microtone accidentals. I personally prefer the use of up or down arrows on extended vertical lines of the standard accidentals (see attached example). The advantage of this style is a better differentiation of enharmonic spelling which makes reading and performance better suited to the way those pitches are produced on different instruments or the musical context (like in the spelling of chords). In this case an extended syntax for the accidentals would make sense. I give two examples with the different enharmonic spellings and the proposed lilypond syntax: 1. pitch: quarter tone below a glyphslilypond syntax - a with natural with arrow down aeh a with flat sign with arrow up aesih g with sharp sign with arrow up gisih 2. pitch: quarter tone above a glyphslilypond syntax - a with natural with arrow upaih a with sharp sign with arrow down aiseh b with flat sign with arrow downbeseh I designed the glyphs in a postscript font and can provide them if anybody is interested (they stem from a very old version of the Petrucci font and probably will have to get adjusted to the more beautiful Feta glyphs, but the basic work is done). What do you think? Question: would it be possible to have access to *both* sets of glyphs? It seems to me that I've seen both types of glyphs mixed together in single scores; usually the existing quartertone glyphs show exact quartertone alterations while the arrowed glyphs show approximate alterations. I actually had never considered substituting arrowed-accidetals for the existing glyphs, but thinking about it now I can see exactly why you would want to do so ... they really do have a cleaner look ... So, I definitely vote for the incusion of the new arrowed-accidentals and, if possible, I'd like to continue to have access to the existing quartertone accidentals for use at the same time. (I don't know what this says about the input syntax, though ...) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: proposal: second style for quartertone accidentals
Am 27. Januar 2007, 12:06 Uhr (-0600) schrieb Trevor Bača: Question: would it be possible to have access to *both* sets of glyphs? It seems to me that I've seen both types of glyphs mixed together in single scores; usually the existing quartertone glyphs show exact quartertone alterations while the arrowed glyphs show approximate alterations. Well, my proposal meant to be completely backwards compatible. I thought about something similar to the notehead-style property like saying \override #'accidental-style = arrowed for getting the arrowed accidentals and \revert #'accidental-style for switching back. -- Orm P.S.: Actually there are existing other styles (the three-quarter flat normally is written with a normal flat sign and a mirrored flat; sometimes a black (filled) flat sign is used to indicate quarter tones, sometimes exactly this notation is used for indicating eighth tones in combination with lilyponds default signs for quartertones etc...) That's one of the reasons I always found the arrows most clear (in combination with arrows without accidentals for indicating eigth tone alterations...) But I don't want to open yet another bike-shed; i would just like to get my preferred style available... ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for new harmonic glyph
If you feel comfortable with it this way
it might be good to update the docs, too (probably adding two sample
bars to note-head-style.ly in the regression tests would suffice). If
you wish I can try to do that later on.
please do.
Here it is. Sorry that it took me so long to submit only a few
additional lines of code. I just wanted to make sure not to miss any
other locations in the docs where a reference to the new styles would
make sense.
In addition, I had a problem with make web when trying to verify the
changes (the file input/typography.ly fails to compile). I am now even
tempted to think that it is a bug in the latest git version because even
the most simple file containing only a few notes fails to be processed
with the freshly compiled v2.11.15 from git (it took me some time to
find that out). But I haven't had time to figure out yet what exactly
causes the error.
Cheers
Max
From f35db04c340cdc55eacf613cbcdc0ffe86a9d0ee Mon Sep 17 00:00:00 2001
From: Maximilian Albert [EMAIL PROTECTED]
Date: Sat, 27 Jan 2007 18:34:26 +0100
Subject: [PATCH] add new notehead styles 'harmonic-black' and 'harmonic-mixed'
to docs (in regression tests)
---
input/regression/note-head-style.ly | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/input/regression/note-head-style.ly
b/input/regression/note-head-style.ly
index b5164e9..c561eec 100644
--- a/input/regression/note-head-style.ly
+++ b/input/regression/note-head-style.ly
@@ -61,6 +61,16 @@ pattern =
\break
+ \override Staff.NoteHead #'style = #'harmonic-black
+ s1*0^\markup { harmonic-black }
+ \pattern
+
+ \override Staff.NoteHead #'style = #'harmonic-mixed
+ s1*0^\markup { harmonic-mixed }
+ \pattern
+
+ \break
+
\override Staff.NoteHead #'style = #'diamond
s1*0^\markup { diamond }
\pattern
--
1.4.4.4
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: proposal: second style for quartertone accidentals
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 through scheme code, as is done with notehead style in the scheme function note-head::calc-glyph-name in file scm/output-lib.scm. ... Ooops, I just recognized that accidental handling obviously has changed during the last two months. Accidentals are now indeed handled via scheme; see scm/output-lib.scm for details. Greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Git help
Trying to get a copy of jneemans branch to try out the new page breaking and score stretching stuff. I clone the repository with $ git clone git://git.sv.gnu.org/lilypond.git Then I create .git/remotes/jneem containing URL: git+ssh://[EMAIL PROTECTED]/srv/git/lilypond.git Push: refs/heads/jneeman:refs/heads/jneeman Pull: refs/heads/jneeman:refs/heads/jneeman But when I then do $ git pull jneem I get conflicts in lily/page-breaking.cc and lily/text-spanner-engraver.cc What do I do wrong? -Rune ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
