Re: Patch: issue #659

2010-02-15 Thread Marc Hohl
Marc Hohl schrieb: [...] Are you sure about "S:|" and "|:S" ? Ah, I think I understand - but I'll use ":|S." and ".S|:" for situations where the segno *and* the repeat sign should be placed on the same line. Marc ___ lilypond-devel mailing list

Re: Patch: issue #659

2010-02-15 Thread Marc Hohl
Alexander Kobel schrieb: [...] So, what do I think is useful? In the optimum, we should have the following combinations: Diving into your proposals, I have some comments: On a line break: - "|S" ("|" end of line, "S" begin of line) - "S|" ("S" only end of line) Ok. - "||S" ("||" end of

Re: Patch: issue #659

2010-02-09 Thread Marc Hohl
Hi Alexander, Alexander Kobel schrieb: [...] I just noticed that the 'extra-offset won't influence the spacing of the notes before the bar line. The better property to tweak should be the right-edge extra space, but this does not work if the line ends prematurely. (See the attached exa

Re: Patch: issue #659

2010-02-09 Thread Marc Hohl
Alexander Kobel schrieb: Marc Hohl wrote: Alexander Kobel schrieb: I don't really know if I saw the "||-before-break, S-after-break" combination, but I think it makes sense to offer it since coda parts are often seperated by double bar lines when the "default" segno sign is above them. I'll s

Re: Patch: issue #659

2010-02-08 Thread Alexander Kobel
Marc Hohl wrote: Alexander Kobel schrieb: I don't really know if I saw the "||-before-break, S-after-break" combination, but I think it makes sense to offer it since coda parts are often seperated by double bar lines when the "default" segno sign is above them. I'll see what I can find in real

Re: Patch: issue #659

2010-02-03 Thread Marc Hohl
Alexander Kobel schrieb: [...] I just noticed that the 'extra-offset won't influence the spacing of the notes before the bar line. The better property to tweak should be the right-edge extra space, but this does not work if the line ends prematurely. (See the attached example.) Still, like T

Re: Patch: issue #659

2010-01-21 Thread Alexander Kobel
Marc Hohl wrote: Alexander Kobel schrieb: Marc Hohl wrote: Trevor Daniels schrieb: It is easy for a user to move the sign to the end of the staff lines with \once \override Score.BarLine #'extra-offset = #'(1 . 0) \once \override Score.SpanBar #'extra-offset = #'(1 . 0) [...] Would it m

Re: Patch: issue #659

2010-01-20 Thread Marc Hohl
Alexander Kobel schrieb: Marc Hohl wrote: Trevor Daniels schrieb: It is easy for a user to move the sign to the end of the staff lines with \once \override Score.BarLine #'extra-offset = #'(1 . 0) \once \override Score.SpanBar #'extra-offset = #'(1 . 0) if this was really wanted, althou

Re: Patch: issue #659

2010-01-20 Thread Trevor Daniels
Marc Hohl wrote Wednesday, January 20, 2010 9:54 AM Trevor Daniels schrieb: [...] I would not worry about this. As Alexander has pointed out, examples showing the staff lines extending through the sign and not extending through the sign can be found. It is easy for a user to move the sign

Re: Patch: issue #659

2010-01-20 Thread Alexander Kobel
Marc Hohl wrote: Trevor Daniels schrieb: It is easy for a user to move the sign to the end of the staff lines with \once \override Score.BarLine #'extra-offset = #'(1 . 0) \once \override Score.SpanBar #'extra-offset = #'(1 . 0) if this was really wanted, although this would admittedly p

Re: Patch: issue #659

2010-01-20 Thread Marc Hohl
Trevor Daniels schrieb: [...] I would not worry about this. As Alexander has pointed out, examples showing the staff lines extending through the sign and not extending through the sign can be found. It is easy for a user to move the sign to the end of the staff lines with \once \override

Re: Patch: issue #659

2010-01-19 Thread Trevor Daniels
Marc Hohl wrote Tuesday, January 19, 2010 10:09 AM Trevor Daniels schrieb: Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is

Re: Patch: issue #659

2010-01-19 Thread Alexander Kobel
Marc Hohl wrote: I don't know. The staff lines should end a little bit earlier, see http://lilypond.googlecode.com/issues/attachment?aid=-394070284723943851&name=segno-end.png&inline=1 I don't think it is a good idea to let the segno sign reach into the margin, so the staff lines have to end

Re: Patch: issue #659

2010-01-19 Thread Marc Hohl
Trevor Daniels schrieb: Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the bar

Re: Patch: issue #659

2010-01-19 Thread Trevor Daniels
Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the barlines? I found out how t

Re: Patch: issue #659

2010-01-19 Thread Marc Hohl
Trevor Daniels schrieb: Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the barlines? I found out how to define a whiteout stencil, but it seems that it is pla

Re: Patch: issue #659

2010-01-18 Thread Trevor Daniels
Marc Hohl wrote Monday, January 18, 2010 8:13 PM Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Hmmm - you are right. Is it possible to whiteout this small part of the barlines? I found out how to define a whiteout stencil, but it seems that it is placed *over* the segno sign

Re: Patch: issue #659

2010-01-18 Thread Marc Hohl
Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/8 Marc Hohl : Yes, the picture in the tracker has one loop missing, but in all other sources, the sign looked (mainly) as mine. How do they deal with the segno at the end of a line though? The tracker example is aligned as a normal barl

Re: Patch: issue #659

2010-01-11 Thread Marc Hohl
Neil Puttock schrieb: 2010/1/8 Marc Hohl : Yes, the picture in the tracker has one loop missing, but in all other sources, the sign looked (mainly) as mine. How do they deal with the segno at the end of a line though? The tracker example is aligned as a normal barline (i.e., with the

Re: Patch: issue #659

2010-01-10 Thread Neil Puttock
2010/1/8 Marc Hohl : > Yes, the picture in the tracker has one loop missing, but in > all other sources, the sign looked (mainly) as mine. How do they deal with the segno at the end of a line though? The tracker example is aligned as a normal barline (i.e., with the double-bar at the right edge)

Re: Patch: issue #659

2010-01-08 Thread Marc Hohl
Marc Hohl schrieb: Neil Puttock schrieb: 2010/1/6 Marc Hohl : I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. Very nice. It's a bit different from the examples posted on the tr

Re: Patch: issue #659

2010-01-07 Thread Marc Hohl
Neil Puttock schrieb: 2010/1/6 Marc Hohl : I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. Very nice. It's a bit different from the examples posted on the tracker, but looks ve

Re: Patch: issue #659

2010-01-07 Thread Neil Puttock
2010/1/6 Marc Hohl : > I've just posted a patch for the alternate segno sign. > To use the new symbol stored at scripts.varsegno, I have > adapted the arguments for the \bar command. Very nice. It's a bit different from the examples posted on the tracker, but looks very elegant. :) Two general

Patch: issue #659

2010-01-06 Thread Marc Hohl
Hello all, I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. To start a sengo part, you can use \bar ".§" or \bar "§" at the end of the segno part, use \bar "§.". The difference between ".§"