Re: setTextDim, arpeggioNeutral problem with 2.11.51-1

2008-07-07 Thread sdfgsdhdshd
Graham Percival-2 wrote: > > Run convert-ly. > The lilypond code is generated from another software: so convert-ly is of no use. -- View this message in context: http://www.nabble.com/setTextDim%2C-arpeggioNeutral-problem-with-2.11.51-1-tp18332022p18332385.html Sent from the Gnu - Lilyp

Re: setTextDim, arpeggioNeutral problem with 2.11.51-1

2008-07-07 Thread Graham Percival
Are you offering to help? Yes, a NEWS item would have been nice. We might remember this for .52, but I'm not guaranteeing anything. - Graham Besides, when you're using the UNSTABLE DEVELOPMENT version, you shoudl check convert-ly as soon as anything fails. On Mon, 7 Jul 2008 22:46:55 -0700 (PD

Re: setTextDim, arpeggioNeutral problem with 2.11.51-1

2008-07-07 Thread sdfgsdhdshd
You should announce officially the change in each version: it is really BORING to trial and error to detect the changes in each version. Graham Percival-2 wrote: > > Run convert-ly. And look at the current docs. > - Graham > > On Mon, 7 Jul 2008 22:14:15 -0700 (PDT) > sdfgsdhdshd <[EMAIL PRO

Re: setTextDim, arpeggioNeutral problem with 2.11.51-1

2008-07-07 Thread Graham Percival
Run convert-ly. And look at the current docs. - Graham On Mon, 7 Jul 2008 22:14:15 -0700 (PDT) sdfgsdhdshd <[EMAIL PROTECTED]> wrote: > > In a score that compiled OK with 2.11.49-1 on XP, > with 2.11.51-1 i get an error on all setTextDim, setTextCresc and > everything described in __ 1.3.1 of t

setTextDim, arpeggioNeutral problem with 2.11.51-1

2008-07-07 Thread sdfgsdhdshd
In a score that compiled OK with 2.11.49-1 on XP, with 2.11.51-1 i get an error on all setTextDim, setTextCresc and everything described in § 1.3.1 of the doc. For example, this does not work: si'16\rest \setTextDim la16[_(_\> Same problem with \arpeggio* instructions. For example: re4 \stemD

Re: 2.11.50 broken on PPC (and/or Windows?)

2008-07-07 Thread Stan Sanderson
On Jul 7, 2008, at 9:27 AM, Han-Wen Nienhuys wrote: between .49 (please report: is this really the last version that worked correctly?) and .50 Yes, that has been my experience with Mac OS 10.4.11, PPC. Stan ___ bug-lilypond mailing list bug-li

Re: 2.11.50 broken on PPC (and/or Windows?)

2008-07-07 Thread Han-Wen Nienhuys
I built the .50-2 binary from scratch, but we are still seeing problem reports. The GUB environment itself has not changed 2.11.47, so this looks like something introduced in lilypond itself between .49 (please report: is this really the last version that worked correctly?) and .50 Here is a like

Re: lilypond 2.11.50-2 still crashes (windows xp sp3)

2008-07-07 Thread John Mandereau
On 2008/07/07 06:16 +, E.Weehaeli wrote: > Here is the log I get (without the verbose option, the log is empty): > > GNU LilyPond 2.11.50 [snip] > FontConfig wird initialisiert... > Schriftartverzeichnis wird hinzugefügt: C:/Programme/LilyPondDevel/usr/share/ > lilypond/current/fonts/otf >

accidentals collide with time signature (was Re: position of accidentals)

2008-07-07 Thread Wilbert Berendsen
Op maandag 7 juli 2008, schreef Stefan Thomas: > Dear Lilypond users, > in the below quoted example, the positions of the accidentals are not > convincing, in my opinion. Is there a possibilitie to change this > generally? I rewrote your example just to make it more readable (it's a good habit to