Issue 4078: Doc: Use variables rather than instrument definitions

Issue 4078: Doc: Use variables rather than instrument definitions

  Using variables for switching character names in vocal music
  rather than instrument definitions is easier to understand,
  easier to set up and quicker to type.  It also frees up the
  use of instrument definitions so they may be tailored for
  better use in instrumental compositions.

  Remove the mention of \transposition.  This is never required
  in vocal music.

  Adjust references to match the changes.

[Keith, 2014-08-31 06:58:47]

LGTM

I was thinking of completing the deprecation of instrumentSwitch, 
https://codereview.appspot.com/133390043/
unless you want to incorporate some or all of that here.

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
File Documentation/notation/vocal.itely (right):

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2580: kaspar = {
David, I think, suggested the name 'setKaspar' to reinforce the concept that it
contains Kaspar's staff-settings, as opposed to Kaspar's music.

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2646: \set instrumentCueName = "Flute"
This is the *other* use of instrumentSwitch,
which I'll probably put back to a <>^\markup

[dak, 2014-08-31 07:14:11]

On 2014/08/31 06:58:47, Keith wrote:
>
https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
> Documentation/notation/vocal.itely:2646: \set instrumentCueName = "Flute"
> This is the *other* use of instrumentSwitch,
> which I'll probably put back to a <>^\markup

I think one of the points of the instrument switches was that you could do as
many as you liked in a row (namely, attaching the instrument switch to the start
of any music variable to be used for a particular instrument) without triggering
extraneous switch messages.

<>^\markup would seem to defeat that part of the original design.  While we
don't need the instrumentSwitch command as such, the respective engravers
weeding out duplication still serve a purpose.

[Trevor Daniels, 2014-08-31 07:58:50]

Thanks Keith.  Responses below.

Trevor

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
File Documentation/notation/vocal.itely (right):

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2580: kaspar = {
On 2014/08/31 06:58:47, Keith wrote:
> David, I think, suggested the name 'setKaspar' to reinforce the concept that
it
> contains Kaspar's staff-settings, as opposed to Kaspar's music.

Personally I prefer just "kaspar" as snappier.
It would typically be used multiple times, whereas
kasparMusic and kasparLyrics would be used only once.
Not something to die in the ditch for - I'll change it.

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2646: \set instrumentCueName = "Flute"
On 2014/08/31 06:58:47, Keith wrote:
> This is the *other* use of instrumentSwitch,
> which I'll probably put back to a <>^\markup

This is using InstrumentSwitch in it's "proper"
orchestral sense, where it's interacting with 
\cueDuring.  Changing that needs more thought, and
needs to be done at the same time as the change to
the corresponding section in staff.itely.

[Keith, 2014-08-31 08:25:53]

still LGTM

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
File Documentation/notation/vocal.itely (right):

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2580: kaspar = {
On 2014/08/31 07:58:49, Trevor Daniels wrote:
> Personally I prefer just "kaspar" as snappier.

Keep it snappy, then.

https://codereview.appspot.com/138950043/diff/1/Documentation/notation/vocal....
Documentation/notation/vocal.itely:2646: \set instrumentCueName = "Flute"
On 2014/08/31 07:58:49, Trevor Daniels wrote:
> This is using InstrumentSwitch in it's "proper"
> orchestral sense, where it's interacting with 
> \cueDuring.  Changing that needs more thought, and
> needs to be done at the same time as the change to
> the corresponding section in staff.itely. 

Whichever use of instrumentSwitch was its original intent, or whichever use is
proper, neither is useful.

I have the rest of the removal ready to follow after this patch.

[Trevor Daniels, 2014-09-05 11:55:29]

Pushed to staging as
c0c3cd6ac43112ce392f9559555f723b359580a6
Closing ...