Re: Sorting out annotation interface questions (GSoC)

[Urs Liska]

Hi Simon,

thanks for the feedback. 


Am 27. Juni 2016 13:21:25 MESZ, schrieb Simon Albrecht <address@hidden>:
>On 27.06.2016 00:55, Urs Liska wrote:
>> \musicalIssue \with {
>>    author = "Urs Liska"
>>    context = "violin 1"
>>    message = "Slur obviously forgotten in original edition"
>>    apply = addition
>> } Slur
>>
>> My question is: is this "application" the same as the type of
>annotation
>> action from the previous issue? Or could it occur that a project
>wants
>> to document types of editorial decisions independently from applying
>> visual indications of that?
>
>A few unsystematic thoughts:
>Well, there are limits to visual indication of critical matters. At 
>least in some projects it will be impossible for the score to contain 
>(or even hint to) every bit of information present in the Critical
>Report.
>I really think we should allow for great diversity in the possible 
>approaches, i.e. editorial policies.

We certainly don't intend to impose editorial policies but to provide the tols 
to tailor project specific behaviour. 

By default annotations dob't have any impact on the layout (which is crucial) 
but just colorize objects while in draft mode.

Additionally we'll provide generic commands that can be used to visually 
indicate certain types of editorial action.

For example something like \editorialAddition can be used to indicate something 
that is missing in the source and has been added by the editor. By default this 
might make slurs dashed and parenthesize other types of elements. Of course the 
visual appearance will be configurable so only the semantic command is inserted 
in the music.

Now annotations *can* trigger the application of such editorial commands (which 
can also be used independently from annitations). 
My question is: are the *type* of decision and the triggering oc commands 
inherently independent so we should implement both a property forvthe 
annotation type *and* the applied command or could they be "merged"?

> In some cases it might be good to 
>have a simple switch (modernise lyrics or not);
>in other cases everything must be decided on a case-by-case basis, with
>
>no automation being possible;
>and the type of annotations one will have, as well as how to display 
>them in both the score and the critical apparatus, will be very 
>different depending on the project.

Of course, as commented on above.

>Perhaps that at one time our footnotes engine will be sophisticated 
>enough to be used for such purposes, and include the apparatus in the 
>actual musical text. It would be good to have hooks for such an
>approach.

Triggering footnotes from annotations is on the GSoC task list. As is the 
possibility to insert scores in annotations  (to be printed in a footnote for 
example, or in the LaTeX critical report).

Best
Urs

>
>I’m sorry I don’t have the time to take a deeper dive into this, but I 
>really appreciate your efforts!
>
>Best, Simon

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.