Undocumented TextSpanner property?

2014-09-19 Thread Jakob Schöttl 

The documentation of TextSpanner.bound-details
http://lilypond.org/doc/v2.18/Documentation/internals/textspanner
seems to miss TextSpanner.bound-details.right.attach-dir, because 
overriding this property obviousliy changes the output:


\version 2.19.7
{

  \override TextSpanner.style = #'line
  \override TextSpanner.thickness = #4
  \once \override TextSpanner.bound-details.right.attach-dir = #-4
  g'\startTextSpan e'\stopTextSpan f' b' |
  g'\startTextSpan e'\stopTextSpan f' b' |
}

-- Jakob



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

Re: Undocumented TextSpanner property?

2014-09-19 Thread Neil Puttock 
Sorry, forgot to reply all

On 19 Sep 2014 12:13, Neil Puttock n.putt...@gmail.com wrote:


 On 19 Sep 2014 11:52, Jakob Schöttl jscho...@gmail.com wrote:
 
  The documentation of TextSpanner.bound-details
  http://lilypond.org/doc/v2.18/Documentation/internals/textspanner
  seems to miss TextSpanner.bound-details.right.attach-dir, because
overriding this property obviousliy changes the output:

 There's currently no automated documentation for nested properties in the
Internals Reference.  I think you'll find they're documented in the main
manual though.

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

Re: Notes with different pitches sharing a staff line are engraved strangely

2014-09-19 Thread Ralph Palmer 
On Sun, Aug 31, 2014 at 3:06 PM, Dan Eble d...@faithful.be wrote:

  I'm not top posting.
 % This example might be worth more than one ticket.
 \version 2.18.0
 \language english

 upper = \relative { bs'4 }
 lower = \relative { b'4 }
 chord = \relative { bs' b4 }

 % In this case, the output clearly represents something other than the
 % input.  The input doesn't make much sense in the kinds of music I'm
 % familiar with, so I don't think there is a major problem with what
 % Lilypond has done except that it should warn that it did not engrave
 % what was requested.
 \score {
   \new Staff 
 \set Staff.instrumentName =   
 \dynamicUp \upper
 \\
 \dynamicDown \lower
   
 }

 % In this case, I'm not sure what the output represents, but unless
 % Lilypond is already engraving the expected musical notation, it
 % should warn.
 \score {
   \new Staff 
 \set Staff.instrumentName =  
 \chord
   
 }

 % The part combiner can choose either to put the two notes in separate
 % voices or in the same voice.  Is the current behavior the better
 % choice in this case?  Possibly not.
 \score {
   \new Staff 
 \set Staff.instrumentName = partcombine
 \partcombine \upper \lower
   
 }

 % ... and the CAPTCHA is oddities.  How appropriate.  :-)


Greetings, Dan Eble. Thanks for the email. This has been submitted as Issue
4113. https://code.google.com/p/lilypond/issues/detail?id=4113
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond