Joe Neeman wrote:
How about:
+sections without notes (either @code{r} or @code{R} rests or
[EMAIL PROTECTED] skips). Rests or skips must be present in all contexts within
the scope
+of the engraver. That is, if the engraver in is a Staff with multiple
+voices, then all the voices must have rests
On Thu, 2006-09-07 at 08:10 +0200, Erik Sandberg wrote:
> On Thursday 07 September 2006 02:25, Joe Neeman wrote:
> > On Wed, 2006-09-06 at 15:08 -0700, Graham Percival wrote:
> > > Joe Neeman wrote:
> > > By "the absence of notes", do you mean "{r | R | s} in all parts", or do
> > > you mean "{s} i
On Thursday 07 September 2006 02:25, Joe Neeman wrote:
> On Wed, 2006-09-06 at 15:08 -0700, Graham Percival wrote:
> > Joe Neeman wrote:
> > By "the absence of notes", do you mean "{r | R | s} in all parts", or do
> > you mean "{s} in all parts" ? That "does not scan for rests" is a bit
> > confus
On Wed, 2006-09-06 at 15:08 -0700, Graham Percival wrote:
> Joe Neeman wrote:
> > +If this is too tedious, you can add a @code{Page_turn_engraver} to a Staff
> > or
> > +Voice context. The @code{Page_turn_engraver} will scan the context for
> > +sections without notes (note that it does not scan f
Joe Neeman wrote:
I figured the new page breaking stuff might be more useful if people had
some idea of how to use it. Writing documentation is not something I've
had much practice with, so please point out any problems
Looks fairly good; I've made a few comments below, but once those are
fixe
cc (penalty): minPageTurnLength ->
minimumPageTurnLength
* scm/define-context-properties.scm (all-user-translation-properties):
add minimumPageTurnLength and minimumRepeatLengthForPageTurn
* Documentation/user/page.itely: update page breaking documentation
In
