anders.vinjar | 17 Dec 15:20 2014
Picon

tuplet number shifted away from beam w. articulations

When placing tuplet numbers wo. brackets at beam-end, the placement is
shifted if there's an accent placed somewhere else along the beam:

Attachment (tuplet-numbers-at-beam-end.ly): application/octet-stream, 692 bytes

Using \override Script.outside-staff-priority = #0 (or any number it
seems) moves the number down to the beam again.

Q: should the tuplet-number wo. bracket go down to the beam when there's
nothing there to collide with?  If so, any clue about how to get that?

Cheers,

-anders
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hans Aberg | 15 Dec 14:27 2014
Picon

Intervals and pitches

I have implemented the formerly described model for intervals and pitches in C++11.
Urs Liska | 15 Dec 12:24 2014

Font switching docs - add a font to LilyPond?

Hi all,

Abraham has sent me documentation for his recent font switch improvement 
to incorporate into LilyPond's manuals.
However, there is one issue I'd like to sort out before I start editing 
the .itely files.

Of course the documentation gives an example of the use of the new font 
selection function. But this will require the used font(s) to be 
installed on the build system because otherwise the build will fail.
I see the following ways to deal with that situation and would like to 
get your opinion about it.

1)
work around that by *not* providing a working (i.e. autocompiling) example.
That could mean providing a listing and a static image.

2)
work around that by only linking to fonts.openlilylib.org and a working 
example there.

3)
Make at least one additional font a requirement for the build system.

4)
Include at least one additional font into LilyPond's distribution and 
use that for the example.

I don't like 1) and 2) at all!

(Continue reading)

James | 14 Dec 20:43 2014
Picon

PATCHES: Countdown for December 17th 2014

Hello,

Here is the current patch countdown list. The next countdown will be on 
December 17th.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

Trevor Daniels: Incorrect wording to example of overriding the 
'positions property in LM, etc
http://code.google.com/p/lilypond/issues/detail?id=4221

James Lowe: Patch: Doc: Usage - added more examples for lilypond
http://code.google.com/p/lilypond/issues/detail?id=4220

James Lowe: Web: Google Summer of Code (GSoC) Webpage needs 
updating/removing/hiding
http://code.google.com/p/lilypond/issues/detail?id=4215

James Lowe: Usage: convert-ly command line tips
http://code.google.com/p/lilypond/issues/detail?id=4187

James Lowe: MusicXML test suite: test description in 
41f-StaffGroups-Overlapping.xml is incorrect
http://code.google.com/p/lilypond/issues/detail?id=4177

(Continue reading)

lemzwerg | 14 Dec 07:54 2014

docstring (issue 187140044 by k-ohara5a5a <at> oco.net)

Some nits.  Thanks for adding this!

https://codereview.appspot.com/187140044/diff/20001/lily/separation-item.cc
File lily/separation-item.cc (right):

https://codereview.appspot.com/187140044/diff/20001/lily/separation-item.cc#newcode190
lily/separation-item.cc:190: "Draws the  <at> code{horizontal-sklines} of
each  <at> code{PaperColumn},"
s/sklines/skylines/

https://codereview.appspot.com/187140044/diff/20001/lily/separation-item.cc#newcode191
lily/separation-item.cc:191: " showing the shapes used to the minimum
distances between"
`used to'?  This sentence looks weird...

https://codereview.appspot.com/187140044/diff/20001/lily/separation-item.cc#newcode193
lily/separation-item.cc:193: " before staves have been spaced on the
page.")
s/have been spaced/ have been spaced (vertically)/

https://codereview.appspot.com/187140044/
david.nalesnik | 11 Dec 14:11 2014
Picon

Doc: Issue 4221: Corrections to example of 'positions property (issue 186920043 by tdanielsmusic <at> googlemail.com)

LGTM

https://codereview.appspot.com/186920043/
James | 11 Dec 08:53 2014
Picon

PATCHES: Countdown for December 14th 2014

Hello,

Here is the current patch countdown list. The next countdown will be on 
December 11th.

You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch

____________________

PUSH:

James Lowe: Web: Add Elaine Gould's Behind Bars to the literature list
http://code.google.com/p/lilypond/issues/detail?id=4206

James Lowe: Website: add lilybin.com to Easier editing
http://code.google.com/p/lilypond/issues/detail?id=4199

Keith OHara: Give compressed multi-measure rests more space
http://code.google.com/p/lilypond/issues/detail?id=4197

____________________

COUNTDOWN:

Trevor Daniels: Incorrect wording to example of overriding the 
'positions property in LM, etc
http://code.google.com/p/lilypond/issues/detail?id=4221

James Lowe: Patch: Doc: Usage - added more examples for lilypond
(Continue reading)

Dan Eble | 11 Dec 05:52 2014
Picon

Voice switching étude

Here’s a trick: routing music to different voices without using the Part_combine_iterator.  Instead,
it uses the same infrastructure as for staff switching.

\version "2.19.15"

\layout {
  \context {
    \name "X"
    \type "Engraver_group"
  }
  \context {
    \Voice
    \accepts "X"
  }
}

one = \relative { b'4 b b b }
two = \relative { b'4 b f f }

% TODO: Derive oneChanges and twoChanges from the result of
% determine-split-list.
oneChanges = \relative { }
twoChanges = \relative { s2 \change Voice = "1" }

\score {
  <<
    \new X << \oneChanges \one >>
  \\
    \new X << \twoChanges \two >>
  >>
(Continue reading)

Villum Sejersen | 10 Dec 17:06 2014
Picon

Web: Essay - Add Elaine Gould's book Behind Bars (issue 187860043 by address <at> hidden)

Hello Trevor and whoever took the trouble to write thge entry (I simply 
can't find the name anywhere)

Yes. concise enough. Personally, although I don't like 'The 
definitive...'; 'An exhaustive...' is much more to my liking.

I am still hoping for Han-Wen and Jan sometime to comment the book 
somewhere... :) Elaine Gould's book and the Lilypond project were 
commenced around the same time! I do sincerely believe that many of 
Eleanor Gould's recommendations and her don'ts are already met by 
Lilypond, even in the default configurations! Not to mention by the many 
power users, whose skills ever astound me.

What about adding a reference to the german translation (2014)? It is 
not that often reference works are translated so early after the 
publication of the original, so I think it ought to be mentioned.

--

-- 
yours,
Villum Sejersen
Nørregade  1 A
DK-4500  Nykøbing Sjælland
mobil   +45   30 34  03 44

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
pkx166h | 9 Dec 08:52 2014
Picon

Re: Docs: state that LilyPond input is in terms of pitches (issue 185140043 by k-ohara5a5a <at> oco.net)

Fails make.

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely#newcode119
Documentation/learning/common-notation.itely:119:  <at> node Pitches
Problem with calling this node 'Pitches' is that it throws an error as
it has been previously defined in another  <at> node in this doc. You'll need
to change it.

https://codereview.appspot.com/185140043/
paulwmorris | 8 Dec 21:24 2014
Picon

Re: Web: Update GSoc entry (issue 180650043 by pkx166h <at> gmail.com)

One more thing.

https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):

https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode965
Documentation/web/community.itexi:965: enharmonic notes  <at> code{ <at> { cis'~
des'  <at> }} and ties  <at> q{broken} by clef or
I think ties on enharmonic notes are recently fixed thanks to dak (issue
461).

https://codereview.appspot.com/180650043/

Gmane