Re: \relative issue

2006-03-20 Thread Werner LEMBERG
> >> I consider this unnatural. Additionally, it isn't documented in > >> section `Relative octaves' that the default startpitch is c' (and > >> not c). > > Actually isn't middle C (c') as logical as anything as default. > What's special about the octave below middle C? Consider this: \relati

Re: Segfault in Linux GUB 2.7.40

2006-03-20 Thread Graham Percival
On 20-Mar-06, at 8:16 PM, Cameron Horsburgh wrote: I've just installed the GNU/Linux GUB. It works on a few simpler files, but when given a more complex file it doesn't work. ... programming error: minimise_least_squares (): Nothing to minimise I see the same thing, occurring with input/ty

Segfault in Linux GUB 2.7.40

2006-03-20 Thread Cameron Horsburgh
I've just installed the GNU/Linux GUB. It works on a few simpler files, but when given a more complex file it doesn't work. Here's the last few lines from lilypond --verbose: Interpreting music... [/usr/local//lilypond/usr/share/lilypond//current/fonts/ot f/emmentaler-20.otf][8][16][24][32][40][4

Re: New lilypond-book error message in 7.2.39, mingw

2006-03-20 Thread Han-Wen Nienhuys
Mats Bengtsson wrote: Running lilypond-book fromversion 2.7.39 in Windows now results in: Traceback (most recent call last): File "C:\Program Files\LilyPond\usr\bin\lilypond-book.py", line 75, in ? import lilylib as ly File "out/lilylib.py", line 17, in ? File "C:\Program Files\LilyPond\us

Re: \relative issue

2006-03-20 Thread Paul Scott
Graham Percival wrote: On 19-Mar-06, at 4:27 AM, Werner LEMBERG wrote: I consider this unnatural. Additionally, it isn't documented in section `Relative octaves' that the default startpitch is c' (and not c). Thanks, fixed in CVS. Actually isn't middle C (c') as logical as anything as defau

Re: Dynamic misplacement in 2.7.39

2006-03-20 Thread Graham Percival
On 20-Mar-06, at 2:25 AM, Han-Wen Nienhuys wrote: I'll note that \cr and \cresc aren't in the documentation. Han-Wen, should they be? \cr is a duplication of \< \cresc is deprecated (since it's prefix) Ok. I've added \cr and \decr, but will not add \cresc. - Graham __

Re: \relative issue

2006-03-20 Thread Graham Percival
On 19-Mar-06, at 4:27 AM, Werner LEMBERG wrote: I consider this unnatural. Additionally, it isn't documented in section `Relative octaves' that the default startpitch is c' (and not c). Thanks, fixed in CVS. - Graham ___ bug-lilypond mailing lis

dashed lines in textspanners

2006-03-20 Thread Arno Waschk
dear list, the following example i have been using in 2.7.38 downloadable windows version (as well as my hand-made cygwin 2.7.38 version) gives a continous line which is not what one would expect for 0.96 fraction. (It starts to be continous from around 0.9) No huge problem, BUT: giving 0.

Regression: lyric-hyphen-retain.ly

2006-03-20 Thread Bertalan Fodor
lyric-hyphen-retain.ly - It's strange for me ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Dot and note collision (in \markup)

2006-03-20 Thread Gilles
Hi. [This bug report wasn't acknowledged; so I thought that it might have gone unnoticed.] > The dot collides with the whole note. > > \version "2.6.0" > > \score { > \relative c'' { > \time 2/2 > a1 | > \time 3/2 > \mark \markup { \small { "[" \note #"2" #1.0 "=" \note #"1."

\relative issue

2006-03-20 Thread Werner LEMBERG
Why is \relative { c'' d } the same as { c''' d''' }? I consider this unnatural. Additionally, it isn't documented in section `Relative octaves' that the default startpitch is c' (and not c). Werner ___ bug-lilypond mailing list bug-

Re: incorrect documentation example?

2006-03-20 Thread Graham Percival
On 18-Mar-06, at 2:56 PM, Paul Scott wrote: In the latest development manual in section 10.4.2 "The markup command |\slashSeparator| is provided as a sensible default, for example" is followed by an example with no separator. Yeah. :( The separator _is_ there, but it gets cut off. I'll fi

version 2.7.39 win2k bug convert

2006-03-20 Thread martial
The version 2.7.39 is ok but It is not possible to convert. D:\lilypond\convert>echo off Traceback (most recent call last): File "C:\Program Files\LilyPond\usr\bin\convert-ly.py", line 39, in ? import lilylib as ly File "out/lilylib.py", line 17, in ? File "C:\Program Files\LilyPond\u

Fwd: Bug in textspanner??

2006-03-20 Thread Arno Waschk
--- Forwarded message --- From: "Arno Waschk" <[EMAIL PROTECTED]> To: "Han-Wen Nienhuys" <[EMAIL PROTECTED]> Subject: Bug in textspanner?? Date: Fri, 17 Mar 2006 11:16:15 +0100 dear list, the following example i have been using in 2.7.38 downloadable windows version gives a continous l

Re: Dynamic misplacement in 2.7.39

2006-03-20 Thread Han-Wen Nienhuys
Graham Percival wrote: On 19-Mar-06, at 12:43 PM, Cameron Horsburgh wrote: In 2.7.39 dynamic changes using the 'dim' or 'cresc' commands offsets the placement of the instruction by one note. I don't know if this happened in other versions. \cresc needs to be defined before a note. Yes, in

Re: \set Staff.instrument=\markup { \center-align { "Instrument." }} still has alignment problems.

2006-03-20 Thread Han-Wen Nienhuys
Trent Johnston wrote: Hi All, Using \mark { \center-align etc... still doesn't format the instrument names correctly. As can be seen in the attached image (V2-7-39instrument) the names of staves are all over the place. The stable 2-6-5 windows the names are set out correctly (see V2-6-5instrum

Re: Je ne peux pas lancer "lilypond-2.6.5-1" sur mon XP tablet PC

2006-03-20 Thread martial
> "lilypond-2.6.5-1" does not install on my XP Tablet PC, Windows 2003. > > Message error is: NSIS Error > > Thank you for any help va voir là (follow this link) http://tinyurl.com/mecrd ___ bug-lilypond mailing list bug-lilypond@gnu.org http://list

bar number positioning bug

2006-03-20 Thread Tuukka Verho
In 2.7.39 the bar number placement behavior is rather odd. When there is no key signature, bar numbers are typeset in the left hand side of the clef as in previous versions, but otherwise they are placed next to the key signature. The following code demonstrates the issue: \version "2.7.39"