Re: NR A.10 Markup commands list review

[Simon Albrecht]

Am 01.09.2014 um 19:34 schrieb James:
> On 31/08/14 13:04, Simon Albrecht wrote:
> > Hello,
> >
> > upon reading the list of markup commands in the NR, I noticed several 
> > issues, which I’d like to report. I apologize for not making a patch 
> > myself; firstly, I have been uncertain at some points, secondly 
> > others are more apt at English phrasing, and also I’m not yet 
> > familiar with the process.
>
> Well this appendix is auto-generated not directly like the bulk of the 
> NR just a bunch of TexInfo files. The information is extracted 
> directly from the core *.scm or *.ly files (or similar),
I think it is only scm/define-markup-commands.scm concerned here, which 
is pretty easy to access and change locally.
> so it is not just a case of editing the page of the NR as it looks 
> directly. You would have to look at each command in its context in 
> whatever associated file it resides in and make the edits there.
>
> While not especially complicated if you know where to edit, it can be 
> time consuming.
So indeed it would be better if I take on this myself, wouldn’t it?
> […]
> This is all rather a lot to process and I don't think you will get 
> much reaction from this email (I may be wrong) from the group. As a 
> group we have been known to spend a lot of time on the (re)naming of 
> just a single command; and changing names of existing commands is not 
> something we take lightly. Look up the discussion on the new recent 
> command for \magnifyMusic.
>
> It seems you have done a lot of reading, and I fear this email may not 
> get any (useful) reply as it is just too much in one go to take in or 
> even begin to address.
>
> Frankly I think each of these last set of points needs its own 'email' 
> (I hesitate to say tracker simply because some of them are just your 
> opinion than any technical 'problem' or 'issue'. That's not to say 
> that your opinion isn't important but if you really want to change the 
> name of \customTabClef to \custom-tab-clef (for example) then start a 
> new email thread with just that discussion, and if the group agree 
> then we can start on getting patches made.

I think I’ll be able to figure out the logic of 
define-markup-commands.scm and apply some of the suggested changes. 
Particularly the part about units of measurement will likely be 
uncontroversial also. Should I just get a start with git, follow the CG 
and commit a patch for review?
And for the other, more controversial items, I will open new threads on 
the list, then.
Thanks for the hints.

Yours, Simon