64-bit font problems in GUB

2014-01-23 Thread Simon Bailey
Hello, I kicked this thread off last week sometime: http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00762.html TL/DR summary: ligatures were not being shown for lilypond-generated output. further investigation led me to:

Re: 64-bit font problems in GUB

2014-01-23 Thread Phil Holmes
- Original Message - From: Simon Bailey si...@bailey.at To: lilypond-user Mailinglist lilypond-user@gnu.org Sent: Thursday, January 23, 2014 9:20 AM Subject: 64-bit font problems in GUB Hello, I kicked this thread off last week sometime:

Re: Non-standard notation challenges (no game this time...)

2014-01-23 Thread Phil Holmes
- Original Message - From: Urs Liska u...@openlilylib.org To: lilypond-user lilypond-user@gnu.org Sent: Wednesday, January 22, 2014 11:59 PM Subject: Non-standard notation challenges (no game this time...) Hi all, I'm facing some notation challenges that aren't part of a self-devised

When was dot notation for dotted property paths added?

2014-01-23 Thread Urs Liska
Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the commit(s). Concretely, I have a snippet that

Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc

2014-01-23 Thread Phil Holmes
- Original Message - From: David Kastrup d...@gnu.org To: MING TSANG tsan...@rogers.com Cc: lilypond-user mailinglist lilypond-user@gnu.org Sent: Thursday, January 23, 2014 2:15 AM Subject: Re: bar-check warning when generating rehearsal midi soprano, alto,tenor etc MING TSANG

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread David Kastrup
Urs Liska u...@openlilylib.org writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread David Kastrup
Urs Liska u...@openlilylib.org writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. 2.17.6, URL:http://code.google.com/p/lilypond/issues/detail?id=2883 -- David Kastrup

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Peter Bjuhr
On 01/23/2014 10:40 AM, Urs Liska wrote: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of the right search terms to locate the

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Noeck
Hi Urs, why not just test it? It works for 2.17.9 so it should with .10, too: \version 2.17.9 { \override Stem.length = #30 a } Cheers, Joram Am 23.01.2014 10:40, schrieb Urs Liska: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread David Kastrup
Peter Bjuhr peterbj...@gmail.com writes: On 01/23/2014 10:40 AM, Urs Liska wrote: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Urs Liska
Am 23.01.2014 10:52, schrieb Noeck: Hi Urs, why not just test it? It works for 2.17.9 so it should with .10, too: \version 2.17.9 { \override Stem.length = #30 a } Cheers, Joram Maybe I'm somewhat selfish, but I only have 2.17.3 and 2.17.96 still present, and I thought asking here

Re: [SPAM] Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Urs Liska
Am 23.01.2014 10:47, schrieb David Kastrup: Urs Liska u...@openlilylib.org writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. 2.17.6,

Re: [SPAM] Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Urs Liska
Am 23.01.2014 10:50, schrieb David Kastrup: Urs Liska u...@openlilylib.org writes: Somewhere in 2.17. David introduced the change from \override Stem #'length to \override Stem.length I would like to know in which LilyPond version this appeared. Somehow I don't seem to be able to think of

Re: When was dot notation for dotted property paths added?

2014-01-23 Thread Peter Bjuhr
On 01/23/2014 10:52 AM, David Kastrup wrote: Peter Bjuhr peterbj...@gmail.com writes: Could it be this: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=680df85187d0f3862b1ef1cf7a14f8ad7b7f0ee9;hp=ee89ee2c8ee328ec261b822aa9e260c9d623c086 No. Sorry! Probably followed an

Re: 64-bit font problems in GUB

2014-01-23 Thread Simon Bailey
On Thu, Jan 23, 2014 at 10:36 AM, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Simon Bailey si...@bailey.at ...SNIP SNAP... This leads me to conclude that there seems to be a problem with the 64-bit version of the font libraries in the build system for the release

Hatches

2014-01-23 Thread Urs Liska
Hi, I never worked with that kind of stuff, so I'd like to get some feedback and hints _before_ digging into the docs myself. So I explicitly don't expect ready solutions, just a few comments if my approach would be right. I'm looking for a way to typeset hatched cancellations in manuscripts

Re: [SPAM] Re: Non-standard notation challenges (no game this time...)

2014-01-23 Thread Urs Liska
Am 23.01.2014 10:39, schrieb Phil Holmes: The problem I would have when presented with this music is that I would have no idea - not a clue - about what the writer of the music intended with this notation. Is it explained anywhere? Without that, it seems rather pointless to try to reproduce

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
Hi, On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley thomasmorle...@gmail.comwrote: Below some coding just to show that it can be done. It's a very first sketch, several issues are present (p.e. linebreak) Might be a starting point, though. There's also the attached file (which comes from

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
Hi again, On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik david.nales...@gmail.comwrote: Hi, On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley thomasmorle...@gmail.comwrote: Below some coding just to show that it can be done. It's a very first sketch, several issues are present (p.e.

Re: frescobaldi macports broken after update

2014-01-23 Thread Davide Liessi
2014/1/18 Davide Liessi davide.lie...@gmail.com: I'll let you know when the patch will be commited. The patch is now in MacPorts. Enter in the Terminal sudo port selfupdate sudo port upgrade outdated and you'll get a working Poppler installation and a working Music View in Frescobaldi. Best

Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc

2014-01-23 Thread MING TSANG
1- I now put spaces to the .ly code 2- my original score has 129 measures; I thought cut it down to 24 will show the warning barcheck error -- now I cut it down to 13 3-  I updated S1*0\f  with \f and I still have the same barcheck warning. Here is the updated test-midi.ly Starting

Re: frescobaldi macports broken after update

2014-01-23 Thread Stan Sanderson
Davide, Once again, many thanks for your support of Frescobaldi through MacPorts. Stan On Jan 23, 2014, at 6:35 AM, Davide Liessi davide.lie...@gmail.com wrote: 2014/1/18 Davide Liessi davide.lie...@gmail.com: I'll let you know when the patch will be commited. The patch is now in

Re: [SPAM] Re: Non-standard notation challenges (no game this time...)

2014-01-23 Thread Keith OHara
Urs Liska ul at openlilylib.org writes: The point in the edition of such snippets is to _document_ the actual state of a manuscript. This isn't _music_ but rather a remainder from the compositional process. Comparing this with later states allows an editor to draw conclusions on the

ekmelily- support fo microtonal notation in lilypond

2014-01-23 Thread Stefan Thomas
Daer community, for those who are interested in microtonal music and its notation: You should have look at http://www.ekmelic-music.org/en/ekmelily.htm it supports microtonal music notation in Lilypond. It also works with Linux (I've tested it) and it runs with Lilypond 2.18.! Stefan

Re: bar-check warning when generating rehearsal midi soprano, alto, tenor etc

2014-01-23 Thread Jan-Peter Voigt
Hi MING TSANG, I think, there is just a typo. You give \sopranoVoiceI as last argument lyrics to the rehaersalMidi function. But that is the melody. \verseSopranoVoiceI are the lyrics. I changed that and the barcheck erros disappeared. HTH Jan-Peter On 23.01.2014 16:08, MING TSANG wrote: 1- I

Re: Non-standard notation challenges (no game this time...)

2014-01-23 Thread Urs Liska
Am 23.01.2014 16:56, schrieb Keith OHara: Urs Liska ul at openlilylib.org writes: The point in the edition of such snippets is to _document_ the actual state of a manuscript. This isn't _music_ but rather a remainder from the compositional process. Comparing this with later states allows an

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik david.nales...@gmail.comwrote: There's also the attached file (which comes from http://www.mail-archive.com/lilypond-devel@gnu.org/msg47432/shape-tie-columns.ly) which will work with broken ties. Here are some more useful values:

Fw: lilypond-user Digest, Vol 134, Issue 154

2014-01-23 Thread MING TSANG
  4. Re:bar-check warning when generating rehearsal midi soprano,       alto,    tenor etc (Jan-Peter Voigt) Message: 4 Date: Thu, 23 Jan 2014 16:58:33 +0100 From: Jan-Peter Voigt jp.vo...@gmx.de To: lilypond-user@gnu.org Subject: Re: bar-check warning when generating rehearsal midi

\set Score.midiPanPosition

2014-01-23 Thread Jim Long
On Tue, Jan 21, 2014 at 04:09:38PM +1100, Vaughan McAlley wrote: On 20 January 2014 07:09, Colin Campbell c...@shaw.ca wrote: \set Score.midiPanPosition = #RIGHT \set Staff.midiPanPosition = #LEFT This is missing in the 2.18 changes, so I didn???t know about it until now. Very nice!

Re: \set Score.midiPanPosition

2014-01-23 Thread Vaughan McAlley
On 24 January 2014 14:06, Jim Long lilyp...@umpquanet.com wrote: On Tue, Jan 21, 2014 at 04:09:38PM +1100, Vaughan McAlley wrote: On 20 January 2014 07:09, Colin Campbell c...@shaw.ca wrote: \set Score.midiPanPosition = #RIGHT \set Staff.midiPanPosition = #LEFT This is missing in the

Re: frescobaldi macports broken after update

2014-01-23 Thread Henning Hraban Ramm
Am 2014-01-23 um 20:35 schrieb Davide Liessi davide.lie...@gmail.com: The patch is now in MacPorts. Great, it works again! Thank you (all of you) very much! I have two little complaints with Frescobaldi on OSX, that didn’t change in all the versions I tried: - If I start the program by