headers
Alex Klein | 1 Aug 2004 17:26

Downbow symbol below slur / slur touches staccato dot

Hi guys,
just compiled and tested the new 2.3.9 and I have to say it looks great 
so far. As I write mostly string music at the moment (and thus often use 
slurs to indicate bowing), I have to nag a bit on the slurs. Most of the 
look great, but there are still some cases where the slur hits the 
staccato dots (most of the time I've got two eights that are staccato 
with a slur to indicate that they have the same bowing direction).

An even more severe problem is the following. When using the downbow 
symbol on a note with a slur (in my case a note that is stemmed down), 
the slur starts ABOVE the downbow symbol. Bowing symbols as well as 
fingering instructions are musical comments and should never be between 
the notes and the slur.
With every release the output looks better and better, so keep up the 
good work. But I would recommend to fix the slur-problems above before 
announcing version 3.0 as this is really annoying when doing string works.
Cheers

Alex

P.S.: If you need a test file for the above, just send me an email...
Permalink | Reply | 1 comment |
headers
Will Oram | 2 Aug 2004 04:39

/a vs. /one

I know either HW or Jan called this a bug two versions ago, but it's a 
problem I can't quite pinpoint.

I have a definitions file for storing frequently used markups. This 
line causes all instances of it in music (eg, a4_\a ) to be called a 
parse error:

a = \markup { \bold {a 2} }

The line below it, though, is accepted everywhere:

one	= \markup { \bold {1.}}

What's the difference between these two? How can I tweak it?

Best,

Will Oram // Genius  <at>  Large // AIM spamguy21
spamguy (at) foxchange (dot) com // wro1 (at) cwru (dot) edu
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 2 Aug 2004 18:13
Picon

text spanner and skips


%
% text-spanner-and-skips.ly
%
% wl <at> gnu.org
%

\version "2.2.5"

\header { texidoc = "
Using skips as `anchors' for TextSpanner objects causes programming error
messages and badly rendered results if there isn't enough (natural?) space.
" }

\score {
  \notes \relative c' {
\override TextSpanner #'edge-text = #'("rall. " . "")
    s1\startTextSpan |
    s1 |
    s1\stopTextSpan |
    s1 |
  }

  \paper {
    indent = 0.0\mm
    linewidth = 70.0\mm
  }
}

% EOF
(Continue reading)

Permalink | Reply | 1 comment |
headers
John Sellers | 2 Aug 2004 18:46

incorrect spacing on Vota Brackets when Cord names are present.

In the example volta-chord-names.ly processed with LilyPond version 
2.2.4 on the website at: 
http://lilypond.org/doc/v2.2/input/test/out-www/collated-files.html , 
there is too much vertical spacing between the staff and the chordname,  
and too much vertical spacing between the chordname and the volta 
alternative endings brackets.

In my netscape browser pointed at 
http://lilypond.org/doc/v2.2/input/test/out-www/collated-files.html
 the vertical spacing between the top of the staff to the mid point of 
the chord name appears to be exactly the difference in hight between the 
bottom and top lines of the staff.  The same difference appears in 
vertical spacing between the mid point of the chord name to the base of 
the bracket.

Also, I saw different behavior between LilyPond version 2.2.4 and 2.0.0 
in this regard.
Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 2 Aug 2004 18:56
Picon
Picon
Favicon

text spanner and skips


fixed.

wl <at> gnu.org writes:
> 
> %
> % text-spanner-and-skips.ly
> %
> % wl <at> gnu.org
> %
> 
> \version "2.2.5"
> 
> \header { texidoc = "
> Using skips as `anchors' for TextSpanner objects causes programming error
> messages and badly rendered results if there isn't enough (natural?) space.
> " }
> 
> 
> \score {
>   \notes \relative c' {
> \override TextSpanner #'edge-text = #'("rall. " . "")
>     s1\startTextSpan |
>     s1 |
>     s1\stopTextSpan |
>     s1 |
>   }
> 
>   \paper {
>     indent = 0.0\mm
(Continue reading)

Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 2 Aug 2004 18:57
Picon
Picon
Favicon

Downbow symbol below slur / slur touches staccato dot


.ly sample please.

AlexK <at> athenstean.com writes:
> An even more severe problem is the following. When using the downbow 
> symbol on a note with a slur (in my case a note that is stemmed down), 
> the slur starts ABOVE the downbow symbol. Bowing symbols as well as 
> fingering instructions are musical comments and should never be between 
> the notes and the slur.

--

-- 

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 2 Aug 2004 18:57
Picon
Picon
Favicon

/a vs. /one

spamguy <at> foxchange.com writes:
> I know either HW or Jan called this a bug two versions ago, but it's a 
> problem I can't quite pinpoint.
> 
> I have a definitions file for storing frequently used markups. This 
> line causes all instances of it in music (eg, a4_\a ) to be called a 
> parse error:
> 
> a = \markup { \bold {a 2} }
> 
> The line below it, though, is accepted everywhere:
> 
> one	= \markup { \bold {1.}}
> 
> What's the difference between these two? How can I tweak it?

a is the name of a note. try

  "a" = \markup ...

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
John Sellers | 2 Aug 2004 19:17

2.3.10 - version num and alternative brackets vertical spacing

Home page link to version 2.3.10 points to a page that says version 2.3.9.

Also in Regression tests for 2.3.9 all alternative repeat brackets 
displayed in my netscape 7.1 browser appear to have waste space between 
the staff and the bracket.  I went into several of my fake books and 
other music literature for the violin, and all published literature did 
not have this kind of vertical waste space.

Also I looked at a couple of popular fake books which have lead sheets 
for simple one-staff songs.  I saw two styles.  One involved a total of 
two text lines of hight as you would see in any book, boxed by the 
bracket and staff with no additional vertical waste space with the 
repeat numbers on the higher line and the chord names on the lower line 
next to but not touching the staff.  The other used about 1 1/2 text 
lines with the vertical position of the chords and the repeat number 
overlapping vertically by about 50%.  In both cases the repeat bracket 
vertical line was extended to, but not touching the staff.
Permalink | Reply | 0 comments |
headers
Stefaan | 3 Aug 2004 00:24
Picon
Picon

variable parsing bug in 2.3.x

Well at least I think it is a bug:

Variable names apparently can no longer contain digits in 2.3.x
Convert-ly does not warn or change anything about offending definitions.

I have tried with the 2.3.6 package (i.e. the most recent one that is 
available in .deb format).

%% example: works in 2.2.3 but fails in 2.3.6 with "error: syntax
%% error, unexpected DIGIT, expecting '='"
%% on the line where v1 is defined.

v1 = \notes{a}
\score { \v1 }
Permalink | Reply | 1 comment |
headers
アシストジャパン・コーポレーション | 3 Aug 2004 08:34
Picon

–¢³‘øL¦ <at> š—L–¼——Dvs—ŽqZ¶vslÈš ŒƒˆÀ‚c‚u‚c”Ì”„ŠJŽnI 


////////////dq[ <at> ɊÂ\L////////////
̃[AhX͑Mpł̂
zM]ȂiIvgAEgj͂ł肢܂B
 <at>  <at> http://www.delivery-mail.com/opt-out/tmmail.cgi
Mҁ <at> AVXgWpER[|[V
Z <at>  <at>  <at> 107-0052 <at> s`ԍ4-6-3
///////////////////////////////////////////////////



 <at>  <at> yA_gcuc≮ <at> w9800YENlbgxz
 <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at> -VOL.1-


dddddddddd

cucArfIAA_gObYil̂jȂRRII
  <at>  <at> 
 <at>  <at> 荢ȃAȃA_giXCWOO~ψII

dddddddddd
 <at> 

 <at>  <at>   <at> jĩI[vjOZ[D]JÒII
 <at>  <at> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
\\\\\\\\\\\\\\\\\\\\\\\\
 <at>  <at> Pe <at> qZEuZVOL.1 <at> i10Zbgj
 <at>  <at> 
 <at>  <at>  <at>  <at>  <at>  <at> 艿 \32,260 \9,800
(Continue reading)

Permalink | Reply | 0 comments |

Gmane