Re: Text above repeat signs

2014-05-01 Thread david morawski
consistent method for labeling repeats without having to worry about which line they are going to end up on. On Thu, May 1, 2014 at 1:40 PM, Federico Bruni wrote: > 2014-05-01 20:27 GMT+02:00 David Morawski : > >> > I'm not top posting. >> >> Hello, >> >&

Re: Text above repeat signs

2014-05-01 Thread Federico Bruni
2014-05-01 21:13 GMT+02:00 david morawski : > Thank you, Federico. Changing your code to > > \once \override Score.RehearsalMark #'break-visibility = > #end-of-line-visible > \once \override Score.RehearsalMark #'self-alignment-X = #RIGHT > > worked for me. Is this considered a bes

Re: Text above repeat signs

2014-05-01 Thread Federico Bruni
2014-05-01 20:27 GMT+02:00 David Morawski : > > I'm not top posting. > > Hello, > > I'm having trouble putting text above repeat signs, specifically when the > :| > symbol precedes a linebreak. In the following example, the text ("3x") that > shou

Text above repeat signs

2014-05-01 Thread David Morawski
> I'm not top posting. Hello, I'm having trouble putting text above repeat signs, specifically when the :| symbol precedes a linebreak. In the following example, the text ("3x") that should belong to the first :| gets pushed on top of the |: of the next volta repeat. \

Re: Percent signs in ghostscript output files should be duplicated

2013-06-23 Thread Federico Bruni
thanks Pavel, added with label defect: https://code.google.com/p/lilypond/issues/detail?id=3421 2013/6/23 Pavel Roskin > Percent signs in ghostscript output files (i.e. those after -sOutputFile) > should be duplicated on the command line. It's not a format string bug as &g

Percent signs in ghostscript output files should be duplicated

2013-06-22 Thread Pavel Roskin
Percent signs in ghostscript output files (i.e. those after -sOutputFile) should be duplicated on the command line. It's not a format string bug as I initially suspected, it's a documented feature. http://ghostscript.com/doc/8.63/Use.htm#File_output "Note: Since the % chara

Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2012-01-14 Thread lilypond
Comment #3 on issue 2139 by elu...@gmail.com: Doc AU: command line options - where to use equal signs in short and long term definitions http://code.google.com/p/lilypond/issues/detail?id=2139 I'm confused - I've never used -d= before, I always used -d… but in fact -dgui works

Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2012-01-14 Thread lilypond
Comment #2 on issue 2139 by pkx1...@gmail.com: Doc AU: command line options - where to use equal signs in short and long term definitions http://code.google.com/p/lilypond/issues/detail?id=2139 Before I dive in to this, I think we need some consensus. At the moment we have (for example) -d

Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2011-12-27 Thread James
Hello, On 27 December 2011 11:55, -Eluze wrote: > > > lilypond-4 wrote: >> >> Updates: >>       Status: Started >>       Owner: pkx1...@gmail.com >> >> Comment #1 on issue 2139 by pkx1...@gmail.com: Doc AU: command line >> options >> - wh

Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2011-12-27 Thread -Eluze
lilypond-4 wrote: > > Updates: > Status: Started > Owner: pkx1...@gmail.com > > Comment #1 on issue 2139 by pkx1...@gmail.com: Doc AU: command line > options > - where to use equal signs in short and long term definitions > http://code.google.com/p/lil

Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2011-12-26 Thread lilypond
Updates: Status: Started Owner: pkx1...@gmail.com Comment #1 on issue 2139 by pkx1...@gmail.com: Doc AU: command line options - where to use equal signs in short and long term definitions http://code.google.com/p/lilypond/issues/detail?id=2139 I'd like to wait until

Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

2011-12-25 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation New issue 2139 by elu...@gmail.com: Doc AU: command line options - where to use equal signs in short and long term definitions http://code.google.com/p/lilypond/issues/detail?id=2139 when reading the line -d,--define-default=var=val

Re: Correct Figured Bass signs (slashed and crossed numbers)

2011-06-09 Thread Reinhold Kainhofer
Am Donnerstag, 9. Juni 2011, 13:22:06 schrieb Nils: > I need correct baroque figured bass signs not the modern equivalents which > Lilypond provides. Yes, that's a valid feature request in my eyes (actually, I'll need them too for my own editions). > For example the slashed 6

Issue 1178 in lilypond: Measure_grouping_engraver uses non-standard signs

2010-07-08 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1178 by Carl.D.Sorensen: Measure_grouping_engraver uses non-standard signs http://code.google.com/p/lilypond/issues/detail?id=1178 As currently implemented, the measure_grouping_engraver uses a triangle for groups

Re: Changing conducting signs

2010-06-25 Thread Patrick McCarty
On Wed, Jun 16, 2010 at 5:47 AM, Carl Sorensen wrote: > On 6/16/10 1:58 AM, "flup2" wrote: >> >> I would like to know if somebody knows how conductng signs ( >> http://lsr.dsi.unimi.it/LSR/Item?id=259 >> http://lsr.dsi.unimi.it/LSR/Item?id=259 ) are created

Re: Changing conducting signs

2010-06-16 Thread Carl Sorensen
Copying to -devel to get developer feedback, and to bug to get the issue in the tracker if it belongs there. On 6/16/10 1:58 AM, "flup2" wrote: > > I would like to know if somebody knows how conductng signs ( > http://lsr.dsi.unimi.it/LSR/Item?id=259 > http://lsr.dsi.un

Re: signs

2008-01-13 Thread Werner LEMBERG
> > > Could you tell me what the exact meanings of these barlines are? > > > The NR hasn't a literal description: > > > > Indeed. So here it is. > > These are shown in 1.2.5 Bar lines -- but of course they're only > shown in the picture example. Again, all of the documentation is > written with t

Re: signs

2008-01-13 Thread Graham Percival
On Sun, 13 Jan 2008 09:57:52 +0100 (CET) Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > Could you tell me what the exact meanings of these barlines are? > > The NR hasn't a literal description: > > Indeed. So here it is. These are shown in 1.2.5 Bar lines -- but of course they're only shown in t

Re: signs

2008-01-13 Thread Werner LEMBERG
> :|two repeat dots followed by a thick line Oops! This should be :|two repeat dots, a thin line, and a thick line Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: signs

2008-01-13 Thread Werner LEMBERG
[I've forwarded your mail to the bug-lilypond list.] > Could you tell me what the exact meanings of these barlines are? > The NR hasn't a literal description: Indeed. So here it is. > \bar ".|" \bar ".|." \bar "|." \bar ":|:" > (What kind of repetition barline is it?) | a thin line ||

Re: Beams across repeat signs

2005-01-16 Thread Erik Sandberg
On Tuesday 11 January 2005 20.02, Erik Ronström wrote: > According to the regression tests, LilyPond does not typeset beams > across manual repeat signs. That is true. However, it does place beams > across repeat-voltas, if the repeat sign is mid-bar. Is there a way to > avoid that w

Re: Beams across repeat signs

2005-01-13 Thread Mats Bengtsson
Seems like a bug to me! Example: \version "2.4.2" \relative c' { \repeat volta 2 {c d e16 f } e f g4 | } /Mats Erik Ronström wrote: According to the regression tests, LilyPond does not typeset beams across manual repeat signs. That is true. However, it does place beams across re