PATCHES: Countdown for July 18 - 06:00 GMT

[James]

Hello

*Countdown -- July 18 -- 06:00 GMT* *
*   *
*   *
*   *
*





3382 
 
	Build 	Julien Rioux 	Push 	build dependencies: check that version of 
texinfo is <=4.13
3442 
 
	Enhancement 	Julien Rioux 	Push 	Patch: Build: Small dependency fix.
3447 
 
	Build 	Julien Rioux 	Push 	make website: no VERSION dependency
3452 
 
	Documentation 	Mark Polesky 	Push 	inconsistency in the description of 
repeats and alternate endings
3451 
 
	Documentation 	Mark Polesky 	Push 	[DOC]anacrucis instead of anacrusis
3450 
 
	Documentation 	thomasmorley65 	Push 	\addlyrics doesn't work with TabStaff
3449 
 
	Enhancement 	David Kastrup 	Push 	Patch: Shift accordion register 
symbols down by half a line width
3151 
 
	Documentation 	thomasmorley65 	Push 	NR 3.4.1: \layout block wrongly 
placed in a \book block causes error






3444 
 
	Enhancement 	David Kastrup 	Countdown 	No warning for misspelled 
properties




James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: upgrade to c++11

[Alexander Kobel]

On 07/14/2013 10:41 PM, Frédéric Bron wrote:

I had taken a look previously at CGALhttp://www.cgal.org/>  since
the kind of stuff we are doing with skylines would benefit from
ready-made code like
http://www.cgal.org/Manual/latest/doc_html/cgal_manual/Envelope_2/Chapter_main.html>
and frankly, doing things like computational geometry tasks is
a) a resource drain
b) a source for problems


It seems that cgal makes more than boost::geometry that cannot compute
convex hull of curves.


Disclaimer: (By choice of PhD topic and working group,) I'm a CGAL 
developer, though rarely active and if so, then not in one of the 
publicly visible areas.


CGAL is a very neat library if you need robust and exact geometry 
processing. It's complex to set up though (the current workflow requires 
CMake and, for a "typical" setup, quite a number of dependencies), so I 
don't know how nicely it plays with GUB. OTOH, the hard requirements 
boil down to Boost and GMP+MPFR(+MPFI). There's currently progress on 
even removing GMP as a dependency, but for us GMP licensing is a 
non-issue, and using it makes your CGAL life a lot easier.
For use cases like skylines of segments which mostly deal with linear 
geometry and are very unlikely to hit degenerate cases, CGAL is a very 
heavy hammer. But using it saves you from even thinking about what 
situations can occur, and this code is highly optimized.


If you know a good piece of code to test a migration to CGAL, give me a 
ping, and I'll try to help.



Best,
Alexander

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Strange cautionary

[Phil Holmes]

What's the cautionary on the 3rd beat of the second bar doing there?

\new PianoStaff <<
  \new Staff = "RH"
  { 
 \accidentalStyle "piano-cautionary"

 \clef "treble"
 R1
 ees''8 d''8 c''8 b'8 ees''8 d''8 c''8 b'8 \bar "|."
 }
 \new Staff = "LH"
 {
 \accidentalStyle "piano-cautionary"
 \clef "bass"
 ees1 ~   |  % 1
 ees1
 }





--
Phil Holmes

<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

workaround for \partcombine limitation, how to add to docs?

[Mark Polesky]

In NR 1.5.2 Multiple voices - Automatic part combining, this
appears in the Known issues:

"All \partcombine… functions can only accept two voices and
are not designed to work with lyrics; such that when one of
the voices is explicitly named in order to attach lyrics to
it, the partcombiner will stop working."

http://lilypond.org/doc/v2.17/Documentation/notation/multiple-voices#Known-issues-and-warnings-82

I have found a workaround, detailed below.  What is the best
way to include this in the docs?

Thanks.
- Mark
__


\version "2.17.21"

sopranoNotes = \relative g' {
  g4 fis8( g) a4 g |
  c4 c b2
}
altoNotes = \relative d' {
  d4 d d d |
  c4 d d2
}
words = \lyricmode {
  As with glad -- ness men of old
}

squashRhythmicStaff = \with {
  \remove Time_signature_engraver
  \remove Bar_engraver
  \remove Staff_symbol_engraver
  \override VerticalAxisGroup.default-staff-staff-spacing =
  #'((basic-distance . 0) (padding . -inf.0))
}

squashVoice = \with {
  \remove Breathing_sign_engraver
  \remove Glissando_engraver
  \remove Multi_measure_rest_engraver
  \remove Pitched_trill_engraver
  \remove Repeat_tie_engraver
  \remove Trill_spanner_engraver

  \omit DynamicLineSpanner
  \omit DynamicText
  \omit DynamicTextSpanner
  \omit Hairpin
  \omit ParenthesesItem
  \omit PhrasingSlur
  \omit Script
  \omit Slur
  \omit TextScript
  \omit TextSpanner
  \omit Tie

  \override Stem.length = #0
  \override Beam.positions = #'(1 . 1)

  \hideNotes
}

<<
  \new RhythmicStaff \with { \squashRhythmicStaff } {
    \new Voice = "soprano" \with { \squashVoice } \sopranoNotes
  }
  \new Staff \with { printPartCombineTexts = ##f } {
    \key g \major
    \partcombine \sopranoNotes \altoNotes
  }
  \new Lyrics \lyricsto "soprano" \words
>>


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: workaround for \partcombine limitation, how to add to docs?

[Trevor Daniels]

Mark Polesky wrote Monday, July 15, 2013 9:50 PM


> In NR 1.5.2 Multiple voices - Automatic part combining, this
> appears in the Known issues:
> 
> "All \partcombine… functions can only accept two voices and
> are not designed to work with lyrics; such that when one of
> the voices is explicitly named in order to attach lyrics to
> it, the partcombiner will stop working."
> 
> http://lilypond.org/doc/v2.17/Documentation/notation/multiple-voices#Known-issues-and-warnings-82
> 
> I have found a workaround, detailed below. What is the best
> way to include this in the docs?

Hi Mark

Add it as a snippet, suitably tagged.  This is neat, but I think it 
is too much of a hack to reference it explicitly in the documentation
text.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Strange cautionary

[Eluze]

Phil Holmes wrote
> What's the cautionary on the 3rd beat of the second bar doing there?

isn't that what piano-cautionary asks for?

from NR  Chapter 1: Musical notation:


piano-cautionary
This is the same as piano but with the extra accidentals typeset as
cautionaries.

piano
This rule reflects twentieth-century practice for piano notation. Its
behavior is very
similar to modern style, but here accidentals also get canceled across the
staves in
the same GrandStaff or PianoStaff, hence all the cancellations of the final
notes.
This accidental style applies to the current GrandStaff or PianoStaff by
default.

modern
This rule corresponds to the common practice in the twentieth century. It
omits
some extra natural signs, which were traditionally prefixed to a sharp
following a
double sharp, or a flat following a double flat. The modern rule prints the
same
accidentals as default, with two additions that serve to avoid ambiguity:
after
temporary accidentals, cancellation marks are printed also in the following
measure
(for notes in the same octave) and, in the same measure, for notes in other
octaves.
Hence the naturals before the b and the c in the second measure of the upper
staff


after reading all this I feel the current behavior is correct

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Strange-cautionary-tp148054p148058.html
Sent from the Dev mailing list archive at Nabble.com.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: workaround for \partcombine limitation, how to add to docs?

[Dan Eble]

Thanks for this hack.  I look forward to trying it.

Any feelings on the likelihood that it is going to stop working in future 
versions?
-- 
Dan

On 2013-07-15, at 17:05 , "Trevor Daniels"  wrote:

> 
> Mark Polesky wrote Monday, July 15, 2013 9:50 PM
> 
> 
>> In NR 1.5.2 Multiple voices - Automatic part combining, this
>> appears in the Known issues:
>> 
>> "All \partcombine… functions can only accept two voices and
>> are not designed to work with lyrics; such that when one of
>> the voices is explicitly named in order to attach lyrics to
>> it, the partcombiner will stop working."
>> 
>> http://lilypond.org/doc/v2.17/Documentation/notation/multiple-voices#Known-issues-and-warnings-82
>> 
>> I have found a workaround, detailed below. What is the best
>> way to include this in the docs?
> 
> Hi Mark
> 
> Add it as a snippet, suitably tagged.  This is neat, but I think it 
> is too much of a hack to reference it explicitly in the documentation
> text.
> 
> Trevor
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Issue 3457: Add snippet `Using \partcombine with lyrics'. (issue 11328043)

[markpolesky]

Reviewers: ,

Message:
Hi folks,

here's a patch that adds a new snippet to NR "Automatic part combining":
my workaround to get \partcombine to work with lyrics.  Is the texidoc
too long?  Should I leave out how it works?

http://code.google.com/p/lilypond/issues/detail?id=3457

Thanks
- Mark

Description:
Add snippet `Using \partcombine with lyrics'.

Also run makelsr.py, and add reference in NR "Automatic part combining".

Please review this at https://codereview.appspot.com/11328043/

Affected files:
  M Documentation/notation/simultaneous.itely
  A Documentation/snippets/new/using-partcombine-with-lyrics.ly
  M Documentation/snippets/simultaneous-notes.snippet-list
  A Documentation/snippets/using-partcombine-with-lyrics.ly
  M Documentation/snippets/vocal-music.snippet-list
  M Documentation/snippets/workaround.snippet-list



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel