Re: Annotate and Lilyglyphs

2015-02-08 Thread Craig Dabelstein
Hi Urs,

[1] I have moved to Git.

[2] The new method of using ScholarLy is all working (when I engrave
through Frescobaldi), but it does give me these warnings first:

openLilyLib: library infrastructure successfully loaded.


Interpreting music...[8][16][24]

warning: openLilyLib:

context property: #f

warning: openLilyLib: actual-context-id: Bassoon 2

warning: openLilyLib: context-id property: Notes

warning: openLilyLib: Resulting ctx-id: Bassoon 2


warning: openLilyLib:

context property: #f

warning: openLilyLib: actual-context-id: Baritone Saxophone

warning: openLilyLib: context-id property: Notes

warning: openLilyLib: Resulting ctx-id: Baritone Saxophone




[3] However, when I try to engrave using my Makefile I get an error:
cannot find file: `openlilylib' 


Craig



On Sun Feb 08 2015 at 9:02:14 AM Urs Liska u...@openlilylib.org wrote:


 Am 07.02.2015 um 11:37 schrieb Craig Dabelstein:

 Urs,

 I tried and failed to understand the ouput Here is the ouput error.

  Processing
 `/Users/craigdabelstein/Dropbox/Maximes_Music/French_music/Berlioz/lilypond/Score/Berlioz-01-score.ly'

 Parsing...


  openLilyLib: library infrastructure successfully loaded.


  Interpreting music...[8][16][24]

 warning: openLilyLib:

 context property: #f

 warning: openLilyLib: actual-context-id: Bassoon 2

 warning: openLilyLib: context-id property: Notes

 warning: openLilyLib: Resulting ctx-id: #t



 /Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:156:34
 http://0: In procedure string-symbol in expression (string-symbol
 ctx-id):


 /Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:156:34
 http://1: Wrong type argument in position 1 (expecting string): #t

 Exited with return code 1.


 Thanks for testing. It turned out to be a simple error in the conditional
 evaluation of the different possibilities to determine a context name. This
 shows that one should actually have a comprehensive test suite ...

 I have pushed the update to Github so you can get it from there.
 I see that you have stored openlilylib in a Dropbox folder. You really
 should consider using Git, if only for getting stuff from Github. It makes
 managing repositories like openlilylib so much cleaner ...

 Best

 Urs



 On Sat Feb 07 2015 at 7:19:25 PM Urs Liska u...@openlilylib.org wrote:


 Am 07.02.2015 um 07:54 schrieb Urs Liska:



 Am 7. Februar 2015 04:47:11 MEZ, schrieb Craig Dabelstein
 craig.dabelst...@gmail.com craig.dabelst...@gmail.com:
 Dear Urs,
 
 All good.
 
 I've followed all your instructions -- no problem.
 
 However, perhaps I'm putting \setOption
 scholarly.annotate.export-targets
 #'(latex plaintext) in the wrong place. I put this in the
 main-init.ily file, yes?
 
 When I try to engrave the score I get this error:
 
 Parsing...
 
 
 openLilyLib: library infrastructure successfully loaded.
 
 
 Interpreting music...[8][16][24]

 /Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:150:34
 0: In procedure string-symbol in expression (string-symbol ctx-id):
 

 /Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:150:34
 1: Wrong type argument in position 1 (expecting string): #t
 
 Exited with return code 1.

 This looks like a bug to me. It seems you managed to use a constellation
 I failed to check. This is in the code where the name of the context is
 determined.

 Please try with a simple example file to check whether you can get it to
 compile at all.

 Unfortunately I don't think I'll be able to work on this today at all.


  There's something you can do to debug:


- Open openlilylib/ly/scholarly/annotate/__main__.ily
- Locate the (set! annotation, should be line 145
 - Insert the following lines _before_ this line:

  (oll:warn \n\context\ property: ~a (assoc-ref
 annotation context))
  (oll:warn \actual-context-id: ~a (ly:context-id
 context))
  (oll:warn \context-id\ property: ~a (assoc-ref
 annotation context-id))
  (oll:warn Resulting \ctx-id\: ~a\n ctx-id)

 This will output like the following for each annotation:

   warning: openLilyLib:

 context property: #f

 warning: openLilyLib: actual-context-id: \new

 warning: openLilyLib: context-id property: usage-examples

 warning: openLilyLib: Resulting ctx-id: usage-examples

 Hopefully you'll get some meaningful information just before the
 offending annotation.
 If you can't find it or can't make sense of it you can also send me the
 whole console output.

 Urs


 Best
 Urs
 .
 
 Craig
 
 
 
 On Sat Feb 07 2015 at 11:23:04 AM Urs Liska u...@openlilylib.org
 u...@openlilylib.org wrote:
 
 
  Am 07.02.2015 um 00:40 schrieb Urs Liska:
 
 
  Am 07.02.2015 um 00:39 schrieb Craig Dabelstein:
 
  Hi List,
 
  Sorry for the frustrating question, but how do I combine Samuel's
 code -- @[^@]*@
  -- with an annotate message such as 

Re: Annotate and Lilyglyphs

2015-02-08 Thread flup2
The few tests I made are working fine now; the only not working thing is
the example file that still uses the former loading and options syntax.

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Annotate-and-Lilyglyphs-tp171471p171599.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Adding lyrics to basic drum beat

2015-02-08 Thread Kevin Tough
On Sat, 2015-02-07 at 13:20 +0100, Thomas Morley wrote:
 2015-02-07 11:45 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
  2015-02-07 9:30 GMT+01:00 David Kastrup d...@gnu.org:
  Thomas Morley thomasmorle...@gmail.com writes:
 
  returns:
  warning: cannot find Voice `DV'
 
   \new Lyrics
   \lyricsto DV  { One Two Three Four }
 
  Coding \layout instead of \midi (or commenting it) will show correct
  assigned lyrics, though.
 
  The context hierarchy is supposed to behave the same for all outputs (of
  course, unless you mess around with output definitions).  If it doesn't,
  that's a bug.  I propose entering it in the tracker.  I don't have a
  good idea off the bat what may be causing this behavior.
 
  --
  David Kastrup
 
  It's now issue 4281:
  https://code.google.com/p/lilypond/issues/detail?id=4281
 
  Cheers,
Harm
 
 Hi Kevin,
 
 in the light of
 https://code.google.com/p/lilypond/issues/detail?id=4281#c2
 you can do for 2.18.2:
 
 \version 2.18.2
 
 \paper { ragged-right = ##f }
 
 m =
   
 \new DrumStaff
   
\new DrumVoice \drummode { \voiceOne hh4 hh hh r hh }
\new DrumVoice = dv \drummode { \voiceTwo bd4 sn bd r sn }
   
 \new Lyrics
   \lyricsto dv { One Two Three Four  }
   
 
 \score {
   \m
   \layout { }
 }
 
 \score {
   \m
   \midi {
 \context {
   \DrumVoice
   \alias Voice
 }
   }
 }
 
 
 Thanks David K.,
   Harm
You guys are great. Thanks so much!

Namaste,
Kevin Tough


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Annotate and Lilyglyphs

2015-02-08 Thread Urs Liska


Am 08.02.2015 um 09:33 schrieb Craig Dabelstein:

Hi Urs,

[1] I have moved to Git.


That's a good thing. You'll see in a minute.



[2] The new method of using ScholarLy is all working (when I engrave 
through Frescobaldi), but it does give me these warnings first:


openLilyLib: library infrastructure successfully loaded.


Interpreting music...[8][16][24]

warning: openLilyLib:

context property: #f

warning: openLilyLib: actual-context-id: Bassoon 2

warning: openLilyLib: context-id property: Notes

warning: openLilyLib: Resulting ctx-id: Bassoon 2


warning: openLilyLib:

context property: #f

warning: openLilyLib: actual-context-id: Baritone Saxophone

warning: openLilyLib: context-id property: Notes

warning: openLilyLib: Resulting ctx-id: Baritone Saxophone





Hihi, I should try that with our 1.000+ annotations Fried score ;-/
When fixing the previous bug I forgot to remove the debug output.

Now I've pushed the fix you can simply do git pull from inside the 
repository and have the update.




[3] However, when I try to engrave using my Makefile I get an error: 
cannot find file: `openlilylib' 




I don't know your makefile, and actually I don't have any experience 
with makefiles. But that error means that ???/openlilylib/ly is not in 
the include path passed to LilyPond.


HTH
Urs



Craig



On Sun Feb 08 2015 at 9:02:14 AM Urs Liska u...@openlilylib.org 
mailto:u...@openlilylib.org wrote:



Am 07.02.2015 um 11:37 schrieb Craig Dabelstein:

Urs,

I tried and failed to understand the ouput Here is the ouput error.

Processing

`/Users/craigdabelstein/Dropbox/Maximes_Music/French_music/Berlioz/lilypond/Score/Berlioz-01-score.ly'

Parsing...


openLilyLib: library infrastructure successfully loaded.


Interpreting music...[8][16][24]

warning: openLilyLib:

context property: #f

warning: openLilyLib: actual-context-id: Bassoon 2

warning: openLilyLib: context-id property: Notes

warning: openLilyLib: Resulting ctx-id: #t



/Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:156:34
http://0: In procedure string-symbol in expression
(string-symbol ctx-id):


/Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:156:34
http://1: Wrong type argument in position 1 (expecting string): #t

Exited with return code 1.



Thanks for testing. It turned out to be a simple error in the
conditional evaluation of the different possibilities to determine
a context name. This shows that one should actually have a
comprehensive test suite ...

I have pushed the update to Github so you can get it from there.
I see that you have stored openlilylib in a Dropbox folder. You
really should consider using Git, if only for getting stuff from
Github. It makes managing repositories like openlilylib so much
cleaner ...

Best

Urs




On Sat Feb 07 2015 at 7:19:25 PM Urs Liska u...@openlilylib.org
mailto:u...@openlilylib.org wrote:


Am 07.02.2015 um 07:54 schrieb Urs Liska:



Am 7. Februar 2015 04:47:11 MEZ, schrieb Craig Dabelstein
craig.dabelst...@gmail.com
mailto:craig.dabelst...@gmail.com:
Dear Urs,

All good.

I've followed all your instructions -- no problem.

However, perhaps I'm putting \setOption
scholarly.annotate.export-targets
#'(latex plaintext) in the wrong place. I put this in the
main-init.ily file, yes?

When I try to engrave the score I get this error:

Parsing...


openLilyLib: library infrastructure successfully loaded.


Interpreting music...[8][16][24]

/Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:150:34
0: In procedure string-symbol in expression
(string-symbol ctx-id):


/Users/craigdabelstein/Dropbox/Lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:150:34
1: Wrong type argument in position 1 (expecting string): #t

Exited with return code 1.

This looks like a bug to me. It seems you managed to use a
constellation I failed to check. This is in the code where
the name of the context is determined.

Please try with a simple example file to check whether you
can get it to compile at all.

Unfortunately I don't think I'll be able to work on this
today at all.


There's something you can do to debug:

  * Open openlilylib/ly/scholarly/annotate/__main__.ily
  * Locate the (set! annotation, should be line 145
  * Insert the following lines _before_ this line:

 (oll:warn \n\context\ property: ~a
(assoc-ref annotation context))
 (oll:warn \actual-context-id: 

Re: Annotate and Lilyglyphs

2015-02-08 Thread Urs Liska


Am 08.02.2015 um 11:08 schrieb flup2:

The few tests I made are working fine now; the only not working thing is
the example file that still uses the former loading and options syntax.


which example file?
I don't see any in my working directory.

Urs



Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Annotate-and-Lilyglyphs-tp171471p171599.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Annotate and Lilyglyphs

2015-02-08 Thread Philippe Massart
The annotate.ly file in openlilylib/ly/scholarly/annotate/examples/

Philippe


 Le 8 févr. 2015 à 11:16, Urs Liska u...@openlilylib.org a écrit :
 
 
 Am 08.02.2015 um 11:08 schrieb flup2:
 The few tests I made are working fine now; the only not working thing is
 the example file that still uses the former loading and options syntax.
 
 which example file?
 I don't see any in my working directory.
 
 Urs
 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Annotate and Lilyglyphs

2015-02-08 Thread Urs Liska


Am 08.02.2015 um 11:33 schrieb Philippe Massart:

The annotate.ly file in openlilylib/ly/scholarly/annotate/examples/


OK.
This is the old one, a new one is in 
openlilylib/ly/scholarly/usage-examples/annotate.ly


This is not really complete or well-enough tested, but I've now 
committed that and removed the other one.

So it should be fixed upstream now.

Urs



Philippe



Le 8 févr. 2015 à 11:16, Urs Liska u...@openlilylib.org a écrit :


Am 08.02.2015 um 11:08 schrieb flup2:

The few tests I made are working fine now; the only not working thing is
the example file that still uses the former loading and options syntax.

which example file?
I don't see any in my working directory.

Urs




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Problem with r2. in two voices

2015-02-08 Thread Noeck
Hi Kieren,

the output has indeed only one dot. But at least here it puts the dot in the
upper staff space (where the e'' is) and not next to the rest.

Cheers,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Gridly: simple Segmented Grid

2015-02-08 Thread Kieren MacMillan
Hi Urs,

 Can anyone tell me (or Matteo) if there have been any significant changes in 
 lyrics handling that may cause this?

For it to behave as expected, you now need \new Voice (where you didn’t before) 
— maybe that’s messing things up?

Cheers,
Kieren.

___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


new font? (was Re: Gridly: simple Segmented Grid)

2015-02-08 Thread Kieren MacMillan
Hi Urs,

 I just pushed to github Gridly, a small LIlyPond library that (partly) 
 implements the segmented grid approach described by Urs Liska in his blog 
 post (http://lilypondblog.org/2014/10/segment-grid/), including some of the 
 ideas proposed by Jan-Peter Voigt in his blog post 
 (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) . 

On a related note, I found Abraham’s next awesome Lilypond font…  ;)
http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf

Cheers,
Kieren.
___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Tablature - Hide Tied Notes

2015-02-08 Thread mike1951
I just recently upgraded to Fedora 21 which upgraded my Lilypond to 2.18.2. 
In previous versions the tied notes were hidden, but now they remain
visible.  I had been using the following snippet to hide them, but it
doesn't seem to work anymore:

#(define (tie::tab-clear-tied-fret-numbers grob)
 (let* ((tied-fret-nr (ly:spanner-bound grob RIGHT)))
 (ly:grob-set-property! tied-fret-nr 'transparent #t)))

Is there a new improved way to hide the tied notes using full-notation
tablature?

Mike




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Tablature-Hide-Tied-Notes-tp171610.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: new font? (was Re: Gridly: simple Segmented Grid)

2015-02-08 Thread Urs Liska


Am 08.02.2015 um 17:25 schrieb Kieren MacMillan:

Hi Urs,


I just pushed to github Gridly, a small LIlyPond library that (partly) 
implements the segmented grid approach described by Urs Liska in his blog post 
(http://lilypondblog.org/2014/10/segment-grid/), including some of the ideas 
proposed by Jan-Peter Voigt in his blog post 
(http://lilypondblog.org/2014/07/trees-music-and-lilypond/) .

On a related note, I found Abraham’s next awesome Lilypond font…  ;)
http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf


Hm, I don't find this so awesome, tends to be not so readable ;-)
And it seems to encourage making errors or mixing staves (e.g. writing 
articulations between staves without clear attribution ;-)


Urs



Cheers,
Kieren.
___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Hungarian Gregorian

2015-02-08 Thread Rita Composer
Dear Pierre,

Thank you for correcting something in connection with the dots,
But we have still a problem with it. The program puts one dot in a right
place and  plus one above...
I attached.

Thank you!
Sister Judit




\version 2.19.15
\include modernGregorian.ily
%\pointAndClickOff
\language deutsch
\header { 
  tagline = ##f
}

melisma = #(define-music-function (parser location mus)
 (ly:music?)
 #{
   { \neume { $mus } \omit Accidental h }
 #})



myMelodyantifónaNégy = \transpose c c' {
  \clef G
  \omit Stem
  \key d\major
 \melisma { f4 g \lst a4.}   -- double dot... how to make it simple? 
 
 
 
  \bar |.
}
myLyricsantifónaNégy = \lyricmode {
 
  
}
\score {
  
\cadenzaOn
\new Voice = MyMelodyantifónaNégy \myMelodyantifónaNégy
\new Lyrics \lyricsto MyMelodyantifónaNégy \myLyricsantifónaNégy
  
  \layout { }
  \header {
piece = \markup {  
  \fontsize #2 
  {
\bold 4.
Kórus:
  }
}
  }
}

\paper { 
  indent = 0
  top-margin = 15
  left-margin = 20
  right-margin = 20
  system-system-spacing = #'((minimum-distance . 16)) 
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Problem with r2. in two voices

2015-02-08 Thread Kieren MacMillan
Hi Cynthia,

 I guess the only way out is to rewrite the two voices so that one of them 
 issues hidden rests in the score, but the rests in the parts, via tags.

Not at all… I can think of about a half-dozen other ways to make that happen in 
Lilypond.

This would be my preference, since it would be applied globally:

\version 2.19.15

#(define (rest-score r)
  (let ((score 0)
(yoff (ly:grob-property-data r 'Y-offset))
(sp (ly:grob-property-data r 'staff-position)))
(if (number? yoff)
(set! score (+ score 2))
(if (eq? yoff 'calculation-in-progress)
(set! score (- score 3
(and (number? sp)
 (= 0 2 sp)
 (set! score (+ score 2))
 (set! score (- score (abs (- 1 sp)
score))

#(define (merge-rests-on-positioning grob)
  (let* ((can-merge #f)
 (elts (ly:grob-object grob 'elements))
 (num-elts (and (ly:grob-array? elts)
(ly:grob-array-length elts)))
 (two-voice? (= num-elts 2)))
(if two-voice?
(let* ((v1-grob (ly:grob-array-ref elts 0))
   (v2-grob (ly:grob-array-ref elts 1))
   (v1-rest (ly:grob-object v1-grob 'rest))
   (v2-rest (ly:grob-object v2-grob 'rest)))
  (and
   (ly:grob? v1-rest)
   (ly:grob? v2-rest)  
   (let* ((v1-duration-log (ly:grob-property v1-rest 'duration-log))
  (v2-duration-log (ly:grob-property v2-rest 'duration-log))
  (v1-dot (ly:grob-object v1-rest 'dot))
  (v2-dot (ly:grob-object v2-rest 'dot))
  (v1-dot-count (and (ly:grob? v1-dot)
 (ly:grob-property v1-dot 'dot-count -1)))
  (v2-dot-count (and (ly:grob? v2-dot)
 (ly:grob-property v2-dot 'dot-count -1
 (set! can-merge
   (and 
(number? v1-duration-log)
(number? v2-duration-log)
(= v1-duration-log v2-duration-log)
(eq? v1-dot-count v2-dot-count)))
 (if can-merge
 ;; keep the rest that looks best:
 (let* ((keep-v1? (= (rest-score v1-rest)
  (rest-score v2-rest)))
(rest-to-keep (if keep-v1? v1-rest v2-rest))
(dot-to-kill (if keep-v1? v2-dot v1-dot)))
   ;; uncomment if you're curious of which rest was chosen:
   ;;(ly:grob-set-property! v1-rest 'color green)
   ;;(ly:grob-set-property! v2-rest 'color blue)
   (ly:grob-suicide! (if keep-v1? v2-rest v1-rest))
   (if (ly:grob? dot-to-kill)
   (ly:grob-suicide! dot-to-kill))
   (ly:grob-set-property! rest-to-keep 'direction 0)
   (ly:rest::y-offset-callback rest-to-keep)))
(if can-merge
#t
(ly:rest-collision::calc-positioning-done grob

Aa = \relative c'' { \oneVoice r2. }
Ab = \relative c'' { \oneVoice r2. }

\score {  
  \new Staff \with { \override RestCollision.positioning-done = 
#merge-rests-on-positioning } 
\time 3/4
\new Voice \Aa  \\ 
\new Voice \Ab 
  
}

Hope this helps!
Kieren.
___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: [openLilyLib] Fundamental reorganization started

2015-02-08 Thread Urs Liska


Am 08.02.2015 um 16:16 schrieb Urs Liska:
We had already made some promising experiments, but only using the 
header-style documentation and usage examples mentioned above.


See http://openlilylib.org/oll-test/index.html to get a first idea.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Octave check for c

2015-02-08 Thread H. S. Teoh
On Sun, Feb 08, 2015 at 08:28:00AM +0100, Noeck wrote:
 Hi Teoh,
 
 I can see no problem:
 
 \version 2.18.2
 
 { g=4 }
 \relative c'' { g='4 g,=4 g=4 }
 
 Can you send a minimal example showing your problem?
[...]

Sorry for the false alarm, folks, I can't reproduce the problem now
either. The above syntax works just fine. I'm thinking I probably
mistyped the syntax before, perhaps I swapped the = with the duration,
or something like that.


T

-- 
Hi. 'Lo.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Problem with r2. in two voices

2015-02-08 Thread Cynthia Karl

 On Feb 7, 2015, at 9:07 PM, Kieren MacMillan kieren_macmil...@sympatico.ca 
 wrote:
 
 Hi Cynthia,
 
 In fact the output generated is just nonsensical.  Two stacked augmentation 
 dots?  That just doesn’t seem right.
 
 No, it’s perfectly sensible, if you want (need) to make it visually explicit 
 that there are two voices at the same time — otherwise, how would the reader 
 know?

But I don’t want to make it visually that there are two voices here, I want to 
make it visually explicit that there is a single voice.  That’s why each voice 
has issued the \oneVoice command before asserting the r2.  And why is it only 
rests and notes that have augmentation dots are affected in \oneVoice mode this 
way? There is no way other than clashing note column warnings to tell that two 
voices have each issued concurrent rests in \oneVoice mode.  It’s just kind of 
weird that augmentation dots get this special treatment.

I guess the only way out is to rewrite the two voices so that one of them 
issues hidden rests in the score, but the rests in the parts, via tags.
 
 Consider, for example, the following related snippet:
 
 \version 2.19.15
 \score {
  \new Staff 
\time 4/2
{ d''2 c''1. }  \\
\new Voice { b'2 c''1. }
 
 }
 
 The reason this output makes sense is the same reason there are two stacked 
 augmentation dots in your rest example.


On Sun, Feb 08, 2015 at 12:03AM , Paul Scott wrote:

 What kind of music are you trying to write?
 
 Paul Scott


Concerto Op3 No12 by Francesco Manfredini.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


[openLilyLib] Fundamental reorganization started

2015-02-08 Thread Urs Liska

Hello everybody,

triggered by some comments on my last post 
http://lilypondblog.org/2015/01/introducing-scholarly/ I decided to pick 
up a few loose ends that have been lying around for some time now, so I 
finally started restructuring openLilyLib, aiming at a quite fundamental 
change.


So this message is directed (in descending order of relevance) to

 * Those who have already taken part in openLilyLib reorganization
   discussions some half a year ago
 * Everybody who has contributed to openLilyLib so afr
 * All openLilyLib users
 * All other LilyPond users/developers

Some motivations to do that now:

 * (Valid) Questions were raised if it is a good idea to have many
   different libraries scattered around.
 * Every now and then the idea arose to create some sort of consistent
   interface/infrastructure/specifications to create/distribute/use
   libraries to extend LilyPond's functionality without having to stuff
   everything into Lily herself.
 * openLilyLib has become a somewhat bubbly, unconcrete collection of code.

I had ideas about the topic that were partially very clear, partially 
rather vague. But now I simply started the task with the initial goal of 
moving ScholarLY into the new structure before I had done too much that 
would have to be reverted or modified later.


I intended to finish a certain step and announce the project in a blog 
post, but I decided to start discussion somewhat earlier and here on the 
list for two reasons: I'll be away for a week (with only mobile phone 
internet access) and won't be able to reach that state before. And I 
think I'd prefer getting feedback before stepping too far. So what 
follows is partially an explanation of what I've done, of what I intend 
to do next, and it's about opening discussion what direction this should 
take. Please understand that it's not about discussing a finished and 
polished project.


### Basic structure/concept
Currently openLilyLib is a library of includable LilyPond files, 
organized in a directory structure which intends to represent its 
conceptional hierarchy. In the new structure openLilyLib will be a 
repository of libraries, each one living in a subdirectory of the 
top-level /ly directory. While these library are also simple directories 
within the repository they are conceptually different in that adding a 
library has to be a significantly more deliberate act than  just 
creating a new directory when one doesn't really know where to put a new 
function:


 * A library must have a maintainer who is responsible for the
   library's target and also for code contributions
 * A library must have a clearly visible purpose, and it must have been
   discussed that such an addition makes sense (i.e. that the intended
   code shouldn't rather be added to other, existing libraries)
 * A library must have a certain weight that might justify setting up
   a subdomain like scholarly.openlilylib.org (doesn't exist, just an
   example)

The idea is that openLilyLib becomes a one-stop-shop solution for 
LilyPond extension, so it will be easy to share functionality and have 
other users easily get hold of it. This will also make it possible for 
tools (e.g. LilyPond editors) to depend on external LilyPond code by 
simply directing their users to get hold of that one repository as a 
dependency.
The hope is that such a set-up will encourage the community to share 
code and enable people to use LilyPond without having to reinvent the 
wheel each time (just as I wouldn't want to implement regular expression 
searching in any programming language but rather use an existing library 
for that).


### Accessing openLilyLib and its libraries

Installing openLilyLib involves the following steps (also needed if 
you want to contribute to the current discussion):


 * Downloading/cloning openLilyLib from
   https://github.com/openlilylib/openlilylib
   (if you haven't done so already)
 * Adding its root path to LilyPond's include path
   (if you haven't done so already)
 * Adding its top-level /ly directory to LilyPond's include path.
   Once everything has been migrated the root path include can be
   dropped but for now this doubled include is unfortunately necessary.

Step one for using is to activate openLilyLib with
\include openlilylib

This will already load some common infrastructure and functionality, 
mostly because openLilyLib itself needs it, but it is also available for 
users' files. Examples already available are:


 * LilyPond version predicates which make it possible for libraries to
   support different LilyPond versions by conditionally executing code
   through things e.g.
   #(if (lilypond-greater-than? 2.19.4) ...
 * Logging
   Commands like oll:log, oll:warn etc. that trigger messages (and log
   them to files) when a certain log-level is set
 * alist access
   Taken from Jan-Peter's library it greatly simplifies the handling of
   (nested) association lists.
   This is an example of functionality included 

Re: Gridly: simple Segmented Grid

2015-02-08 Thread Urs Liska

Hi Matteo,

as I've already expressed privately I think this is a great project - 
thank you for following up on my ideas. If I get the README right this 
will in fact overcome several limitations of my so-far manual approach. 
I hope we'll be able to make that generally available in the most 
straight-forward manner.


However, your example files don't compile with LilyPond 2.19. (the 
oldest 2.19 I can test is 2.19.6, so I don't exactly know where it 
breaks). 2.18.2 works fine but 2.19.x results in


Parsing...

/home/uliska/git/openlilylib/gridly/example/multi-file/../../grid-templates.ily:31:44 
0: error: syntax error, unexpected MUSIC_FUNCTION, expecting 
\sequential or \simultaneous or  or '{'


\new Lyrics \lyricsto soprano

\gridGetLyrics soprano $segments


and then of course numerous follow-up errors.

Can anyone tell me (or Matteo) if there have been any significant 
changes in lyrics handling that may cause this?


Urs



Am 07.02.2015 um 16:42 schrieb Matteo Ceccarello:

Hi all!

I just pushed to github Gridly, a small LIlyPond library that (partly) 
implements the segmented grid approach described by Urs Liska in his 
blog post (http://lilypondblog.org/2014/10/segment-grid/), including 
some of the ideas proposed by Jan-Peter Voigt in his blog post 
(http://lilypondblog.org/2014/07/trees-music-and-lilypond/) .


Basically this library allows to define and populate a grid with music 
without resorting to a preprocessing of the input files with external 
scripts. It still is in early development, however I find it already 
pretty usable. If you are interested, take a look at the code on 
https://github.com/Cecca/gridly :-)


Cheers,

Matteo



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: new font? (was Re: Gridly: simple Segmented Grid)

2015-02-08 Thread Urs Liska


Am 8. Februar 2015 21:56:28 MEZ, schrieb tisimst tisimst.lilyp...@gmail.com:
Conor, et. al.,

Looking closely at the score, I don't believe the staff lines are
pre-fixed at all, since I can see variable spacing. I can't say for
anything beyond the one page in the pdf, of course. My experience tells
me that LilyPond can manage just about anything I throw at it :)

As for making the font, it wouldn't be that difficult. Create missing
glyphs will be relatively easy since it's a hand-writing style, so I
wouldn't need a lot of reference material. It would take some time and
work, however, so if there's enough interest in it, some financial
sponsoring would be very helpful, though not required.

Cool idea, Kieren! Where is this sample from?


Here's the whole thing:
Http://beautifulscores.net/fried/fullscore.pdf 

-Abraham

Sent from my iPhone

 On Feb 8, 2015, at 1:32 PM, Conor Cook [via Lilypond]
ml-node+s1069038n171621...@n5.nabble.com wrote:
 
 It looks like an extremely neat handwritten score, but probably 
 written on staves that were already set, space-wise.  I wonder if it 
 could be modified for the purposes of Lilypond, while retaining its 
 distinct features. 
 
 ~Conor 
 
  -- Forwarded message -- 
  From: Kieren MacMillan [hidden email] 
  To: Urs Liska [hidden email], Abraham Lee [hidden email] 
  Cc: Lilypond-User Mailing List [hidden email] 
  Date: Sun, 8 Feb 2015 11:25:13 -0500 
  Subject: new font? (was Re: Gridly: simple Segmented Grid) 
  Hi Urs, 
  
  I just pushed to github Gridly, a small LIlyPond library that
(partly) implements the segmented grid approach described by Urs Liska
in his blog post (http://lilypondblog.org/2014/10/segment-grid/),
including some of the ideas proposed by Jan-Peter Voigt in his blog
post (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) . 
  
  On a related note, I found Abraham’s next awesome Lilypond font… 
;) 
 
http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf 
  
  Cheers, 
  Kieren. 
  ___ 
  
  Kieren MacMillan, composer 
  www:  http://www.kierenmacmillan.info 
  email:  [hidden email] 
  
  
  
  -- Forwarded message -- 
  From: Urs Liska [hidden email] 
  To: Kieren MacMillan [hidden email], Abraham Lee [hidden email]

  Cc: Lilypond-User Mailing List [hidden email] 
  Date: Sun, 08 Feb 2015 17:43:37 +0100 
  Subject: Re: new font? (was Re: Gridly: simple Segmented Grid) 
  
  Am 08.02.2015 um 17:25 schrieb Kieren MacMillan: 
  
  Hi Urs, 
  
  I just pushed to github Gridly, a small LIlyPond library that
(partly) implements the segmented grid approach described by Urs Liska
in his blog post (http://lilypondblog.org/2014/10/segment-grid/),
including some of the ideas proposed by Jan-Peter Voigt in his blog
post (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) . 
  
  On a related note, I found Abraham’s next awesome Lilypond font… 
;) 
 
http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf 
  
  
  Hm, I don't find this so awesome, tends to be not so readable ;-) 
  And it seems to encourage making errors or mixing staves (e.g.
writing articulations between staves without clear attribution ;-) 
  
  Urs 
  
  
  Cheers, 
  Kieren. 
  ___ 
  
  Kieren MacMillan, composer 
  www:  http://www.kierenmacmillan.info 
  email:  [hidden email]
 
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 If you reply to this email, your message will be added to the
discussion below:

http://lilypond.1069038.n5.nabble.com/new-font-was-Re-Gridly-simple-Segmented-Grid-tp171621.html
 To start a new topic under User, email
ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML




--
View this message in context:
http://lilypond.1069038.n5.nabble.com/new-font-was-Re-Gridly-simple-Segmented-Grid-tp171621p171623.html
Sent from the User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Fwd: RE: How to remove gap in UpPrall spanner?

2015-02-08 Thread Noeck
Am 08.02.2015 um 22:05 schrieb Ed Gordijn:
 This is even better then perfection.

Hi,

I tried almost the same:

\version 2.18.2

\relative c'' {
  \override TrillSpanner.bound-details.left.text =
  \markup\concat{
\raise #1.0
\smaller
\musicglyph #scripts.upprall
\hspace #-0.5
  }
  \override TrillSpanner.bound-details.left.padding = #'0
  \override TrillSpanner.to-barline = ##t
  a4\startTrillSpan a a a
  a\stopTrillSpan
  \override TrillSpanner.bound-details.left.text =
  \markup\concat{
\raise #.15
\fontsize #-5
\bold (
\hspace #-0.58
  }
  a4\startTrillSpan a a
  a\stopTrillSpan
  \override TrillSpanner.bound-details.left.text =
  \markup\concat{
\raise #.1
\fontsize #-5
\rotate #-7 \sans (
\hspace #-0.61
  }
  a4\startTrillSpan a a
  a\stopTrillSpan
}

But I didn’t post it here, because I was not satisfied with it for these 
reasons:
- the the lower edge of the roman paranthesis is too sharp
- the sans version is a bit too light (bold would be too much)
- the whole trill span is shifted upwards, even thought the parenthesis does
  not collide with the stems below.

Perhaps you like them anyway.

Cheers,
Joram


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Problem with r2. in two voices

2015-02-08 Thread Kevin Barry
On Sun, Feb 8, 2015 at 2:03 PM, Cynthia Karl pck...@mac.com wrote:

 But I don’t want to make it visually that there are two voices here, I
 want to make it visually explicit that there is a single voice.  That’s why
 each voice has issued the \oneVoice command before asserting the r2.  And
 why is it only rests and notes that have augmentation dots are affected in
 \oneVoice mode this way? There is no way other than clashing note column
 warnings to tell that two voices have each issued concurrent rests in
 \oneVoice mode.  It’s just kind of weird that augmentation dots get this
 special treatment.


I think you are misusing \oneVoice here; it isn't for merging things into a
single voice, but rather for telling LilyPond that there is only one voice
that it needs to position on the staff. If you are still `feeding' it two
(or more) voices you will have to do some extra work to tell LilyPond what
to do or you will get errors and/or unintended output.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: new font? (was Re: Gridly: simple Segmented Grid)

2015-02-08 Thread tisimst
Conor, et. al.,

Looking closely at the score, I don't believe the staff lines are pre-fixed at 
all, since I can see variable spacing. I can't say for anything beyond the one 
page in the pdf, of course. My experience tells me that LilyPond can manage 
just about anything I throw at it :)

As for making the font, it wouldn't be that difficult. Create missing glyphs 
will be relatively easy since it's a hand-writing style, so I wouldn't need a 
lot of reference material. It would take some time and work, however, so if 
there's enough interest in it, some financial sponsoring would be very helpful, 
though not required.

Cool idea, Kieren! Where is this sample from?

-Abraham

Sent from my iPhone

 On Feb 8, 2015, at 1:32 PM, Conor Cook [via Lilypond] 
 ml-node+s1069038n171621...@n5.nabble.com wrote:
 
 It looks like an extremely neat handwritten score, but probably 
 written on staves that were already set, space-wise.  I wonder if it 
 could be modified for the purposes of Lilypond, while retaining its 
 distinct features. 
 
 ~Conor 
 
  -- Forwarded message -- 
  From: Kieren MacMillan [hidden email] 
  To: Urs Liska [hidden email], Abraham Lee [hidden email] 
  Cc: Lilypond-User Mailing List [hidden email] 
  Date: Sun, 8 Feb 2015 11:25:13 -0500 
  Subject: new font? (was Re: Gridly: simple Segmented Grid) 
  Hi Urs, 
  
  I just pushed to github Gridly, a small LIlyPond library that (partly) 
  implements the segmented grid approach described by Urs Liska in his blog 
  post (http://lilypondblog.org/2014/10/segment-grid/), including some of 
  the ideas proposed by Jan-Peter Voigt in his blog post 
  (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) . 
  
  On a related note, I found Abraham’s next awesome Lilypond font…  ;) 
  http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf 
  
  Cheers, 
  Kieren. 
  ___ 
  
  Kieren MacMillan, composer 
  www:  http://www.kierenmacmillan.info 
  email:  [hidden email] 
  
  
  
  -- Forwarded message -- 
  From: Urs Liska [hidden email] 
  To: Kieren MacMillan [hidden email], Abraham Lee [hidden email] 
  Cc: Lilypond-User Mailing List [hidden email] 
  Date: Sun, 08 Feb 2015 17:43:37 +0100 
  Subject: Re: new font? (was Re: Gridly: simple Segmented Grid) 
  
  Am 08.02.2015 um 17:25 schrieb Kieren MacMillan: 
  
  Hi Urs, 
  
  I just pushed to github Gridly, a small LIlyPond library that (partly) 
  implements the segmented grid approach described by Urs Liska in his 
  blog post (http://lilypondblog.org/2014/10/segment-grid/), including 
  some of the ideas proposed by Jan-Peter Voigt in his blog post 
  (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) . 
  
  On a related note, I found Abraham’s next awesome Lilypond font…  ;) 
  http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf 
  
  
  Hm, I don't find this so awesome, tends to be not so readable ;-) 
  And it seems to encourage making errors or mixing staves (e.g. writing 
  articulations between staves without clear attribution ;-) 
  
  Urs 
  
  
  Cheers, 
  Kieren. 
  ___ 
  
  Kieren MacMillan, composer 
  www:  http://www.kierenmacmillan.info 
  email:  [hidden email]
 
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 If you reply to this email, your message will be added to the discussion 
 below:
 http://lilypond.1069038.n5.nabble.com/new-font-was-Re-Gridly-simple-Segmented-Grid-tp171621.html
 To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/new-font-was-Re-Gridly-simple-Segmented-Grid-tp171621p171623.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


new font? (was Re: Gridly: simple Segmented Grid)

2015-02-08 Thread Conor Cook
It looks like an extremely neat handwritten score, but probably
written on staves that were already set, space-wise.  I wonder if it
could be modified for the purposes of Lilypond, while retaining its
distinct features.

~Conor

 -- Forwarded message --
 From: Kieren MacMillan kieren_macmil...@sympatico.ca
 To: Urs Liska u...@openlilylib.org, Abraham Lee tisimst.lilyp...@gmail.com
 Cc: Lilypond-User Mailing List lilypond-user@gnu.org
 Date: Sun, 8 Feb 2015 11:25:13 -0500
 Subject: new font? (was Re: Gridly: simple Segmented Grid)
 Hi Urs,

 I just pushed to github Gridly, a small LIlyPond library that (partly) 
 implements the segmented grid approach described by Urs Liska in his blog 
 post (http://lilypondblog.org/2014/10/segment-grid/), including some of the 
 ideas proposed by Jan-Peter Voigt in his blog post 
 (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) .

 On a related note, I found Abraham’s next awesome Lilypond font…  ;)
 http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf

 Cheers,
 Kieren.
 ___

 Kieren MacMillan, composer
 www:  http://www.kierenmacmillan.info
 email:  i...@kierenmacmillan.info



 -- Forwarded message --
 From: Urs Liska u...@openlilylib.org
 To: Kieren MacMillan kieren_macmil...@sympatico.ca, Abraham Lee 
 tisimst.lilyp...@gmail.com
 Cc: Lilypond-User Mailing List lilypond-user@gnu.org
 Date: Sun, 08 Feb 2015 17:43:37 +0100
 Subject: Re: new font? (was Re: Gridly: simple Segmented Grid)

 Am 08.02.2015 um 17:25 schrieb Kieren MacMillan:

 Hi Urs,

 I just pushed to github Gridly, a small LIlyPond library that (partly) 
 implements the segmented grid approach described by Urs Liska in his blog 
 post (http://lilypondblog.org/2014/10/segment-grid/), including some of 
 the ideas proposed by Jan-Peter Voigt in his blog post 
 (http://lilypondblog.org/2014/07/trees-music-and-lilypond/) .

 On a related note, I found Abraham’s next awesome Lilypond font…  ;)
 http://lilypondblog.org/wp-content/uploads/2014/10/sample-page.pdf


 Hm, I don't find this so awesome, tends to be not so readable ;-)
 And it seems to encourage making errors or mixing staves (e.g. writing 
 articulations between staves without clear attribution ;-)

 Urs


 Cheers,
 Kieren.
 ___

 Kieren MacMillan, composer
 www:  http://www.kierenmacmillan.info
 email:  i...@kierenmacmillan.info

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Fwd: RE: How to remove gap in UpPrall spanner?

2015-02-08 Thread Ed Gordijn
Sorry,

Didn't reply to the list.

This is even better then perfection.

\version 2.17.9

beginPrallSpan =
 \tweak bound-details.left.text
   \markup { \fontsize #-5 { \musicglyph #accidentals.leftparen } }
 \tweak bound-details.left.stencil-offset #'(0.02 . -0.65)
 \tweak bound-details.left.padding #-0.25
 \tweak bound-details.right.padding #-1
 \startTrillSpan

endPrallSpan = \stopTrillSpan

{
  c'\beginPrallSpan d' c'2\endPrallSpan
}

See the old thread.

Greetings, Ed
-- Doorgestuurd bericht --
Van: Ed Gordijn ed.klari...@gmail.com
Datum: 8 feb. 2015 09:42
Onderwerp: RE: How to remove gap in UpPrall spanner?
Aan: Javier Ruiz-Alma jav...@ruiz-alma.com
Cc:

If you like this,

 PERFECTION

Take a look at this old thread.
http://lists.gnu.org/archive/html/lilypond-user/2013-01/msg00167.html

Greetings, Ed
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Problem with r2. in two voices

2015-02-08 Thread Simon Albrecht

Am 08.02.2015 21:32, schrieb Kevin Barry:


On Sun, Feb 8, 2015 at 2:03 PM, Cynthia Karl pck...@mac.com 
mailto:pck...@mac.com wrote:


But I don't want to make it visually that there are two voices
here, I want to make it visually explicit that there is a single
voice.  That's why each voice has issued the \oneVoice command
before asserting the r2.  And why is it only rests and notes that
have augmentation dots are affected in \oneVoice mode this way?
There is no way other than clashing note column warnings to tell
that two voices have each issued concurrent rests in \oneVoice
mode.  It's just kind of weird that augmentation dots get this
special treatment.


I think you are misusing \oneVoice here;
Indeed the name of the command makes perfectly clear that it's 
contradictory and nonsensical (and lily basically requires to be given 
sensible input) to write \oneVoice and have two voices all the same. Too 
much noise for such a basic misconception!


Yours, Simon

it isn't for merging things into a single voice, but rather for 
telling LilyPond that there is only one voice that it needs to 
position on the staff. If you are still `feeding' it two (or more) 
voices you will have to do some extra work to tell LilyPond what to do 
or you will get errors and/or unintended output.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


EB Garamond font-series

2015-02-08 Thread Simon Albrecht

Hello list,

I just re-installed the incredibly beautiful EB Garamond font from 
http://www.georgduffner.at/ebgaramond/ 
https://bitbucket.org/georgd/eb-garamond/downloads/EBGaramond-0.016.zip, 
but apparently Lily can’t find the bold font series. Can anyone tell me 
where to search for a solution?


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


openlilylib and Makefiles

2015-02-08 Thread Craig Dabelstein
Hi List,

Does anyone have experience with using both openlilylib and Makefiles? I'm
using Urs' scholarLy, and have updated to the latest code as of yesterday,
and through Frescobaldi it all engraves fine. However, when I try to run my
Makefile on the same piece it gives me cannot find file: `openlilylib' 

Any ideas?

Craig
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: EB Garamond font-series

2015-02-08 Thread tisimst
No need to test that. There isn't a bold variant (yet), though it seems 
like the author hopes to get that far. Hope that doesn't make you too 
sad :)

-Abraham

On Sun, Feb 8, 2015 at 9:06 PM, Thomas Spuhler [via Lilypond] 
ml-node+s1069038n171634...@n5.nabble.com wrote:
 On Monday, February 09, 2015 02:13:53 AM Simon Albrecht wrote:
 
  Hello list, 
  
  I just re-installed the incredibly beautiful EB Garamond font from 
  http://www.georgduffner.at/ebgaramond/ 
  
 https://bitbucket.org/georgd/eb-garamond/downloads/EBGaramond-0.016.zip, 
  but apparently Lily can’t find the bold font series. Can anyone 
 tell me 
  where to search for a solution? 
  
  Best, Simon 
  
  ___ 
  lilypond-user mailing list 
  [hidden email] 
  https://lists.gnu.org/mailman/listinfo/lilypond-user
 Can you provide more details on how to test it? 
 Can you see them using another program such as libereoffice writer. 
 
 Does your system show them as imported? 
 
 Last but not least which fonts did you install, the otf? 
 
 
 -- 
 Best regards 
 Thomas Spuhler 
 
 All of my e-mails have a valid digital signature 
 ID 60114E63
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
  signature.asc (205 bytes) Download Attachment
 
 
 If you reply to this email, your message will be added to the 
 discussion below:
 http://lilypond.1069038.n5.nabble.com/EB-Garamond-font-series-tp171632p171634.html
 To start a new topic under User, email 
 ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/EB-Garamond-font-series-tp171632p171635.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


[OT] Vaughan is now composing…

2015-02-08 Thread Vaughan McAlley
http://xkcd.com/1482/

…it would be quite easy to implement in Frescobaldi or Lilypond!

Vaughan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: EB Garamond font-series

2015-02-08 Thread Thomas Spuhler
On Monday, February 09, 2015 02:13:53 AM Simon Albrecht wrote:
 Hello list,
 
 I just re-installed the incredibly beautiful EB Garamond font from
 http://www.georgduffner.at/ebgaramond/
 https://bitbucket.org/georgd/eb-garamond/downloads/EBGaramond-0.016.zip,
 but apparently Lily can’t find the bold font series. Can anyone tell me
 where to search for a solution?
 
 Best, Simon
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

Can you provide more details on how to test it?
Can you see them using another program such as libereoffice writer.

Does your system show them as imported?

Last but not least which fonts did you install, the otf?


-- 
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: openlilylib and Makefiles

2015-02-08 Thread Kevin Barry
On Mon, Feb 9, 2015 at 2:01 AM, Craig Dabelstein craig.dabelst...@gmail.com
 wrote:

 Does anyone have experience with using both openlilylib and Makefiles? I'm
 using Urs' scholarLy, and have updated to the latest code as of yesterday,
 and through Frescobaldi it all engraves fine. However, when I try to run my
 Makefile on the same piece it gives me cannot find file: `openlilylib' 


Do you have the necessary folders in your include path in the makefile?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: EB Garamond font-series

2015-02-08 Thread Thomas Spuhler
On Sunday, February 08, 2015 09:16:40 PM tisimst wrote:
 No need to test that. There isn't a bold variant (yet), though it seems
 like the author hopes to get that far. Hope that doesn't make you too
 sad :)

 -Abraham

 On Sun, Feb 8, 2015 at 9:06 PM, Thomas Spuhler [via Lilypond]

 ml-node+s1069038n171634...@n5.nabble.com wrote:
  On Monday, February 09, 2015 02:13:53 AM Simon Albrecht wrote:
   Hello list,
  
   I just re-installed the incredibly beautiful EB Garamond font from
   http://www.georgduffner.at/ebgaramond/
 
  https://bitbucket.org/georgd/eb-garamond/downloads/EBGaramond-0.016.zip,
 
   but apparently Lily can’t find the bold font series. Can anyone
 
  tell me
 
   where to search for a solution?
  
   Best, Simon
  
   ___
   lilypond-user mailing list
   [hidden email]
   https://lists.gnu.org/mailman/listinfo/lilypond-user
 
  Can you provide more details on how to test it?
  Can you see them using another program such as libereoffice writer.
 
  Does your system show them as imported?
 
  Last but not least which fonts did you install, the otf?

 --
 View this message in context:
 http://lilypond.1069038.n5.nabble.com/EB-Garamond-font-series-tp171632p171635.html
  Sent from the
 User mailing list archive at Nabble.com.

Are you sure:
see attachment from libreoffice writer, normal and bold

--
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63

EBGaramond_08_20points_normal_bold.pdf
Description: Adobe PDF document


signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: EB Garamond font-series

2015-02-08 Thread Kevin Barry
On Mon, Feb 9, 2015 at 4:27 AM, Thomas Spuhler thomas.spuh...@btspuhler.com
 wrote:

 Are you sure:
 see attachment from libreoffice writer, normal and bold


When there is no bold face present, a word processor might `fake' one by
modifying the regular (roman) face. I don't know if that is what happened
in your attachment, but the zip archive for the EB Garamond font linked to
in your first message does not contain any files for a bold face. Normally
a typeface has separate files for regular, bold, italic, bold-italic and so
on, which LilyPond will attempt to use, but in this case it can't because
that file presumably doesn't exist on your system.

Elsewhere on the website the author does mention bold in the list of goals,
but it does not appear in the specimen pdf which suggests it is not
implemented yet.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: EB Garamond font-series

2015-02-08 Thread tisimst
This is correct. LibreOffice does fake italic, bold, and bold-italic if that 
variant doesn't exist. LilyPond, however, makes no attempt at this and just 
reverts to the closest one that is installed, which is usually the regular 
variant. 

- Abraham

Sent from my iPhone

 On Feb 8, 2015, at 9:41 PM, Kevin Barry [via Lilypond] 
 ml-node+s1069038n171638...@n5.nabble.com wrote:
 
 
 On Mon, Feb 9, 2015 at 4:27 AM, Thomas Spuhler [hidden email] wrote:
 Are you sure:
 see attachment from libreoffice writer, normal and bold
 
 When there is no bold face present, a word processor might `fake' one by 
 modifying the regular (roman) face. I don't know if that is what happened in 
 your attachment, but the zip archive for the EB Garamond font linked to in 
 your first message does not contain any files for a bold face. Normally a 
 typeface has separate files for regular, bold, italic, bold-italic and so on, 
 which LilyPond will attempt to use, but in this case it can't because that 
 file presumably doesn't exist on your system.
 
 Elsewhere on the website the author does mention bold in the list of goals, 
 but it does not appear in the specimen pdf which suggests it is not 
 implemented yet.
 
 ___ 
 lilypond-user mailing list 
 [hidden email] 
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 If you reply to this email, your message will be added to the discussion 
 below:
 http://lilypond.1069038.n5.nabble.com/EB-Garamond-font-series-tp171632p171638.html
 To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com 
 To unsubscribe from Lilypond, click here.
 NAML




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/EB-Garamond-font-series-tp171632p171639.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: [OT] Vaughan is now composing…

2015-02-08 Thread brentboylan
Love this! Attach it to Frescobaldi's auto-compile so that it tweets and/or
posts to my facebook wall every time.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/OT-Vaughan-is-now-composing-tp171629p171630.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user