Re: Problems with \inversion

2012-06-21 Thread Colin Hall
On Thu, Jun 21, 2012 at 11:09:13PM +0100, Trevor Daniels wrote: > > David Kastrup wrote Tuesday, June 19, 2012 10:57 AM > > > > "Both in relative notation" is asking for trouble. I'd strongly suggest > > only inverting absolute music, and the result of \relative ... _is_ > > absolute music. >

Re: Problems with \inversion

2012-06-21 Thread Trevor Daniels
David Kastrup wrote Tuesday, June 19, 2012 10:57 AM > "Trevor Daniels" writes: > >> Colin Hall wrote Tuesday, June 19, 2012 1:12 AM >> >>> It looks like the behaviour has been explained by David Kastrup here: >>> >>> http://lists.gnu.org/archive/html/lilypond-user/2012-06/msg00380.html >>>

Re: Apparent error in NR section 1.8.1

2012-06-21 Thread Colin Hall
On Wed, Jun 20, 2012 at 05:24:32PM +0100, Phil Holmes wrote: > "Philip Thomas" wrote in message > news:45218.0305067033$1340207...@news.gmane.org... > >Hi there, Documentation Wardens, > > > >There's seems to be an error in NR > section 1.8.1 > Text marks > Selected > >Snippets > Aligning marks wi

Re: bug in SVG output

2012-06-21 Thread Federico Bruni
Il 21/06/2012 22:07, m...@apollinemike.com ha scritto: Have you tried to visualize the SVG in several browsers? Could you confirm if the image is the same or different depending on the browser? It's the same in Chromium, Firefox and Inkscape. See svg attached. \version "2.15.41" { \tempo 4

Re: bug in SVG output

2012-06-21 Thread m...@apollinemike.com
On 21 juin 2012, at 21:16, Karol Majewski wrote: > I think I have found a bug. It's related to metronome mark in SVG output. > Normally, there is one space before equality sign. In SVG output there is > no space. Take a look at the example. Thank you for the report, Karol. Have you tried to visu

bug in SVG output

2012-06-21 Thread Karol Majewski
I think I have found a bug. It's related to metronome mark in SVG output. Normally, there is one space before equality sign. In SVG output there is no space. Take a look at the example. <><>___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.

Re: Bug: simple chord inversions take 2-octaves

2012-06-21 Thread Ralph Palmer
On Thu, Jun 21, 2012 at 11:32 AM, Nucleos wrote: > Hello, > > c major is : > > The first inversion would be . This is what I call c/e. > The second inversion would be . This is what I call c/g > > The code below triggers nevertheless Lilypond 2.14.2 to display > -- which is 2 octaves wide ! > >

Re: simple chord inversions take 2-octaves

2012-06-21 Thread Nucleos
Le 21/06/2012 18:24, Phil Holmes a écrit : > This doesn't help you, but for my money, both inversions are > incorrect. Correct inversions would look as attached. Wonder if it's > an artifact from relative note placement? You are right, "theoretically" any inversions could be used, but in theory,

Re: simple chord inversions take 2-octaves

2012-06-21 Thread Phil Holmes
"Nucleos" wrote in message news:4fe33eab.2020...@free.fr... Hello, c major is : The first inversion would be . This is what I call c/e. The second inversion would be . This is what I call c/g The code below triggers nevertheless Lilypond 2.14.2 to display -- which is 2 octaves wide ! Weird

Bug: simple chord inversions take 2-octaves

2012-06-21 Thread Nucleos
Hello, c major is : The first inversion would be . This is what I call c/e. The second inversion would be . This is what I call c/g The code below triggers nevertheless Lilypond 2.14.2 to display -- which is 2 octaves wide ! Weirdly, Lilypond seems to think my definition of inversions is righ