Re: Horizontal spacing depends on stem 'direction

2011/9/9 Keith OHara : > Trevor Daniels treda.co.uk> writes: > >> It seems the horizontal spacing is slightly dependent on the stem >> direction. > > This spacing was intentional, including the spacing adjustment > between stems and bar lines : >

Re: Horizontal spacing depends on stem 'direction

Trevor Daniels treda.co.uk> writes: > It seems the horizontal spacing is slightly dependent on the stem > direction. This spacing was intentional, including the spacing adjustment between stems and bar lines :

Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string

Comment #11 on issue 1741 by bernardo...@gmail.com: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 Now it works! Attachments: tabtest.png 8.8 KB ___ bug-lilypo

Re: Horizontal spacing depends on stem 'direction

On Thu, Sep 08, 2011 at 11:57:54PM +0100, Trevor Daniels wrote: > I'd class this as an engraving nitpick, but we don't have that > classification anymore. Type-Ugly. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.

Horizontal spacing depends on stem 'direction

I'd class this as an engraving nitpick, but we don't have that classification anymore. It seems the horizontal spacing is slightly dependent on the stem direction. This can cause a score to mysteriously spread over an extra system when a single note with stem down is changed to one with stem

Re: Issue 1871 in lilypond: Several fixes for annotate-spacing

Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1871 by pkx1...@gmail.com: Several fixes for annotate-spacing http://code.google.com/p/lilypond/issues/detail?id=1871 Passes Make and reg tests ___ bug-lilypond mailing list bug-

Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string

Updates: Labels: Patch-new Comment #10 on issue 1741 by d...@gnu.org: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 The tabulature code uses ly:pitch-semitones, and ly:pitch-semitones maddeningly does not

Re: Issue 1798 in lilypond: Full measure rests do not occupy correct horizontal space.

Comment #1 on issue 1798 by pkx1...@gmail.com: Full measure rests do not occupy correct horizontal space. http://code.google.com/p/lilypond/issues/detail?id=1798 Reinhold Kainhofer via gnu.org to Lilypond show details 10:10 PM (59 minutes ago) In the attached example, the full-bar rests are w

Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't

Status: Accepted Owner: reinhold...@gmail.com Labels: Type-Scripts Patch-new New issue 1876 by pkx1...@gmail.com: MusicXML: fix case when some elements have a staff number, while others don't http://code.google.com/p/lilypond/issues/detail?id=1876 Hey all, here is a tiny example (see file at

Presence of a bar number changes whole-measure rest width significantly

If there is bar number printed after a measure, a full measure rest will be much longer than if there is no bar number printed. Simple example attached. A bar number should not have an influence on horizontal spacing! Cheers, Reinhold -- -

Re: Whole measure rest is too narrow (compared to whole measure note)

Hi Reinhold, 2011/9/8 Reinhold Kainhofer : > In the attached example, the full-bar rests are way too narrow, compared to > measures with multiple note, and even to measures with one full-measure note. > > This is not just ugly, musicians have real problems playing from these notes, > as I experien

Whole measure rest is too narrow (compared to whole measure note)

In the attached example, the full-bar rests are way too narrow, compared to measures with multiple note, and even to measures with one full-measure note. This is not just ugly, musicians have real problems playing from these notes, as I experienced with some friends (professional string musician

Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string

Updates: Summary: Tablature Bug when pitch is higher then beh in a quarter-tone string Comment #9 on issue 1741 by lilyli...@googlemail.com: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 (No comment was entered

Re: musicxml2ly does not recognize clef elements containing number attributes

Am Donnerstag, 8. September 2011, 18:29:21 schrieb Patrick Schmidt: > here is a tiny example (see file attached) to demonstrate the issue: the > musicxml2ly-conversion results in a common treble clef instead of a bass > clef. Without the number attribute everything works as expected. MusicXML > all

musicxml2ly does not recognize clef elements containing number attributes

Hey all, here is a tiny example (see file attached) to demonstrate the issue: the musicxml2ly-conversion results in a common treble clef instead of a bass clef. Without the number attribute everything works as expected. MusicXML allows number attributes in clef elements, so it's valid XML-code.

Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests

Updates: Owner: reinhold...@gmail.com Comment #9 on issue 1248 by reinhold...@gmail.com: GUB produces a random "unbound open-file" in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 (No comment was entered for this change.) __

Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings

Updates: Status: Fixed Labels: fixed_2_15_10 Comment #7 on issue 1805 by reinhold...@gmail.com: Ambitus engraver produces false warnings http://code.google.com/p/lilypond/issues/detail?id=1805 Pushed as 5d6df4944b265eded25882104e3f7899d1bc21c5 ___

Re: tests for flower appear to miss instantiations of classes

"Dmytro O. Redchuk" writes: > On Thu 08 Sep 2011, 14:13 David Kastrup wrote: >> When configured with >> >> ./configure CXXFLAGS=-fkeep-inline-functions >> >> (which does not optimize unused functions away) >> >> make test fails in the flower subdirectory in the linking stage with >> quite insc

Re: tests for flower appear to miss instantiations of classes

On Thu 08 Sep 2011, 14:13 David Kastrup wrote: > When configured with > > ./configure CXXFLAGS=-fkeep-inline-functions > > (which does not optimize unused functions away) > > make test fails in the flower subdirectory in the linking stage with > quite inscrutable error messages. > > I don't hav

Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes

Status: Accepted Owner: Labels: Type-Build New issue 1875 by brownian.box: tests for flower appear to miss instantiations of classes http://code.google.com/p/lilypond/issues/detail?id=1875 Reported by David Kastrup, http://lists.gnu.org/archive/html/bug-lilypond/2011-09/msg00215.html: %

Re: tests for flower appear to miss instantiations of classes

David Kastrup writes: > When configured with > > ./configure CXXFLAGS=-fkeep-inline-functions > > (which does not optimize unused functions away) > > make test fails in the flower subdirectory in the linking stage with > quite inscrutable error messages. > > I don't have the error message handy r

Re: tests for flower appear to miss instantiations of classes

Am Donnerstag, 8. September 2011, 14:13:12 schrieb David Kastrup: > When configured with > > ./configure CXXFLAGS=-fkeep-inline-functions > > (which does not optimize unused functions away) > > make test fails in the flower subdirectory in the linking stage with > quite inscrutable error message

tests for flower appear to miss instantiations of classes

When configured with ./configure CXXFLAGS=-fkeep-inline-functions (which does not optimize unused functions away) make test fails in the flower subdirectory in the linking stage with quite inscrutable error messages. I don't have the error message handy right now, but since this has been buggi

Issue 1874 in lilypond: some stems are no longer transparent in the docs

Status: Accepted Owner: Labels: Type-Documentation New issue 1874 by percival.music.ca: some stems are no longer transparent in the docs http://code.google.com/p/lilypond/issues/detail?id=1874 Mike: I'll need to make sure that all of the flags that are supposed to be transparent in the

Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests.

Updates: Labels: -Patch-review Patch-needs_work Comment #6 on issue 1833 by percival.music.ca: Deprecate \fermataMarkup for full-bar rests. http://code.google.com/p/lilypond/issues/detail?id=1833 if the patch meister is confused, then the patch is not ready for review. This doesn't

Re: Issue 1838 in lilypond: Make accidental styles available as context mods

Updates: Labels: -Patch-review Patch-needs_work Comment #4 on issue 1838 by percival.music.ca: Make accidental styles available as context mods http://code.google.com/p/lilypond/issues/detail?id=1838 any problem with a patch puts it back at needs_work. __

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

Updates: Labels: -Patch-review Patch-needs_work Comment #7 on issue 1855 by percival.music.ca: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Mike has more work to do on this one. ___ bug-lil

Issue 1873 in lilypond: Added glyphs for Kievan Notation

Status: Started Owner: Labels: Type-Enhancement Patch-new New issue 1873 by pkx1...@gmail.com: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 Added Kievan glyphs and a basic test file add basic infrastructure for kievan font First step in supporti

Re: Issue 1871 in lilypond: Several fixes for annotate-spacing

Updates: Labels: -Patch-needs_work Patch-new Comment #4 on issue 1871 by pkx1...@gmail.com: Several fixes for annotate-spacing http://code.google.com/p/lilypond/issues/detail?id=1871 (No comment was entered for this change.) ___ bug-lilypo