Re: Advice on naming and structuring scholarLY commands

2018-06-18 Thread Urs Liska
Hi Elaine, I was off my PC over the weekend, so I'll only now reply to your post. Am 16.06.2018 um 03:21 schrieb Flaming Hakama by Elaine: -- Forwarded message - From: Urs Liska mailto:li...@openlilylib.org>> Date: Fri, 15 Jun 2018 09:28:05 +0200 Subject: Re: A

Re: \consists terminology (was: Advice on naming and structuring scholarLY commands)

2018-06-15 Thread Flaming Hakama by Elaine
On Fri, Jun 15, 2018, 1:42 AM David Kastrup wrote: > David Kastrup writes: > > > Flaming Hakama by Elaine writes: > > > >> I think that conveys more clearly what is happening. > > > > Not really: that remains something to look up in the documentation. > > > > Now I'll readily admit that \consis

\consists terminology (was: Advice on naming and structuring scholarLY commands)

2018-06-15 Thread David Kastrup
David Kastrup writes: > Flaming Hakama by Elaine writes: > >> I think that conveys more clearly what is happening. > > Not really: that remains something to look up in the documentation. > > Now I'll readily admit that \consists / \remove does not make for an > appealing antonym pair. I'd be le

\consists terminology (was: Advice on naming and structuring scholarLY commands)

2018-06-15 Thread Urs Liska
[Adding a distinction in the thread title] Am 15. Juni 2018 09:44:44 MESZ schrieb "N. Andrew Walsh" : >Pedantry Corner: the *active* verb that Elaine is seeking is actually >"comprise." As in, "the committee comprises representatives from >various >disciplines." The verb in the opposite direction

\cobsists terminology (was: Advice on naming and structuring scholarLY commands)

2018-06-15 Thread Urs Liska
Just adding a distinction in the thread title Am 15. Juni 2018 09:44:44 MESZ schrieb "N. Andrew Walsh" : >Pedantry Corner: the *active* verb that Elaine is seeking is actually >"comprise." As in, "the committee comprises representatives from >various >disciplines." The verb in the opposite direct

Re: Advice on naming and structuring scholarLY commands

2018-06-15 Thread N. Andrew Walsh
Pedantry Corner: the *active* verb that Elaine is seeking is actually "comprise." As in, "the committee comprises representatives from various disciplines." The verb in the opposite direction is "compose:" "representatives of various disciplines compose the committee." "Composed" can be used in pas

Re: Advice on naming and structuring scholarLY commands

2018-06-15 Thread Urs Liska
Am 15.06.2018 um 08:58 schrieb David Kastrup: Flaming Hakama by Elaine writes: This is probably tilting at windmills at this point, since we seem to have adopted this language, both in LilyPond and in the ee. But, from the perspective of our terminology reflecting English language usage, I

Re: Advice on naming and structuring scholarLY commands

2018-06-15 Thread David Kastrup
Flaming Hakama by Elaine writes: > This is probably tilting at windmills at this point, > since we seem to have adopted this language, > both in LilyPond and in the ee. > > But, from the perspective of our terminology reflecting English language > usage, > I feel compelled to point out that "cons

Re: Advice on naming and structuring scholarLY commands

2018-06-14 Thread Urs Liska
Am 14.06.2018 um 15:56 schrieb Kieren MacMillan: Hi Urs, \variant seems unsuitable not only for the potential mistakes. Many cases will not deal with variants but single events. For example you may want to simply state that some notes are illegible, which is an editorial assessment and not

Re: Advice on naming and structuring scholarLY commands

2018-06-14 Thread Kieren MacMillan
Hi Urs, > \variant seems unsuitable not only for the potential mistakes. Many cases > will not deal with variants but single events. For example you may want to > simply state that some notes are illegible, which is an editorial assessment > and not a variant. The same goes for \option. > > Th

Re: Advice on naming and structuring scholarLY commands

2018-06-14 Thread Urs Liska
Am 14. Juni 2018 15:16:58 MESZ schrieb Kieren MacMillan : >Hi Urs, > >1. I think \variants is good. The fact that \choice matches MEI is its >only true advantage over \variants (IMO). > And not even a strong one. If it's for the conversion and *only* the name it's trivial to handle. >2. I ag

Re: Advice on naming and structuring scholarLY commands

2018-06-14 Thread Kieren MacMillan
Hi Urs, 1. I think \variants is good. The fact that \choice matches MEI is its only true advantage over \variants (IMO). 2. I agree that \edit doesn’t immediately seem optimal. The same problems, I think, plague \option. I considered \variant [singular], which works well (IMO) except for the o

Re: Advice on naming and structuring scholarLY commands

2018-06-14 Thread Urs Liska
Well, it seems my post was too extensive (and at the same time not controversial enough) to trigger serious discussion (or any feedback at all) - so basically I've made most decisions myself and with some private feedback. What I would still like to discuss are two function names. What I'm doi

Advice on naming and structuring scholarLY commands

2018-06-11 Thread Urs Liska
Hi all, I've started some serious work on the scholarLY package (https://github.com/openlilylib/scholarly) and will presumably have a bunch of questions over the next few weeks, both on design/interface, and implementation. [For all users of scholarLY: I also expect that this *may* end up in