Re: Fedora 22

[Martin Tarenskeen]

On Thu, 30 Apr 2015, Martin Tarenskeen wrote:


Hi,

Can anyone confirm that lilypond (2.19.18) in Fedora 22 Beta currently is 
unusable, probably due to problems with Ghostscript? (9.16)


It's not working for me. (compilation of *.ly files fails)


I am talking about the lilypond package that I installed from the Fedora 
22 repository using dnf (which has replaced yum in F22)


--

MT

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

Fedora 22

[Martin Tarenskeen]

Hi,

Can anyone confirm that lilypond (2.19.18) in Fedora 22 Beta currently is 
unusable, probably due to problems with Ghostscript? (9.16)


It's not working for me. (compilation of *.ly files fails)

--

MT



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

Re: Jianpu Notation

[Super-User]

Hi Ming!


I've moved to new apartment in Beijing last week, and gonna to join events in 
Hangzhou these days. I will checkout the new code when I am available.


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

Re: Jianpu Notation

[MING TSANG]

Paul,I do further run of jianpu9.ly. Please refer to .png
I added :     this verse is just for JianpuStaff   --- Staff has the regular 
lyric (without the \skip1)1.  \skip1 \skip1 for lyric for n - - &   n - 0   
...ref bar 24, 27      2.  \skip1 for n -  ...ref bar 25 
I coded \tuplet  ...the lyric display correctly
I also notice 8th-note underline in bar 25 is lower than that of bar 26, 28, 29 
 and 30
Immanuel,Ming. 


 On Wednesday, April 29, 2015 4:03 PM, MING TSANG  
wrote:
   

 Paul,
Thank you very much. This look great.
As I mention few days ago, David put the following options in jianpu6.ly.  Is 
jianpu9.ly stable enough to merge with jianpu6.ly?If yes, David, can you do the 
honer?  OR Paul, do you want to take the challenge.  I let you all decide.  I 
appreciated for both of you taking time out of your busy schedule to make this 
jianpu notation possible.  My wish came true since lilypond v.2.12. 
<>

Immanuel,Ming.  


 On Wednesday, April 29, 2015 3:14 PM, Paul Morris  
wrote:
   

 
On Apr 29, 2015, at 7:18 AM, MING TSANG  wrote:
Paul,
Thank you very much for the update.
One minor glitch, bar 27 & 28 the rest does not show on jianpu-score. It show 
the same as previous note. 

Thanks Ming for catching that glitch.  Everything worked fine for simple test 
cases with rests, but somehow for those rests in your score the code was 
somehow registering a pitch for those rest events (I don’t know why…) so they 
were being treated as notes.  
The new version 9 that's attached solves this problem.  Not hard to fix once I 
figured out the cause (just check to see if should be a rest first, rather than 
first checking for a pitch as an indication that it should be a note).  Let me 
know if you find any other odd glitches like this.
Oh, and thanks Werner, I agree that it has gotten a lot better!
-Paul



   

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

Re: variable in scheme

[Stephen MacNeil]

Hey thanks I didn't need it after all.

>>What's the intent?

I never use tab so my bend file ""definitions.ily" has all the tab sections
removed so it doesn't print tab- did that a long time ago. All works fine
however a friend wanted to use the tab and couldn't do quarter tones. So I
was going to hack the scheme but well .. i don't no scheme :) However i
figured the midi doesn't play anyway so why not just use the interface and
change it ?

Anyway long story short he can now use it with quarter tones to print his
music.

Thanks
Stephen


On Wed, Apr 29, 2015 at 3:46 AM, Mattes  wrote:

>
> Am Mittwoch, 29. April 2015 07:21 CEST, Stephen MacNeil <
> classicalja...@gmail.com> schrieb:
>
> > is this correct?
>
> What's the intent?
>
> >
> > (#'(,num))
> >
> > (#'(,str))
>
> No, commas (',') are only allowed within a backquoted form.
>
> Cheers, RalfD
>
>
> >
> >
> > thanks
> >
> > Stephen
>
>
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: svg font issue(bug?): can't change TimeSignature font (but markup fonts can be changed)

[padovani]

Nice! Thank you!!

2015-04-29 20:02 GMT-03:00 Dan Eble :

> On Apr 29, 2015, at 16:48 , padovani  wrote:
> >
> > So... I discovered that the TimeSignature issue is related to the fact
> that
> > it is not being written as text to the svg file, but as a path.
> >
> > If I use this code I can create a svg file with different fonts for the
> > time signature, overriding the stencil with a text:
> ...
> > It works, but I'm struggling here to change the text of the time
> signature
> > automatically with a scheme function.
>
> \version "2.19.16"
>
> #(add-simple-time-signature-style 'swiss
>   (lambda (fraction)
>(let ((n (car fraction))
>  (d (cdr fraction)))
> #{
>   \markup {
> \override #'(font-name . "Helvetica")
> \override #'(baseline-skip . 0.2)
> \fontsize #4
> \column { #(number->string n) #(number->string d) }
>   }
> #} )))
>
> \score {
>   \new Staff \with {
> \override TimeSignature.style = #'swiss
>   } {
> \time 2/4
> c2
>   }
> }
>
> —
> Dan
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: svg font issue(bug?): can't change TimeSignature font (but markup fonts can be changed)

[Dan Eble]

On Apr 29, 2015, at 16:48 , padovani  wrote:
> 
> So... I discovered that the TimeSignature issue is related to the fact that
> it is not being written as text to the svg file, but as a path.
> 
> If I use this code I can create a svg file with different fonts for the
> time signature, overriding the stencil with a text:
...
> It works, but I'm struggling here to change the text of the time signature
> automatically with a scheme function.

\version "2.19.16"

#(add-simple-time-signature-style 'swiss
  (lambda (fraction)
   (let ((n (car fraction))
 (d (cdr fraction)))
#{
  \markup {
\override #'(font-name . "Helvetica")
\override #'(baseline-skip . 0.2)
\fontsize #4
\column { #(number->string n) #(number->string d) }
  }
#} )))

\score {
  \new Staff \with {
\override TimeSignature.style = #'swiss
  } {
\time 2/4
c2
  }
}

— 
Dan


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

Re: Questions about the edition engraver

[Noeck]

Hi Simon, Kieren, Urs and Jan-Peter,

thanks for all your replies!

>> 1. Can I use the same tweak at several points in time?

\editionModList is what I was looking for, thanks

>> 2. What do the letters mean in edition.Staff.A?
> 
> The [alphabetical] order of such contexts, from the top. So in your example, 
> Staff.B would correspond to your “mg”.
> 
> n.b. I have requested of Jan-Peter that the edition-engraver allow id- or 
> name-based addressing, so you could use "full-score.Staff.mg" or even just 
> “full-score.mg”; I don’t know the current status of that request.

That would be nice.

>> 2. What do the letters mean in edition.Staff.A?
>> A numbering? How can I know which voice is which?
>> Can I test that (like \displayEngraverNameHere)?
> When I started to implement it, I realized, that one has to identify 
> contexts, that share the same edition-engraver-id. So I added a counter. But 
> if I want to enter the ID with dot-notation, I may not use digits, but only 
> characters. So I count from A to Z, using capital letters to prevent taking 
> it as a pitch.
> I know that it is difficult to address Voices, when they are tagged from A to 
> Z ... but more on that later!

Thanks, that makes things clear.

>> 3. How can I address a temporary voice in some measure?
>> a) One with << · \\ · >>?
>> b) One with << · \new Voice { · } >>?
>> (So far I
> There is an instantiation for an edition-engraver in every voice via a layout 
> declaration. If an edition-engraver is instantiated with #f for the id, it 
> looks into the parent context for an id. So if there is a Staff with an 
> \editionEngraver my.special.id , any voice created in this context will 
> consist an edition-engraver and can be addressed with 
> 'my.special.id.Voice.[A-Z]'. As mentioned above, it can be tedious to 
> identify the right voice. And OTOH it is not ideal, if you have to type 
> Score.A anytime, as there is only one Score for each score.
> Urs mentioned the pending pull-request, where I developed a change. I am 
> working in another project right now ... that is the reason I didn't have a 
> deeper look into the problem Urs mentioned ... time will come

In the log there are Voices up to P so I probably have much more voices
than I thought (I know of 4 or 6).
I suppose this means I should use a dedicated edition engraver for this
Voice to make it more robust even if I find the number of the Voice.

>> 4. What does the word 'edition' after the \editionEngraver mean?
>> Can I choose this name? Why would I need more than one?
> As mentioned above, every instance of an edition-engraver has an id, so you 
> can address it. In the pull-request around the corner, the edition-engraver 
> takes
> 1. the id given as an argument
> or, if it is not a list,
> 2. the context-property 'edition-id
> or, if that is not a non-empty list,
> 3. the id of the parent contexts edition-engraver

To be a list, must there be always a dot in this name? Like 'mytest.id'?
Or is 'edition' equally fine?

>> 4. What does the word 'edition' after the \editionEngraver mean?
>>   Can I choose this name?
>
> Yes. And you should, as in my example above.
>
>> Why would I need more than one?
>
> Well, for example, ...
That makes sense. That way I might even be able to address a temporary
voice by adding a different engraver here in the \with block (I’ll have
to check).

>> 5. Can I put tweaks with the edition engraver?
>> Like coloring the second of three note heads in a chord?
>> {  }
> Kieren said yes, but I think, I still have to implement it that way. I have 
> the idea to act on music found by a listener to add tweaks or to change 
> properties like the pitch. (the auto-transposer does it on that level)

I think Kieren meant \tweaks in general (not inside a chord). With the
listeners etc. you lost me, but that’s ok. I don’t need it right now.

>> 6. Would you consider \voiceOne etc. content or layout? \noBeam?
> I’d phrase it this way: everything that is decided by the
> composer/arranger is content, everything that is decided by the \
> typesetter/editor is presentation. Where exactly the border is to be >
drawn, depends.
I agree. (\noBeam already depends on the editions I know in some
cases, though.)

>> 7. Would you write a Dynamics context using spacer rests ...
answered.


> In the mentioned pull-request the addressing of contexts is streamlined.
> And I take the questions to continue development:
> 
> * create dynamics
Ok, but I agree with Kieren that this is more content than edition-layout.
> * add tweaks to single notes in an event chord
That would be nice. I don’t need it right now, though.

Thanks for all your answers! I think I can handle it now.

Cheers,
Joram

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

Re: svg font issue(bug?): can't change TimeSignature font (but markup fonts can be changed)

[padovani]

So... I discovered that the TimeSignature issue is related to the fact that
it is not being written as text to the svg file, but as a path.

If I use this code I can create a svg file with different fonts for the
time signature, overriding the stencil with a text:

%% BEGIN CODE 1
\score {
\new Staff {

\once \override Staff.TimeSignature.stencil = #ly:text-interface::print
  \once \override Staff.TimeSignature.text = \markup {
  \override #'(font-name . "Helvetica")
  \override #'(baseline-skip . 0.2)
  \fontsize #4
 \column { "3"
   "4"
  }}
\time 2/4
c2
}
}
%% END CODE 1

It works, but I'm struggling here to change the text of the time signature
automatically with a scheme function. Tried the code below, but it does not
work (giving me exactly the same error dump of my previous message). Any
suggestions?

%% BEGIN CODE 2
#(define-public (tsigastext grob)
   (let* ((frac (ly:grob-property grob 'fraction))
  (num (if (pair? frac) (car frac) 4))
  (den (if (pair? frac) (cdr frac) 4))
  (m (markup
  #:override '(font-name . "Helvetica")
  #:override '(baseline-skip . 0.5)
  #:fontsize 4
  #:center-column (#:number (number->string num)
   #:override '(style . default)
   #:number (number->string den)
 
(ly:grob-set-property! grob 'stencil ly:text-interface::print)
(grob-interpret-markup grob m)))


\score {
\new Staff {

  \override Staff.TimeSignature.stencil = #tsigastext
\time 2/4
c2


%%% \override Staff.TimeSignature.stencil = #(lambda (grob)
%%%(parenthesize-stencil (ly:time-signature::print grob) 0.1 0.4 0.4
0.1 ))

\time 3/4
c2
}
}
%% END CODE 2

thanks!

2015-04-28 14:37 GMT-03:00 padovani :

> Hi,
>
> This code compiles on .ps /.svg backends without problems:
>
> %code 1
> \score {
> \new Staff {
> \time 2/4
> c2_\markup {
>   \override #'(font-name . "Helvetica")
> "here it works"
> }
> }
> }
> %end code 1
>
> But the code below one gives me an error if I compile with -dbackend=svg
>
> %code2
> \score {
> \new Staff {
> \override Staff.TimeSignature.font-name = #'"Helvetica"
> \time 2/4
> c2_\markup {
>   \override #'(font-name . "Helvetica")
> "here it works"
> }
> }
> }
> % end code 2
>
> here is the error:
> %%error begin
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `teste.svg'...
> warning: cannot find SVG font #f
> /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/output-svg.scm:558:7:
> In procedure string-null? in expression (string-null? expr):
> /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/output-svg.scm:558:7:
> Wrong type argument in position 1 (expecting string): #
> %%error end
>
> (I'm using 2.19.19 on OSX 10.9.5.)
>
> Is this a bug? It seems that something need to be changes in
> output-svg.scm... any idea?
>
> Thank you!
>
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Jianpu Notation

[MING TSANG]

Paul,
Thank you very much. This look great.
As I mention few days ago, David put the following options in jianpu6.ly.  Is 
jianpu9.ly stable enough to merge with jianpu6.ly?If yes, David, can you do the 
honer?  OR Paul, do you want to take the challenge.  I let you all decide.  I 
appreciated for both of you taking time out of your busy schedule to make this 
jianpu notation possible.  My wish came true since lilypond v.2.12. 
<>

Immanuel,Ming.  


 On Wednesday, April 29, 2015 3:14 PM, Paul Morris  
wrote:
   

 
On Apr 29, 2015, at 7:18 AM, MING TSANG  wrote:
Paul,
Thank you very much for the update.
One minor glitch, bar 27 & 28 the rest does not show on jianpu-score. It show 
the same as previous note. 

Thanks Ming for catching that glitch.  Everything worked fine for simple test 
cases with rests, but somehow for those rests in your score the code was 
somehow registering a pitch for those rest events (I don’t know why…) so they 
were being treated as notes.  
The new version 9 that's attached solves this problem.  Not hard to fix once I 
figured out the cause (just check to see if should be a rest first, rather than 
first checking for a pitch as an indication that it should be a note).  Let me 
know if you find any other odd glitches like this.
Oh, and thanks Werner, I agree that it has gotten a lot better!
-Paul



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

Re: [LSR] Colored notes with black outlines (enhancement).

[Paul Morris]

Hi Pierre,

Looks good to me.  Basically, a slightly asymmetrical “shadow” type effect, 
rather than a symmetrical outline (at least with the thinner outlines).

Cheers,
-Paul


> On Apr 29, 2015, at 9:09 AM, Pierre Perol-Schneider 
>  wrote:
> 
> Hi Paul, Hi List,
> 
> The recent discussion about a better 'whiteout' function made me think about 
> some changes.
> See attached (noteHead size remains, only outline's growing).
> Hope you'll like it!
> Cheers,
> Pierre
> 
> 
> 2015-03-27 20:10 GMT+01:00 Pierre Perol-Schneider 
> mailto:pierre.schneider.pa...@gmail.com>>:
> Hi Paul,
> 
> 2015-03-26 23:43 GMT+01:00 Paul Morris  >:
>  
> Oh, well, I was thinking it could just be changed to "7 is a good default"
> so it would match the new input scale.
> 
> But of course (was I asleep?)!! Sorry for the misunderstanding.
> Cheers,
> Pierre
> 
> 
> 

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

Re: Jianpu Notation

[Paul Morris]

On Apr 29, 2015, at 7:18 AM, MING TSANG  wrote:Paul,Thank you very much for the update.One minor glitch, bar 27 & 28 the rest does not show on jianpu-score. It show the same as previous note. Thanks Ming for catching that glitch.  Everything worked fine for simple test cases with rests, but somehow for those rests in your score the code was somehow registering a pitch for those rest events (I don’t know why…) so they were being treated as notes.  The new version 9 that's attached solves this problem.  Not hard to fix once I figured out the cause (just check to see if should be a rest first, rather than first checking for a pitch as an indication that it should be a note).  Let me know if you find any other odd glitches like this.Oh, and thanks Werner, I agree that it has gotten a lot better!-Paul

jianpu9.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lining up key signatures

[James Worlton]

Actually the workaround is from Mats, not Keith. Sorry.
James W

On Wed, Apr 29, 2015 at 1:37 PM, James Worlton  wrote:

> On Tue, Apr 28, 2015 at 7:33 PM, Kieren MacMillan <
> kieren_macmil...@sympatico.ca> wrote:
>
>> Hi James,
>>
>> > >I don't see a way to make the key-cancellation and key-signature
>> simultaneous.
>>
>> The following (hacky!) code seems to work for me:
>>
>> \version "2.19.18"
>>
>> musicA = {
>>   \key c \major
>>   \repeat unfold 2 { c'4 c' c' c' }
>>   \key des \major
>>   des'1
>> }
>>
>> musicB = {
>>   \key fis \major
>>   \repeat unfold 2 { dis'4 dis' dis' dis' }
>>   \override Score.KeyCancellation.X-extent = #'(-0.125 . 0) \key c \major
>>   e'1
>> }
>>
>> \score {
>>   \new StaffGroup <<
>> \new Staff { \musicA }
>> \new Staff { \musicB }
>>   >>
>> }
>>
>> Hope that helps!
>> Kieren.
>>
>
> Thanks everyone for responding. (Sorry for the delay in replying. I've
> been slammed busy since I posted my original question.) The workaround that
> I'm using, which works great for my purposes, is from Keith's comment (#2)
> on the bug tracker:
> https://code.google.com/p/lilypond/issues/detail?id=448
>
> I inserted  \override Staff.KeyCancellation #'X-extent = #'(0 . 0) in the
> Staff just before the key change that resulted in the key cancellations.
> Works great for my needs at this time!
>
> James W.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lining up key signatures

[James Worlton]

On Tue, Apr 28, 2015 at 7:33 PM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi James,
>
> > >I don't see a way to make the key-cancellation and key-signature
> simultaneous.
>
> The following (hacky!) code seems to work for me:
>
> \version "2.19.18"
>
> musicA = {
>   \key c \major
>   \repeat unfold 2 { c'4 c' c' c' }
>   \key des \major
>   des'1
> }
>
> musicB = {
>   \key fis \major
>   \repeat unfold 2 { dis'4 dis' dis' dis' }
>   \override Score.KeyCancellation.X-extent = #'(-0.125 . 0) \key c \major
>   e'1
> }
>
> \score {
>   \new StaffGroup <<
> \new Staff { \musicA }
> \new Staff { \musicB }
>   >>
> }
>
> Hope that helps!
> Kieren.
>

Thanks everyone for responding. (Sorry for the delay in replying. I've been
slammed busy since I posted my original question.) The workaround that I'm
using, which works great for my purposes, is from Keith's comment (#2) on
the bug tracker:
https://code.google.com/p/lilypond/issues/detail?id=448

I inserted  \override Staff.KeyCancellation #'X-extent = #'(0 . 0) in the
Staff just before the key change that resulted in the key cancellations.
Works great for my needs at this time!

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

Re: How to determine if a font is a fallback font?

[David Nalesnik]

On Wed, Apr 29, 2015 at 2:45 AM, Urs Liska  wrote:

>
>
> Am 29.04.2015 um 09:42 schrieb Urs Liska:
>
>> I conclude that the lookup function used in ly:font-config-get-font-file
>> is not absolutely correct, but has never been so.
>> So I tend to ignore this for now and open an issue about it so it could
>> be handled separately *if* someone has the knowledge to do so.
>>
>> Urs
>>
>>
> Sorry, forgot to ask:
> Can you use these fonts the default way at all?
>

Yes--the following works just fine for me:

 \version "2.19.19"

\paper {
  #(define fonts
(set-global-fonts
  #:roman "Kedage"))
}

\markup {
  \char ##x0CE7 \char ##x0CE8 \char ##x0CE9
  \char ##x0CEA \char ##x0CEB \char ##x0CEC
}

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

Re: a proper whiteout function

[Alexander Kobel]

On 04/29/2015 03:03 PM, Kieren MacMillan wrote:

Hi Francisco,


To achieve a whiteout that is useful for music, I think a thick
default 'middle' stroke in white on a lower layer would work.
See example.


YES! This is exactly the kind of thing I’m hoping for.


+1.


Do you think this “function” (bad choice of words here, I know) could be made 
to handle arbitrary [music] grobs, or would one always have to manually work 
through all 4 (?) steps of the process for each grob?


I guess Francisco's example was handmade in Inkscape or similar 
software, but it should be possible to automize it.
AFAIK, all output from Lilypond is laid out in Postscript first, which 
offers support for these operations (at least for text) - see the 
attached example and, e.g., the following page.

  http://paulbourke.net/dataformats/postscript/
The Postscript code for this is as follows:

%!PS-Adobe-3.0
/Times-Bold findfont 30 scalefont setfont

100 400 moveto
(Hello World!)
true charpath
5 setlinewidth
0.5 setgray
stroke

100 400 moveto
(Hello World!)
0 setgray
show

showpage

The main idea is to typeset the object/path/glyph/grob, you name it, 
twice: once in white, non-filled, with thick stroke, and once in the 
actual color. IIUC, this could be achieved by some stencil which is on 
top of the PS-output-stencil.
Unfortunately, I could not make it work with glyphshow, which is what is 
used for the embedded fonts (at least by Lilypond)...



Best,
Alexander


hello.ps
Description: PostScript document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [LSR] Colored notes with black outlines (enhancement).

[Pierre Perol-Schneider]

Hi Paul, Hi List,

The recent discussion about a better 'whiteout' function made me think
about some changes.
See attached (noteHead size remains, only outline's growing).
Hope you'll like it!
Cheers,
Pierre


2015-03-27 20:10 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Paul,
>
> 2015-03-26 23:43 GMT+01:00 Paul Morris :
>
>
>> Oh, well, I was thinking it could just be changed to "7 is a good default"
>> so it would match the new input scale.
>>
>
> But of course (was I asleep?)!! Sorry for the misunderstanding.
> Cheers,
> Pierre
>
>
\version "2.18"
%\version "2.19"

%%http://lsr.di.unimi.it/LSR/Item?id=890

% Two lines commented out below to allow submission to LSR
% Credits: code by Pierre Perol-Schneider and Paul Morris

%% http://lsr.di.unimi.it/LSR/Item?id=890

%%
% LSR workaround:
#(set! paper-alist (cons '("snippet" . (cons (* 210 mm) (* 180 mm))) paper-alist))
\paper {
  #(set-paper-size "snippet")
  tagline = ##f
}
\markup\vspace #.5
#(set-global-staff-size 30)
%%

coloredNoteHeads =
#(lambda (color-outline line-width)
   ;; @var{color-outline} is a boolean for whether
   ;; the outline is colored (#t) or the note head (#f).
   ;; @var{line-width} is a number, the width of
   ;; the outline, 7 is a good default.
   (lambda (grob)
 (let* ((fsz  (ly:grob-property grob 'font-size 0.0))
(mult (magstep fsz))
(stl empty-stencil)
(dur-log (ly:grob-property grob 'duration-log))
(pch (ly:event-property (event-cause grob) 'pitch))
(nnm (ly:pitch-notename pch))
(alt (ly:pitch-alteration pch))
(clr (case nnm
   ((0) (case alt
  ((-1) red) ;; Cbb
  ((-1/2) red) ;; Cb
  ((0) red) ;; C
  ((1/2) red) ;; C#
  ((1) red) ;; C##
  (else black)))
   ((1) (case alt
  ((-1) (x11-color 'orange)) ;; Dbb
  ((-1/2) (x11-color 'orange)) ;; Db
  ((0) (x11-color 'orange)) ;; D
  ((1/2) (x11-color 'orange)) ;; D#
  ((1) (x11-color 'orange)) ;; D##
  (else black)))
   ((2) (case alt
  ((-1) yellow) ;; Ebb
  ((-1/2) yellow) ;; Eb
  ((0) yellow) ;; E
  ((1/2) yellow) ;; E#
  ((1) yellow) ;; E##
  (else black)))
   ((3) (case alt
  ((-1) green) ;; Fbb
  ((-1/2) green) ;; Fb
  ((0) green) ;; F
  ((1/2) green) ;; F#
  ((1) green) ;; F##
  (else black)))
   ((4) (case alt
  ((-1) blue) ;; Gbb
  ((-1/2) blue) ;; Gb
  ((0) blue) ;; G
  ((1/2) blue) ;; G#
  ((1) blue) ;; G##
  (else blue)))
   ((5) (case alt
  ((-1) (x11-color 'purple)) ;; Abb
  ((-1/2) (x11-color 'purple)) ;; Ab
  ((0) (x11-color 'purple)) ;; A
  ((1/2) (x11-color 'purple)) ;; A#
  ((1) (x11-color 'purple)) ;; A##
  (else black)))
   ((6) (case alt
  ((-1) (x11-color 'brown)) ;; Bbb
  ((-1/2) (x11-color 'brown)) ;; Bb
  ((0) (x11-color 'brown)) ;; B
  ((1/2) (x11-color 'brown)) ;; B#
  ((1) (x11-color 'brown)) ;; B##
  (else black)))
   (else black)))
(outline-clr (if color-outline clr black))
(note-clr (if color-outline black clr)))
   
 (set! stl
   (cond
;; quarter notes and smaller
((> dur-log 1)
 (grob-interpret-markup grob
#{
  \markup {
\combine
\with-color #outline-clr
\path #(/ line-width 10)
#'((moveto0.07   -0.40)
   (curveto  -0.310.16   0.90   0.86   1.25   0.40)
   (curveto   1.60   -0.12   0.46  -0.87   0.07  -0.40))
\translate #(cons (* 0.0002 line-width) 0)
\with-color #note-clr
\musicglyph #"noteheads.s2"
  }
#}
  

Re: a proper whiteout function

[Kieren MacMillan]

Hi Francisco,

> To achieve a whiteout that is useful for music, I think a thick
> default 'middle' stroke in white on a lower layer would work.
> See example.

YES! This is exactly the kind of thing I’m hoping for.

Do you think this “function” (bad choice of words here, I know) could be made 
to handle arbitrary [music] grobs, or would one always have to manually work 
through all 4 (?) steps of the process for each grob?

Thank you,
Kieren.



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

Re: Jianpu Notation

[Werner LEMBERG]

> Thank you very much for the update.

Indeed, it starts looking good :-)  Congrats.


Werner

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

Re: a proper whiteout function

[Francisco Vila]

2015-04-29 13:30 GMT+02:00 Alexander Kobel :
> A
> minute of googling brought me to the following page, which nicely shows some
> difficulties, and illustrates why it requires significant effort:
>   http://tavmjong.free.fr/blog/?p=1257

To achieve a whiteout that is useful for music, I think a thick
default 'middle' stroke in white on a lower layer would work. See
example.



-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: a proper whiteout function

[Alexander Kobel]

On 04/29/2015 12:04 PM, Pierre Perol-Schneider wrote:

Hi Kieren, Hi Carl,

I don't think that a standard scaling will help in this case.
Here's an illustration of what could happened :

\markup {
   \combine
   \with-color #magenta
   \scale #'(1.2 . 1.2)
   \musicglyph #"clefs.G"
   \musicglyph #"clefs.G"
}

Whatever glyph re-centering, you'll never get a proper whiteout.
One has to define a specific scaling function that can "blows" the glyph
in order to get a bold one.


Correct. You need an offset (effectively a white stroke around all 
boundary curves) of whatever is rendered, and I think this should not be 
done with Lilypond inspecting the shape, but rather something on the 
lower level. A minute of googling brought me to the following page, 
which nicely shows some difficulties, and illustrates why it requires 
significant effort:

  http://tavmjong.free.fr/blog/?p=1257
I know that boldsymbol or something similar in LaTeX uses (used?) a 
bunch of copies of the same symbol with a slight translation each time, 
but that's 1. conceptually ugly and 2. prone to break for really thin 
lines, so I would not recommend to go this route.


I guess there might be a way to encode such a thing in PostScript? But 
even if there is a simple shortcut, I don't whether it can be applied to 
arbitrary stencils...



Best,
Alexander

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

Re: Jianpu Notation

[MING TSANG]

Paul,
Thank you very much for the update.
One minor glitch, bar 27 & 28 the rest does not show on jianpu-score. It show 
the same as previous note. 
Thanks again. I am looking forward for midi  and lyrics  working.
Immanuel,Ming.  


 On Wednesday, April 29, 2015 1:24 AM, Paul Morris  
wrote:
   

 > On Apr 29, 2015, at 12:54 AM, Paul Morris  wrote:
> 
> Luckily it was not hard to fix.  Attached is a new version.

Well, I spoke too soon… so here’s another version that should work.

-Paul


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

Re: a proper whiteout function

[Pierre Perol-Schneider]

Just thinking...
Here's a rough path drawing that could do the job:

\version "2.19.19"

\markup {
  \combine
  \with-color #magenta
  \path #0.3 #'(
 (moveto   1.17   -0.50)
 (curveto   1.24   -0.53   1.33  -0.43   1.24  -0.36)
 (curveto   0.76   -0.07   0.82   0.57   1.49   0.62)
 (curveto   2.500.60   2.54  -0.65   1.77  -0.84)
 (curveto   0.89   -1.02   0.50  -0.54   0.35  -0.20)
 (curveto   0.260.00   0.07   0.63   1.18   1.77)
 (curveto   2.042.70   2.19   3.28   1.81   4.20)
 (curveto   1.634.62   1.52   4.71   1.49   4.76)
 (curveto   1.474.79   1.43   4.79   1.40   4.76)
 (curveto   1.094.51   0.84   4.15   0.82   3.70)
 (curveto   0.803.00   0.88   2.70   1.03   2.15)
 (curveto   1.351.00   1.48   0.51   1.69  -0.90)
 (curveto   1.93   -2.80   0.68  -2.44   0.57  -2.09)
 (curveto   1.30   -2.34   1.25  -1.07   0.49  -1.39)
 (curveto   0.32   -1.48   0.23  -1.61   0.28  -1.90)
 (curveto   0.39   -2.72   2.12  -3.04   1.85  -0.95)
 (curveto   1.620.70   1.52   0.90   1.21   2.10)
 (curveto   0.753.46   1.14   3.90   1.64   4.20)
 (curveto   1.863.49   1.70   3.05   1.10   2.31)
 (curveto   0.081.24   0.00   0.80   0.00   0.45)
 (curveto   0.00   -0.51   0.73  -1.20   1.72  -1.00)
 (curveto   2.98   -0.72   2.80   1.15   1.45   1.04)
 (curveto   0.500.95   0.52  -0.25   1.17  -0.50)
 )
  \translate #'(0.015 . 0)
  \musicglyph #"clefs.G"
}

Note: X translation is 0.5 * 'line thickness'

The "only" problem is to find a way to get all glyphs coordinates
automagically ...

Cheers,
Pierre


2015-04-29 12:04 GMT+02:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Kieren, Hi Carl,
>
> I don't think that a standard scaling will help in this case.
> Here's an illustration of what could happened :
>
> \markup {
>   \combine
>   \with-color #magenta
>   \scale #'(1.2 . 1.2)
>   \musicglyph #"clefs.G"
>   \musicglyph #"clefs.G"
> }
>
> Whatever glyph re-centering, you'll never get a proper whiteout.
> One has to define a specific scaling function that can "blows" the glyph
> in order to get a bold one.
>
> Cheers,
> Pierre
>
>
>
> 2015-04-29 2:26 GMT+02:00 Kieren MacMillan 
> :
>
>> Hi Carl,
>>
>> >> 1. follow exactly the grob/glyph outline (i.e., not just a
>> rectangle/box,
>> >> as currently implemented);
>> >> 2. include a parameter to set the thickness of the outline; and
>> >> 3. include a parameter to determine whether the whiteout was filled
>> >> throughout, or allowed ³holes² inside (as per the grob/glyph outline).
>> >
>> > I think that doing all 3 things is virtually impossible, given my
>> > understanding of the current state of stencil handling.
>>
>> Okay. Thanks for the information.
>>
>> > I think that a stencil whiteout for simple stencils could be created by
>> > combining two stencils:
>> > 1) the original stencil
>> > 2) a scaled version of the original stencil, colored white, and placed
>> on
>> > a lower layer
>> > The amount of scaling would determine the thickness of the outline.
>> > There would be no way of dealing properly with holes.
>>
>> That might be sufficient for the vast majority of cases I’ve seen.
>> I’ll see if I can work out a quick Scheme function to accomplish what
>> you’ve suggested here.
>>
>> Thanks,
>> Kieren.
>> 
>>
>> Kieren MacMillan, composer
>> ‣ website: www.kierenmacmillan.info
>> ‣ email: i...@kierenmacmillan.info
>>
>>
>> ___
>> 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: a proper whiteout function

[Pierre Perol-Schneider]

Hi Kieren, Hi Carl,

I don't think that a standard scaling will help in this case.
Here's an illustration of what could happened :

\markup {
  \combine
  \with-color #magenta
  \scale #'(1.2 . 1.2)
  \musicglyph #"clefs.G"
  \musicglyph #"clefs.G"
}

Whatever glyph re-centering, you'll never get a proper whiteout.
One has to define a specific scaling function that can "blows" the glyph in
order to get a bold one.

Cheers,
Pierre


2015-04-29 2:26 GMT+02:00 Kieren MacMillan :

> Hi Carl,
>
> >> 1. follow exactly the grob/glyph outline (i.e., not just a
> rectangle/box,
> >> as currently implemented);
> >> 2. include a parameter to set the thickness of the outline; and
> >> 3. include a parameter to determine whether the whiteout was filled
> >> throughout, or allowed ³holes² inside (as per the grob/glyph outline).
> >
> > I think that doing all 3 things is virtually impossible, given my
> > understanding of the current state of stencil handling.
>
> Okay. Thanks for the information.
>
> > I think that a stencil whiteout for simple stencils could be created by
> > combining two stencils:
> > 1) the original stencil
> > 2) a scaled version of the original stencil, colored white, and placed on
> > a lower layer
> > The amount of scaling would determine the thickness of the outline.
> > There would be no way of dealing properly with holes.
>
> That might be sufficient for the vast majority of cases I’ve seen.
> I’ll see if I can work out a quick Scheme function to accomplish what
> you’ve suggested here.
>
> Thanks,
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> 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: PDF portfolio of 2.19.19 docs

[Nick Payne]

On 29/04/2015 16:39, Andrew Bernard wrote:

Dear Nick,

Why make this a PDF portfolio? It’s not readable on Linux where I do my work. 
As I understand it, the point of a portfolio is to incorporate disparate 
document types in one convenient PDF, and to be able to edit them in their 
native format in situ. But these files are all PDF’s. Why don’t you make a 
single PDF of these combined? Then everybody can use it on any system.


Because the portfolio is indexed and you can quickly search for a term 
across all the manuals in the portfolio and see the results in a 
separate window.


I create it for my own use and put it on Dropbox in case it is of use to 
anyone else. It's quite usable on Linux if you install acroread - I use 
it that way myself.


If you want to combine all the manuals as a simple PDF use a tool like 
pdftk. But I can't see the advantage of doing it.


Nick



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

Re: a proper whiteout function

[Simon Albrecht]

Another example: it’s currently impossible to whiteout LyricHyphen – 
which would be nice in combination with SpanBar.


Yours, Simon

Am 29.04.2015 um 02:44 schrieb Kieren MacMillan:

Hi,

Forgive my ignorance, but could you just set the color of the grob to 
white?


No: I want a black grob with a white outline (“padding”), for 
“layering” purposes.


For reference, this is what happens with the current whiteout function:


I’m hoping to avoid the “boxy” look, which I find unattractive.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info 
‣ email: i...@kierenmacmillan.info 



___
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: variable in scheme

[Mattes]

 
Am Mittwoch, 29. April 2015 07:21 CEST, Stephen MacNeil 
 schrieb: 
 
> is this correct?

What's the intent?

> 
> (#'(,num))
> 
> (#'(,str))

No, commas (',') are only allowed within a backquoted form.

Cheers, RalfD


> 
> 
> thanks
> 
> Stephen
 
 
 


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

Re: How to determine if a font is a fallback font?

[Urs Liska]

Am 29.04.2015 um 09:42 schrieb Urs Liska:
I conclude that the lookup function used in 
ly:font-config-get-font-file is not absolutely correct, but has never 
been so.
So I tend to ignore this for now and open an issue about it so it 
could be handled separately *if* someone has the knowledge to do so.


Urs



Sorry, forgot to ask:
Can you use these fonts the default way at all?

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

Re: How to determine if a font is a fallback font?

[Urs Liska]

Am 29.04.2015 um 02:14 schrieb David Nalesnik:



I tried this out on my VM (Ubuntu 10.04.4 -- yes, I need to
update to the most recent LilyDev...)

Should it work for any font that's listed by
ly:font-config-display-fonts?  It works for most of the names
I've tried, though not all.  For example. "Kedage" returns #f.


AFAICS it should, What is the "font name" of Kedage?


Here is a part of the output of (display (ly:font-config-display-fonts):

family DejaVu Sans Mono
 DejaVu Sans Mono:style=Book
family DejaVu Sans Mono
 DejaVu Sans Mono:style=Bold
family Century Schoolbook L
 Century Schoolbook L:style=BoldItalic
family Liberation Serif
 Liberation Serif:style=Italic
family Umpush
 Umpush:style=BoldOblique
family Kedage
 Kedage:style=Normal
family Lohit Bengali
 Lohit Bengali:style=Regular

I simply used the family name, so
\fontExists "Kedage"

Doing so with this list, all return #t except Kedage and Umpush.

Both

(display (ly:font-config-get-font-file "Kedage"))

and

(display (ly:font-config-get-font-file "Umpush"))

return

/usr/share/fonts/truetype/thai/TlwgTypo.ttf

so I presume I am using the right name for the two fonts.


You could try out with my version from the second-to-last post,
which returns the "plain" result of the fontconfig lookup.


OK, here with both Umpush and Kedage I get
Tlwg Typo

\fontExists "Tlwg Typo"
does in fact return #t with the later patch.

but then one of the entries from ly:font-config-display-fonts is

family Tlwg Typo
 Tlwg Typo:style=Oblique

...so I'm pretty sure I understand nothing of what is going on here :(



I assume this has to do with fontconfig not handling these special fonts.

I just installed the  ttf-thai-tlwg package (which installs fonts in a 
slightly different location on my system) which contains Umpush and the 
Tlwg fonts but no Kedage. Umpush and Tlwg Typo are shown in 
ly:font-config-display-fonts;


family Umpush
 Umpush:style=LightOblique

family Tlwg Typo
 Tlwg Typo:style=Bold

while ly:font-config-get-font-file "Umpush" returns the fallback file, 
in my case the emmentaler-11 font file.


fc-match (on the command line) correctly locates both fonts.

I conclude that the lookup function used in ly:font-config-get-font-file 
is not absolutely correct, but has never been so.
So I tend to ignore this for now and open an issue about it so it could 
be handled separately *if* someone has the knowledge to do so.


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

Re: Size of 2.19.19 notation PDF

[Phil Holmes]

- Original Message - 
From: "Nick Payne" 

To: 
Sent: Tuesday, April 28, 2015 11:02 PM
Subject: Size of 2.19.19 notation PDF


I notice that the notation.pdf that I downloaded for 2.19.19 is about half 
the size of its predecessors - 17.2Mb vs 30.8Mb for the 2.19.18 notation 
manual. I downloaded it twice to verify and got the same size each time. On 
a quick check of the file I didn't find anything obviously missing.


All the other manuals as PDFs are much the same size as previously with 
the exception of the snippets manual, which is about 75% of it's previous 
size.


Nick



I wonder whether http://code.google.com/p/lilypond/issues/detail?id=4332 
might be instrumental?


--
Phil Holmes 



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

Re: Size of 2.19.19 notation PDF

[Phil Holmes]

- Original Message - 
From: "Paul Scott" 

To: "Nick Payne" 
Cc: 
Sent: Wednesday, April 29, 2015 2:01 AM
Subject: Re: Size of 2.19.19 notation PDF



On Wed, Apr 29, 2015 at 08:02:08AM +1000, Nick Payne wrote:
I notice that the notation.pdf that I downloaded for 2.19.19 is about 
half

the size of its predecessors - 17.2Mb vs 30.8Mb for the 2.19.18 notation
manual. I downloaded it twice to verify and got the same size each time. 
On

a quick check of the file I didn't find anything obviously missing.

All the other manuals as PDFs are much the same size as previously with 
the
exception of the snippets manual, which is about 75% of it's previous 
size.


I haven't received announcements about new development versions for
several times now.

Paul Scott



I seem to have lost the ability to get such announcements posted to the 
list.  I have tried, and they don't appear.


--
Phil Holmes 



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

Re: mutopia's shortcomings

[Noeck]

> not production-ready.

Hi Urs and Kieren,

thanks for your replies. I don't want to urge you, especially not with
the design of OLL as a library. My interest in it is definitely high.
Your replies make the current status clear:

> not production-ready.

at least not for Mutopia purposes (personally I am using it already).

Cheers,
Joram



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