John Chambers a skrivas:
> So I note that the V:  lines are, technically,  all  in  the  "music"
> portion,  not  in  the  "header"  portion.   This  doesn't seem to be
> mentioned in the proposed standard.

Field name            header tune elsewhere Used by Examples and notes
==========            ====== ==== ========= ======= ==================
$ V:voice                    yes                    V:2, V:Soprano

There is no need to have a V: field in the header: it is just a voice
switch and not a voice definition.

        [snip]
> What abc2ps does is let you declare your voices in the header with  a
> rather general syntax:
> 
>    V: <label> <par1>=<value1> <par2>=<value2>  ...
> 
> Within the music, you only use V:<label>, or perhaps [V:<label>],  to
> tell the software that the music that follows is for that voice.  The
> docs that come with abc2ps say that the <label> may  be  any  "word",
> but  all the examples seem to use numbers.

False: look at 'voices.abc' (abc2ps-1.3.0): you will see an implicit
voice and then the 'V:acc_1' and 'V:acc_2' switches.

> Symbolic names for a part
> are handled in the header with parameters:
> 
>    V:3 name="Violin II" sname="Vl.II"
> 
> Here, the name param is printed on the first  staff,  and  the  sname
> (short  name)  is  printed  on subsequent staves, as is commonly done
> with band and orchestra scores.
> 
> There are a lot of such V:  parameters described in the abc2ps  docs,
        [snip]

These parameters deal with staff printing. They are at a wrong place;
for example, a same voice may be the main song and also some accompa-
niement. Only a staff field may say which name is to be printed on the
score.

> Any official standard would probably want to include a comment to the
> effect  that  such parameters are all optional, and may be ignored by
> programs that don't need them.  I can also  see  the  possibility  of
> software  that  parses  the  name= parameter and uses it to establish
> things like default clef and transposition, but I'd  suppose  that  a
> standard would want to carefully avoid mentioning any such thing.

May be a compatibility clause could be inserted, but, this is not useful
as only the <label> needs to be parsed.

-- 
Ken ar c'henta� |             ** Breizh ha Linux atav! **
                |               http://moinejf.free.fr/
P�p� Jef        |       please, on reply, mailto:[EMAIL PROTECTED]
                |    or mailto:[EMAIL PROTECTED]


To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html

Reply via email to