Re: Clef changes in retrograde, will only print a new clef. note positions will not change to accommodate the new clef

2013-07-07 Thread Federico Bruni
2013/7/6 Thomas Morley > General policy-question: > Sometimes I reply to some mails on this list, before a > bug-squad-member answered. (To do some analysis; solve a problem, > which would have better sent to the user-list; etc) > Is this ok? Or should I let a bug-squad-member answer first? > yo

Re: Marks right-aligned in unstable

2013-07-07 Thread Federico Bruni
2013/7/7 Thomas Morley > 2013/7/7 Federico Bruni : > > > BTW, I've never received the email from Timothy (spam folder already > > checked). > > I think that it's not the first time that happens. > > > > Hmm. > Have you got > > http://lilypond.1069038.n5.nabble.com/Clef-changes-in-retrograde-wil

Re: Clef changes in retrograde, will only print a new clef. note positions will not change to accommodate the new clef

2013-07-07 Thread Federico Bruni
2013/6/23 Thomas Morley > So yes, \retrograde should be improved. > I'd call it an enhancement-request. > added here: https://code.google.com/p/lilypond/issues/detail?id=3445 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mail

Re: Marks right-aligned in unstable

2013-07-07 Thread Thomas Morley
2013/7/7 Federico Bruni : > BTW, I've never received the email from Timothy (spam folder already > checked). > I think that it's not the first time that happens. > Hmm. Have you got http://lilypond.1069038.n5.nabble.com/Clef-changes-in-retrograde-will-only-print-a-new-clef-note-positions-will-n

Re: No warning for misspelled properties.

2013-07-07 Thread Federico Bruni
2013/7/7 Thomas Morley > although they're misspelled, neither of the commands in the following > code returns a warning, nor does 2.16.2 (apart from the _expected_ > syntax error). > Selfcompiled 2.17.22 doesn't throw an error, too. > > \version "2.17.21" > > { > \override Score.RehearsalMark #

Re: Marks right-aligned in unstable

2013-07-07 Thread Federico Bruni
2013/7/7 Thomas Morley > thanks for your report, seems this doesn't work accurately since some time. > > 2.12.3 was good. > With 2.14.2 aligning to time-signature went wrong. > Same with 2.16.2. > 2.17.21 aligns all wrong. > Many thanks for your analysis! I've marked it as a regression: https://

Re: Issue 3363: Scripts misplaced with cross-staff slurs

2013-07-07 Thread Federico Bruni
2013/7/2 Timothy Lanfear > > I'm not top posting. > > Issue 3363 has reappeared in 2.17.20; 2.17.19 was fine. I'm using Windows > 32-bit. > this issue was reopened by Keith end of May so no need to open a new one ___ bug-lilypond mailing list bug-lilyp

No warning for misspelled properties.

2013-07-07 Thread Thomas Morley
Hi, although they're misspelled, neither of the commands in the following code returns a warning, nor does 2.16.2 (apart from the _expected_ syntax error). Selfcompiled 2.17.22 doesn't throw an error, too. \version "2.17.21" { \override Score.RehearsalMark #'verticalll-skylinesss = #'() \ove

Re: Marks right-aligned in unstable

2013-07-07 Thread Thomas Morley
2013/7/7 Timothy Lanfear : > Marks are aligned to the right edge of objects in unstable release, whereas > they are centred in the stable release in agreement with the documentation. > Compare, for example, the arrow above the treble clef in the example near > the end of > > http://www.lilypond.org

Re: Broken x-refs in translated docs

2013-07-07 Thread Jean-Charles Malahieude
Le 06/07/2013 19:48, Jean-Charles Malahieude disait : Le 06/07/2013 15:45, Phil Holmes disait : "Jean-Charles Malahieude" wrote... I'll try to narrow this large window (slowly because of my box's power) and let you know. If you have less of a restriction with download limits, http://download

Re: tempo error

2013-07-07 Thread David Kastrup
Bastian writes: >> I'm not top posting. > > % Entering a tempo different from 4 = 120 > % generates an empty c++ error promt. > > \version "2.17.21" > \language "deutsch" > > > melody = \relative c' { > \clef treble > \key c \major > \time 4/4 > \tempo 4 = 96 > c2 d > e4. d8 c2 > } > > \s

Re: musicxml2ly stops making chords after some timing errors

2013-07-07 Thread Phil Holmes
"Pavel Roskin" wrote in message news:20130706171855.91mxat93pycg440g-ceb...@webmail.spamcop.net... Quoting pls : I don't care how the faulty markup looks. But MuseScore got the second measure right. It could recover and musicxml2ly could not. that's because of the faulty MusicXML markup yo

Re: tempo error

2013-07-07 Thread Phil Holmes
"Bastian" wrote in message news:loom.20130707t095919-...@post.gmane.org... I'm not top posting. % Entering a tempo different from 4 = 120 % generates an empty c++ error promt. \version "2.17.21" \language "deutsch" melody = \relative c' { \clef treble \key c \major \time 4/4 \tempo 4 =

Marks right-aligned in unstable

2013-07-07 Thread Timothy Lanfear
Marks are aligned to the right edge of objects in unstable release, whereas they are centred in the stable release in agreement with the documentation. Compare, for example, the arrow above the treble clef in the example near the end of http://www.lilypond.org/doc/v2.16/Documentation/notation/writ

tempo error

2013-07-07 Thread Bastian
> I'm not top posting. % Entering a tempo different from 4 = 120 % generates an empty c++ error promt. \version "2.17.21" \language "deutsch" melody = \relative c' { \clef treble \key c \major \time 4/4 \tempo 4 = 96 c2 d e4. d8 c2 } \score { \new Staff \melody } __