|
From: | Urs Liska |
Subject: | Re: Advice on naming and structuring scholarLY commands |
Date: | Mon, 18 Jun 2018 10:55:52 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
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:
Not *alternatives*, basically an individual segment of music.
Technically (as music-functions) they can be nested but not overlapping. Conceptually it should be possible to have overlapping findings, but I don't plan to try supporting this. I think users would have to work around with adjacent segments.
We already have these, in the existing scholarLY annotations \criticalRemark, \musicalIssue etc. These "point" to a specific element (through a \tweak or \once \override) and "attach" an annotation to this. In the sense of "I want to say something about this score element", not "this 'is' something".
Basically this is what I would like to achieve. I want to encode the information that
However, this would "pollute" the namespace with numerous names, many of whom being pretty generic (gap, add, del, corr etc.), which is why I am looking for a generic "wrapper" command that is specified by its first argument.
Maybe (probably) I'll drop the idea of tagging both the beginning and end of the segment, but I think this description is going into the right direction ...
There need not be alternatives. The command in question encodes *one* finding, which may include a single musical element or a (sequential) music _expression_. If the editor wants to encode alternatives (for example the original vs. the corrected text) there is (going to be) an additional command that wraps them and decides which one to use for the current engraving. There need not be editorial marks. The *basic* task of the command is to encode a certain segment of music "as" something, for example: { c' d' \corr { e' d' } | c'1 }which would encode the information that this half measure has been corrected from faulty text in the source. An editorial mark *can* be generated by this command, which would then attach an annotation to the first element of the music _expression_ (the e'). My understanding is that the command "marks up" or "tags" the music _expression_. It doesn't add a mark to the music, and it doesn't "describe" it, rather it "names" it. Another option would be to say it "labels" it. The problem seems to be that while all these four are valid they conflict with existing uses of the words. My personal favourite would be \editorialMarkup because in my understanding this is exactly the use of the term in "markup language". The above example would roughly map to HTML like this: Some words <span class="corr">have been corrected</span> from obvious errors.where "span" would be the entity we're searching a correspondence for. { c' d' \editorialMarkup corr { e' d' } | c'1 }-- which finally brings me to the idea of using "span" - since that is so semantically open: { c' d' \span corr { e' d' } | c'1 }This would open the thing up from the more narrow perspective of scholarly editing to the more general idea of semantic encoding of music. There could then be a provision for users to add their own "classes" in the future.
Indeed, and I do want to get this one right before going further. While the \consists case is clearly more important we have an important advantage *here*: we build upon an empty space and don't discuss changing syntax that has been around for decades. Best Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |