lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Doc: NR: Using \partial with \repeat.


From: Graham Percival
Subject: Re: [PATCH] Doc: NR: Using \partial with \repeat.
Date: Sun, 9 May 2010 15:08:02 +0100

On Sun, May 9, 2010 at 8:20 AM, Mark Polesky <address@hidden> wrote:
> I suppose it's a little too LMy for the NR?  Any suggestions
> for improving it?  Or is it good enough to push?

After Neil's comment to the issue, I'm not certain if you still want
to propose this solution.  But if you do,

+\override Score.BarNumber #'break-visibility = #'#(#f #t #t)

This means it's snippet-territory, not main text.  I could be
convinced to let it go if you added a
  % show all bar numbers
above it (as you did later), for pedagogical reasons (even though it's
contrary to the strict interpretation of the doc policy, our doc
policy has a "notwithstanding" clause[1]).

[1] err, sorry, Canadian political joke that won't translate.  Our
Charter of Rights and Freedom has a clause that basically states that
the government can temporarily (5 years) ignore our basic rights
(freedom of expression, religion, thought, belief, peaceful assembly,
association), as well as legal guarantees (fair trial, representation,
etc) if it really wants to.

http://en.wikipedia.org/wiki/Section_Thirty-three_of_the_Canadian_Charter_of_Rights_and_Freedoms

However, I'm really not fond of the incrBarNum stuff.  In the first
place, the names should be written in full.  In the second place, this
is really getting into snippet territory.


And the whole thing reads like Learning rather than Notation, which
you already noted.

I see two options:
1) wait for more clarity about the various workarounds for repeat issues.
2) dump the whole thing inside @knownissues without any more changes.
(the doc policy doesn't apply to @knownissues)
3)  rewrite the material somehow.  I'm not encouraging this option
given the lack of clarity about #1, but I present it for completeness.


Cheers,
- Graham




reply via email to

[Prev in Thread] Current Thread [Next in Thread]