Re: Very strange beaming example

2013-12-27 Thread ul


Zitat von Keith OHara :


Urs Liska  openlilylib.org> writes:


Has anybody seen this before?


No.  If it is Chopin, what Opus and Number is it ?


It's Leopold Godowsky's Study on Chopin's Study op. 25,11.




And, just out of curiosity, how would you do that in LilyPond?


If possible, use a more standard way to show whatever this means.


I see it's _very_ non-standard notation. But I think it's a clever  
idea to express the metric ambiguity of that pattern.
If one were to engrave this composition I don't see any justification  
to 'normalize' that notation.




You can set the number of beams fairly easily, but LilyPond always
draws the outer beams so the span across the inner beams

\relative c''{
\set subdivideBeams = ##t
\once\override Beam #'beam-segments = #
(lambda (g)
  (let ((segs (ly:beam::calc-beam-segments g)))
(display segs)(newline)
segs))
c16[ d e f d
\set #'stemRightBeamCount = #0
e
\set #'stemLeftBeamCount = #0
f g e f g a] r4 }

You could probably add some Scheme code to pick out the middle beams
with "vertical-count 1" and replace them with a single beam.


Sorry, I don't know when I'll have access to a decent computer (i.e.  
one running LilyPond ;-) ) again, so I can't play around with your  
suggestion right now.


Thanks
Urs




___
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


chart alignment

2013-12-27 Thread Bric
How can I avoid the following glitch: 
http://www.flight.us/misc/chart_glitch.png  (the final fret chart is 
misaligned, rising above the adjacent one, instead of vertically 
aligning with the one on its left.)


also struggling with labelling the chords with the chord letters (A, 
C#m, etc.), but that's kind of a separate issue


TIA


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


Re: the "perfect" break-engraver (was Re: [Feature Request] \compressFullBarRests improvement(s))

2013-12-27 Thread Jay Anderson
On Fri, Dec 27, 2013 at 4:08 PM, Kieren MacMillan
 wrote:
> I think the “perfect” break-engraver would admit coding like the following 
> (pseudocode; all numbers in measures):
>
> \lineBreakAt 27
> \lineBreaksAt (12 28 34 48)
> \noLineBreaks (27-30)
> \lineBreaksForbidAt 28
> \lineBreaksAllowAt 34
> etc., and identical for \pageBreaks-
>
> These breaking-codes would be put in the \layout block of a score — cf. the 
> way David N’s engraver currently works — so that there is no need to mix this 
> presentation-layer information into the content layer.
>
> The only additional [optional] argument I can think of is a Staff (or Voice?) 
> "context target”, e.g.,
>
> \lineBreakAt 27 #”soprano"
>
> which would be necessary for polymetric music (where the measures might not 
> all end simultaneously).
>
> Thoughts?

I like the ideas (though I haven't been following the preceding
conversation). Some minor changes would be needed if a break is needed
mid-measure (something like \lineBreakAt 27 3/4). I think I'd still
prefer keeping the breaks within the score section (instead of in the
\layout). Something like:

\score <<
  \new Staff {...}
  \breakmode {
\lineBreakAfter 27
\pageBreakForbidAfter 98
etc...
  }
>>

It could even be expanded into the regular music after parsing. I'm
not sure how possible that would be, but it would isolate the changes
needed. The above would be transformed into something like:
\score <<
  ...
  {
% Assuming '\time 4/4'
s1*27 \break
s1*71 \noPageBreak
etc...
  }
>>

-Jay

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


the "perfect" break-engraver (was Re: [Feature Request] \compressFullBarRests improvement(s))

2013-12-27 Thread Kieren MacMillan
Further to this thread…

> I just think it — or something like it — should be vetted and [the 
> improved/approved version] included with the regular distro.

I think the “perfect” break-engraver would admit coding like the following 
(pseudocode; all numbers in measures):

\lineBreakAt 27
\lineBreaksAt (12 28 34 48)
\noLineBreaks (27-30)
\lineBreaksForbidAt 28
\lineBreaksAllowAt 34
etc., and identical for \pageBreaks-

These breaking-codes would be put in the \layout block of a score — cf. the way 
David N’s engraver currently works — so that there is no need to mix this 
presentation-layer information into the content layer.

The only additional [optional] argument I can think of is a Staff (or Voice?) 
"context target”, e.g.,

\lineBreakAt 27 #”soprano"

which would be necessary for polymetric music (where the measures might not all 
end simultaneously).

Thoughts?

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


Re: Very strange beaming example

2013-12-27 Thread Keith OHara
Urs Liska  openlilylib.org> writes:

> Has anybody seen this before?

No.  If it is Chopin, what Opus and Number is it ?

> And, just out of curiosity, how would you do that in LilyPond?

If possible, use a more standard way to show whatever this means.

You can set the number of beams fairly easily, but LilyPond always
draws the outer beams so the span across the inner beams

\relative c''{
\set subdivideBeams = ##t
\once\override Beam #'beam-segments = #
(lambda (g) 
  (let ((segs (ly:beam::calc-beam-segments g)))
(display segs)(newline)
segs))
c16[ d e f d 
\set #'stemRightBeamCount = #0
e
\set #'stemLeftBeamCount = #0
f g e f g a] r4 }

You could probably add some Scheme code to pick out the middle beams
with "vertical-count 1" and replace them with a single beam.


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


Very strange beaming example

2013-12-27 Thread Urs Liska

Has anybody seen this before?

And, just out of curiosity, how would you do that in LilyPond?

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


Re: [Feature Request] \compressFullBarRests improvement(s)

2013-12-27 Thread Kieren MacMillan
Hi David,

> A content-independent line- and page-breaking system is easy.
> The content is what makes it complicated…

Ah, the semantics cop is on the beat.  ;)

Let me put it another way: Using David’s engraver (which he graciously sent me 
off-list), I am happily adding manual breaks EXTERNAL TO THE CONTENT, and this 
has (for me, anyway) eliminated the need for hacks like \tempBreak, 
\originalBreak, \draftSkip, etc.

I just think it — or something like it — should be vetted and [the 
improved/approved version] included with the regular distro.

We should be encouraging best engraving practices, and simple 
functions/mechanisms like this would allow us to in ways we cannot right now.

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


point and click in gvim

2013-12-27 Thread Stefan Thomas
Dear community,
I would like to enable point and click for okular and gvim on my
ubuntu-machine.
Does someone know, how to do it?
Thanks
Stefan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: [Feature Request] \compressFullBarRests improvement(s)

2013-12-27 Thread David Kastrup
Kieren MacMillan  writes:

> Hi all,
>
>> How would it behave if \draftSkip were, instead of being changed,
> tagged, and you ran lilypond with exclude-tag #draft? (I can't
> remember the syntax off the top of my head, but I think that's
> reasonably close.)
>
> It would be fine… but it’s still a band-aid (um, Band-Aid™) solution.
>
> Lilypond needs a fully-integrated, content-independent, robust line-
> and page-breaking system (q.v., David N’s
> bars-per-line-systems-per-page engraver).

A content-independent line- and page-breaking system is easy.  The
content is what makes it complicated...

-- 
David Kastrup

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


Re: [Feature Request] \compressFullBarRests improvement(s)

2013-12-27 Thread Kieren MacMillan
Hi all,

> How would it behave if \draftSkip were, instead of being changed, tagged, and 
> you ran lilypond with exclude-tag #draft? (I can't remember the syntax off 
> the top of my head, but I think that's reasonably close.)

It would be fine… but it’s still a band-aid (um, Band-Aid™) solution.

Lilypond needs a fully-integrated, content-independent, robust line- and 
page-breaking system (q.v., David N’s bars-per-line-systems-per-page engraver).

Just my 2¢.
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: using latex @ packages within \markup

2013-12-27 Thread David Kastrup
Francois Planiol  writes:

> Thanks!
>
> Best would be directly in lilypond for keeping the working flow.
> I remember, but was it MusixTeX or Lilypond (?) that had a command like
> @latex{ ... here LaTeX stuff ...}
> Isnt it possible?

LilyPond does not run TeX or LaTeX as part of its operation.

You'll probably want to work with lilypond-book which is about the
opposite: then your main document is LaTeX with embedded LilyPond rather
than the other way round.

Of course, the other direction is entirely "possible", but lilypond-book
has been written and is available, and latex-symphony has not yet been
written.  Feel free to do so.

-- 
David Kastrup

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


Re: using latex @ packages within \markup

2013-12-27 Thread Francois Planiol
Thanks!

Best would be directly in lilypond for keeping the working flow.
I remember, but was it MusixTeX or Lilypond (?) that had a command like
@latex{ ... here LaTeX stuff ...}
Isnt it possible?

About #2 solution, I suppose it will be more difficult to control the
size of the picts, and anyway much work to creat all possible
functions.

Francois

2013/12/27, David Kastrup :
> Francois Planiol  writes:
>
>> hello,
>>
>> I dont know how is developping for Riemann symbols right know.
>> I developped this in LaTeX and this works ok for me.
>> The question is how to pack it in a \markup block, using LaTeX and two
>> packages.
>>
>> Some idea?
>>
>> Thanks in advance,
>>
>> Francois
>>
>> \documentclass{article}
>> \usepackage{amsmath}
>> \usepackage{cancel}
>> \begin{document}
>>
>> \[ \overset{8}{\underset{3}{\cancel Dp \: }}
>> \overset{9<}{\overset{7>}{\overset{6}{}}} \]
>>
>> \end{document}
>
> If you are not using LilyPond-book, create an EPS file from your math.
> Something like
>
> \usepackage[active,displaymath,tightpage]{preview}
>
> in your preamble and dvips -E should do the trick for creating a nice
> EPS file.
>
> --
> David Kastrup
>

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


Re: two-column dialogue markup function(s)

2013-12-27 Thread Kieren MacMillan
Hi David,

> By using a non-predefined name for that kind of thing.

H… I was trying that, and getting “undeclared variable” warnings.
Anyway, it seems to work now.

  BEGIN SNIPPET

\version "2.17.97"

#(define-markup-command (mm-feed layout props amount) (number?)
(let ((o-s (ly:output-def-lookup layout 'output-scale)))
  (ly:make-stencil "" '(0 . 0) (cons 0 (abs (/ amount o-s))

#(define-markup-command (put-mm layout props dir amount arg)
(ly:dir? number? markup?) (interpret-markup layout props
  (markup #:put-adjacent Y dir arg #:mm-feed amount)))

#(define-markup-command (dialogue layout props charname text) (markup? 
markup-list?)
  #:properties ((column-width 40)
(bline-skip 2.2)
(char-skip 3.5)
(f-size 9))
  (interpret-markup layout props
#{ \markup \abs-fontsize #f-size \override #`(baseline-skip . ,bline-skip) 
\line {
 \bold \concat { #charname : }
 \hspace #1
 \override #`(line-width . ,column-width) \put-mm #DOWN #char-skip 
\wordwrap #text } #}))

\markup \fill-line {
  \hcenter-in #54 \left-column {
\dialogue Cop { Much better. Now, miss— }
\dialogue Jill { Oh, you can call me ‘Jill’, officer! }
\dialogue Cop { Of course I can, miss. I understand you were at the scene 
of the crime— }
\dialogue Jill { Oh no, I wasn’t actually there. I read it! }
\dialogue Cop { Fine, miss. I understand you ‘read’ the scene of the crime— 
}
  }
  \hcenter-in #54 \left-column {
\dialogue Jill { And then I imagined the whole thing, just like my Grandma 
taught me to do when I was too young to read. }
\dialogue Cop { So essentially you were at the scene of the crime. }
\dialogue Jill { I guess you could say that… Oh, it was horrible. Just 
awful, officer! Those poor little pigs! }
  }
}

  BEGIN SNIPPET

Next questions:

1. Is there an easy way to make the dialogue block left-aligned (i.e., as if it 
were “tabbed” in a word processor)? I could hand-code an \hcenter-in width 
based on the widest character name, but would love a more automated solution.

2. Any other improvements anyone can think of? I’d like to make this function 
(-set) dead-simple for others to drop in and use.

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


Re: two-column dialogue markup function(s)

2013-12-27 Thread David Kastrup
Kieren MacMillan  writes:

> Hi David,
>
>> The wrong quotes, Sir!
>
> That was some weird email or editor translation… sorry.
>
>> Apart from that #:properties ((line-width 12)) will only use the 12 as a
>> default if it is left unspecified, and it never is unspecified.  You
>> need to use a non-predefined name for that kind of thing.
>
> *That* was the main problem, apparently.
> But I would like the user to be able to specify the line-width — how
> can I accomplish that?

By using a non-predefined name for that kind of thing.  How about
column-width?

-- 
David Kastrup

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


Re: improving LilyPond useability

2013-12-27 Thread Alex Loomis
I can proofread the English version.



On Dec 27, 2013, at 4:08 AM, Daniel Rosen  wrote:

>> -Original Message-
>> From: Janek Warchoł [mailto:janek.lilyp...@gmail.com]
>> Sent: Thursday, December 05, 2013 12:58 PM
>> To: Daniel Rosen
>> Cc: LilyPond Users; Jan Nieuwenhuizen; David Kastrup; Urs Liska; Noeck;
>> Kieren MacMillan; Joseph Wakeling; Benjamin CL; Richard Shann
>> Subject: Re: improving LilyPond useability
>> 
>> Hi Daniel,
>> 
>> (sorry for delayed reply - so many emails flying around...)
>> 
>> 2013/12/2 Daniel Rosen :
 -Original Message-
 From: Janek Warchoł [mailto:janek.lilyp...@gmail.com] I've created a
 "Quick-start" tutorial some time ago - my choir colleagues used it
 when crowd-typesetting "Dixit Dominus".  It's only
 6 pages long and covers nearly all basic notation elements than a
 beginner would need - but it's not just a cheat-sheet: it introduces
 and teaches how to use Lily.  Add to that 3 pages explaining how to
 write basic structure and we'd have something that gives an easy (but
 complete enough) introduction to LilyPond in half an hour (as opposed
 to 2 days of reading and heavy thinking for the Learning manual).
>>> 
>>> Sounds awesome.
>>> 
 I'd be more than happy to share this tutorial and translate it, but i
 don't have time to lead an effort to incorporate it in our docs.  So,
 if someone wants to take responsibility for this, i'll help, but
 without support this will not work out!
>>> 
>>> I would definitely be willing to help with this, but I’m afraid that
>>> my skill set may be too limited to take the lead--in particular, I
>>> don't speak any languages well enough to translate them into English
>> without resorting to Google.
>> 
>> That's not a problem at all!  I would translate my materials to English; as 
>> for
>> translating them back to other languages we have people who'd take care of
>> that.  What you'd have to do is to turn my materials into proper
>> documentation: find a place for it, fix wording (my translation probably 
>> won't
>> be perfect), incorporate comments from other developers, etc.
>> 
>> In other words, i'd be glad to make the translation but i want to be sure 
>> that
>> my work will actually be used, and that someone will shepherd it through our
>> contributing process so that it ends up in the official documentation (i 
>> don't
>> have time to this management myself).
>> Of course if you run into *any* technichal difficulty (like "how do i add a 
>> new
>> section to the documentation?"), i'll try to help.  But i need someone that 
>> will
>> take responsibility for getting it done.
>> 
>> Quite frankly, i think this would be an excellent project to get started in
>> contributing to LilyPond.  It doesn't require programming expertise or any
>> particular knowledge - you just have to put some effort in.
>> 
>> best,
>> Janek
> 
> Janek,
> 
> I think I'm about ready to take a swing at this. Shall I email you about it 
> directly, or keep the discussion here on the list?
> 
> DR
> ___
> 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: using latex @ packages within \markup

2013-12-27 Thread David Kastrup
Francois Planiol  writes:

> hello,
>
> I dont know how is developping for Riemann symbols right know.
> I developped this in LaTeX and this works ok for me.
> The question is how to pack it in a \markup block, using LaTeX and two 
> packages.
>
> Some idea?
>
> Thanks in advance,
>
> Francois
>
> \documentclass{article}
> \usepackage{amsmath}
> \usepackage{cancel}
> \begin{document}
>
> \[ \overset{8}{\underset{3}{\cancel Dp \: }}
> \overset{9<}{\overset{7>}{\overset{6}{}}} \]
>
> \end{document}

If you are not using LilyPond-book, create an EPS file from your math.
Something like

\usepackage[active,displaymath,tightpage]{preview}

in your preamble and dvips -E should do the trick for creating a nice
EPS file.

-- 
David Kastrup

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


Re: [Feature Request] \compressFullBarRests improvement(s)

2013-12-27 Thread Alex Loomis
How would it behave if \draftSkip were, instead of being changed, tagged, and 
you ran lilypond with exclude-tag #draft? (I can't remember the syntax off the 
top of my head, but I think that's reasonably close.)



On Dec 27, 2013, at 1:38 AM, "Keith OHara"  wrote:

> On Thu, 26 Dec 2013 18:44:56 -0800, Kieren MacMillan 
>  wrote:
> 
>> I look forward to stress-testing this in the very near future.
> 
> One missing feature is that \mergeSkips doesn't look inside {...} to see if 
> they are empty.  I often set breaks for proofreading and then remove them by 
> defining them as an empty {}
>  draftBreak = {} %% \pageBreak
>  conductor = { s1*5 \draftBreak s1*3 }
> 
> I could make \mergeSkips {s1*5 {} s1*3} check if the {..} is completely empty 
> and output s1*8, but if it gets too complicated for my sake its behavior will 
> confuse and maybe frustrate somebody else.
> 
> 
> ___
> 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: using latex @ packages within \markup

2013-12-27 Thread Alex Loomis
Have you looked at lilypond-book?



On Dec 27, 2013, at 9:12 AM, Francois Planiol  wrote:

> hello,
> 
> I dont know how is developping for Riemann symbols right know.
> I developped this in LaTeX and this works ok for me.
> The question is how to pack it in a \markup block, using LaTeX and two 
> packages.
> 
> Some idea?
> 
> Thanks in advance,
> 
> Francois
> 
> \documentclass{article}
> \usepackage{amsmath}
> \usepackage{cancel}
> \begin{document}
> 
> \[ \overset{8}{\underset{3}{\cancel Dp \: }}
> \overset{9<}{\overset{7>}{\overset{6}{}}} \]
> 
> \end{document}
> 
> ___
> 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


using latex @ packages within \markup

2013-12-27 Thread Francois Planiol
hello,

I dont know how is developping for Riemann symbols right know.
I developped this in LaTeX and this works ok for me.
The question is how to pack it in a \markup block, using LaTeX and two packages.

Some idea?

Thanks in advance,

Francois

\documentclass{article}
\usepackage{amsmath}
\usepackage{cancel}
\begin{document}

\[ \overset{8}{\underset{3}{\cancel Dp \: }}
\overset{9<}{\overset{7>}{\overset{6}{}}} \]

\end{document}

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


Re: two-column dialogue markup function(s)

2013-12-27 Thread Kieren MacMillan
Hi David,

> The wrong quotes, Sir!

That was some weird email or editor translation… sorry.

> Apart from that #:properties ((line-width 12)) will only use the 12 as a
> default if it is left unspecified, and it never is unspecified.  You
> need to use a non-predefined name for that kind of thing.

*That* was the main problem, apparently.
But I would like the user to be able to specify the line-width — how can I 
accomplish that?

> At any rate, the following should get you a bit further:

Thanks!

> I'd actually lean towards _not_ using a markup? as the last argument but
> a markup-list?.  Then the argument can be given as
> 
> \markup \dialogue Kieren { This long line ... }
> 
> which is more natural.

Yes! Thanks again.

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


Re: ANN: Frescobaldi 2.0.12

2013-12-27 Thread Pierre Perol-Schneider
Thanks Wilbert, that's very good news !
Fröhliche Weihnachten !
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Possible bug with TrillSpanner.to-barline?

2013-12-27 Thread David Kastrup
Daniel Rosen  writes:

>> -Original Message-
>> From: Eluze [mailto:elu...@gmail.com]
>>
>> try it in the Staff context:
>> 
>> \override Staff.TrillSpanner.to-barline = ##t
>> 
>> Eluze
>
> Well, that did the trick. A couple things about this are interesting
> to me, though.
>
> First of all, working through the IR, I see the following:
>
> TrillSpanner: "TrillSpanner objects are created by: Trill_spanner_engraver."
> Trill_spanner_engraver: "Trill_spanner_engraver is part of the
> following context(s): CueVoice, DrumVoice,
> GregorianTranscriptionVoice, KievanVoice, MensuralVoice,
> PetrucciVoice, TabVoice, VaticanaVoice and Voice."
>
> So it's unclear to me why typing \override Staff.TrillSpanner.anything
> should have any effect at all. Whenever I get the context wrong when I
> try to \override any other grob property, nothing happens.

There is no such thing as "too far up in the context hierarchy"
regarding grob descriptions and general context properties: as long as
there is no setting in a lower context, any setting in a higher context
will be visible below.

> Second of all, even passing over the first issue, why does it have
> THIS effect (i.e. making the "tr" fail to appear)?

> I'm not a programmer, but it still seems to me like there's some kind of bug 
> here.

Well, the first bug is that you do

\override TrillSpanner.bound-details.left.text but then do
\revert TrillSpanner.bound-details

which is not a matched pair.  The second bug is that you don't use
\temporary \override
so any previous setting is clobbered.

Then LilyPond throws in a longstanding bug of its own which means that

\revert TrillSpanner.bound-details.left.text

will not necessarily only revert the left text.

At any rate, reverting a subproperty in any manner is a recipe for
disaster when other overrides come into play, and \override
TrillSpanner.to-barline is another override.  You get the same problem
if you do \override TrillSpanner.direction = #UP in that place.

\override Staff.TrillSpanner... will tamper with a _different_ property
list (namely the Staff-level one) and thus will not mess with the
subproperty override.  While it is indeed the Staff-level barline
engraver that will ultimately look at the to-barline setting of the
TrillSpanner grob, that's irrelevant since the setting is indeed
established when the grob is _created_, namely at the level of the
Trill_span_engraver.

The best solution is not to use overrides here, but rather tweaks as
their action is definitely temporary.  That keeps you out of the bugs.

\version "2.17.97"

trillSharpMarkup = \markup {
   \concat { \musicglyph #"scripts.trill" \hspace #0.4 \raise #1.9
\teeny \sharp } }

startTrillSpanSharp = \tweak bound-details.left.text \trillSharpMarkup
\startTrillSpan

\relative c' {
   %% Uncomment next line
   \override TrillSpanner.to-barline = ##t
   c1\startTrillSpanSharp |
   c1\stopTrillSpan\startTrillSpan | }


-- 
David Kastrup

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


RE: improving LilyPond useability

2013-12-27 Thread Daniel Rosen
> -Original Message-
> From: Janek Warchoł [mailto:janek.lilyp...@gmail.com]
> Sent: Thursday, December 05, 2013 12:58 PM
> To: Daniel Rosen
> Cc: LilyPond Users; Jan Nieuwenhuizen; David Kastrup; Urs Liska; Noeck;
> Kieren MacMillan; Joseph Wakeling; Benjamin CL; Richard Shann
> Subject: Re: improving LilyPond useability
> 
> Hi Daniel,
> 
> (sorry for delayed reply - so many emails flying around...)
> 
> 2013/12/2 Daniel Rosen :
> >> -Original Message-
> >> From: Janek Warchoł [mailto:janek.lilyp...@gmail.com] I've created a
> >> "Quick-start" tutorial some time ago - my choir colleagues used it
> >> when crowd-typesetting "Dixit Dominus".  It's only
> >> 6 pages long and covers nearly all basic notation elements than a
> >> beginner would need - but it's not just a cheat-sheet: it introduces
> >> and teaches how to use Lily.  Add to that 3 pages explaining how to
> >> write basic structure and we'd have something that gives an easy (but
> >> complete enough) introduction to LilyPond in half an hour (as opposed
> >> to 2 days of reading and heavy thinking for the Learning manual).
> >
> > Sounds awesome.
> >
> >> I'd be more than happy to share this tutorial and translate it, but i
> >> don't have time to lead an effort to incorporate it in our docs.  So,
> >> if someone wants to take responsibility for this, i'll help, but
> >> without support this will not work out!
> >
> > I would definitely be willing to help with this, but I’m afraid that
> > my skill set may be too limited to take the lead--in particular, I
> > don't speak any languages well enough to translate them into English
> without resorting to Google.
> 
> That's not a problem at all!  I would translate my materials to English; as 
> for
> translating them back to other languages we have people who'd take care of
> that.  What you'd have to do is to turn my materials into proper
> documentation: find a place for it, fix wording (my translation probably won't
> be perfect), incorporate comments from other developers, etc.
> 
> In other words, i'd be glad to make the translation but i want to be sure that
> my work will actually be used, and that someone will shepherd it through our
> contributing process so that it ends up in the official documentation (i don't
> have time to this management myself).
> Of course if you run into *any* technichal difficulty (like "how do i add a 
> new
> section to the documentation?"), i'll try to help.  But i need someone that 
> will
> take responsibility for getting it done.
> 
> Quite frankly, i think this would be an excellent project to get started in
> contributing to LilyPond.  It doesn't require programming expertise or any
> particular knowledge - you just have to put some effort in.
> 
> best,
> Janek

Janek,

I think I'm about ready to take a swing at this. Shall I email you about it 
directly, or keep the discussion here on the list?

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


RE: Possible bug with TrillSpanner.to-barline?

2013-12-27 Thread Daniel Rosen
> -Original Message-
> From: Eluze [mailto:elu...@gmail.com]
> Sent: Thursday, December 26, 2013 5:22 PM
> To: Daniel Rosen; lilypond-user@gnu.org
> Subject: Re: Possible bug with TrillSpanner.to-barline?
> 
> 
> Am 26.12.2013 22:22, schrieb Daniel Rosen:
> > In the example below, uncommenting the indicated line results in the
> TrillSpanner only printing the wavy line without the "tr." Is this a bug?
> >
> > \version "2.17.97"
> >
> > trillSharpMarkup = \markup {
> >\concat { \musicglyph #"scripts.trill" \hspace #0.4 \raise #1.9
> > \teeny \sharp } }
> >
> > trillspanSharp = { \override TrillSpanner.bound-details.left.text =
> > \trillSharpMarkup }
> >
> > trillspanNormal = \revert TrillSpanner.bound-details
> >
> > \relative c' {
> >%% Uncomment next line
> >%\override TrillSpanner.to-barline = ##t
> >\trillspanSharp c1\startTrillSpan |
> >\trillspanNormal c1\stopTrillSpan\startTrillSpan | }
> >
> >
> try it in the Staff context:
> 
> \override Staff.TrillSpanner.to-barline = ##t
> 
> Eluze

Well, that did the trick. A couple things about this are interesting to me, 
though.

First of all, working through the IR, I see the following:

TrillSpanner: "TrillSpanner objects are created by: Trill_spanner_engraver."
Trill_spanner_engraver: "Trill_spanner_engraver is part of the following 
context(s): CueVoice, DrumVoice, GregorianTranscriptionVoice, KievanVoice, 
MensuralVoice, PetrucciVoice, TabVoice, VaticanaVoice and Voice."

So it's unclear to me why typing \override Staff.TrillSpanner.anything should 
have any effect at all. Whenever I get the context wrong when I try to 
\override any other grob property, nothing happens.

Second of all, even passing over the first issue, why does it have THIS effect 
(i.e. making the "tr" fail to appear)?

I'm not a programmer, but it still seems to me like there's some kind of bug 
here.

DR

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


RE: ANN: Frescobaldi 2.0.12

2013-12-27 Thread Daniel Rosen
> -Original Message-
> From: Johan Vromans [mailto:jvrom...@squirrel.nl]
> Sent: Thursday, December 26, 2013 2:30 PM
> To: lilypond-user@gnu.org
> Subject: Re: ANN: Frescobaldi 2.0.12
> 
> Wilbert Berendsen  writes:
> 
> > Enjoy, and please report bugs as usual!
> 
> Oh, how wonderful it would have been if a download link had been included
> :)
> 
> -- Johan
> 

http://bit.ly/19mY7Tz

;-)

DR


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