Urs Metzger wrote:
In the following snippet, the augmentation dot should appear immediately after
the a, not after the g.
This is a known issue, but it is quite difficult to fix. Please see the
workaround in:
http://code.google.com/p/lilypond/issues/detail?id=339&can=1&q=dot
Cheers,
- Gra
Richard TALBOT wrote:
Inside a slur, the command \ acciaccatura doesn't work.
When I want to use an \acciaccatura command in a slur, the program can't close
the slur
That's because an \acciaccature includes a slur. Perhaps you want to
use phrasing slurs \( \) for the big slurs?
Cheers,
-
Issue 338: weird space in the middle of a repeat sign
http://code.google.com/p/lilypond/issues/detail?id=338
Comment #2 by hallstein.lunde:
Test of solution outlined in comment #1. See attached file
Attachments:
foo1.png 1.5 KB
--
You received this message because you are listed in
> Note, I'm not top-posting
\header {
texidoc = "Note too close (collides?) with polyphony"
reportedin = "2.10.5"
}
\version "2.10.5"
\paper{ragged-right=##t}
{
<<
{ c'8 e' g' c'' r2 } \\
{ c'2 r2 }
>>
}
...I have an actual scan of expected output in this c
Arvid -
Please, post a score (.ly and .pdf) somewhere with all the goodies you have
developed, especially the cover stuff.
- Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Arvid Grøtting
Sent: Saturday, November 04, 2006 6:5
Inside a slur, the command \ acciaccatura doesn't work.
When I want to use an \acciaccatura command in a slur, the program can't close
the slur
For example, when I try :
fad16\!( sol do sib \acciaccatura sib lab sol \acciaccatura sol fad mib)
the program says :
AVERTISSEMENT : impossible de
Tiago -
Not pretty, but:
XXX = \markup { "XXX" \postscript #"0.2 setlinewidth -5.2 -0.2 moveto 4.5 0
rlineto stroke" }
YY = \markup { "YY" \postscript #"0.2 setlinewidth -3.5 -0.2 moveto 3.0 0
rlineto stroke" }
{ c''^\XXX g'^\YY }
- Bruce
-Original Message-
From: [E
You are completely right. The implementation of the repeat handling
should be
corrected to correspond to normal typesetting conventions. This problem
has been
brought up on the mailing lists several times over the years, but nobody
has fixed it yet.
Clearly, the "explanation" provided in the cur
