[MEI-L] Problems encoding CMN
DanielAlles at stud.uni-frankfurt.de
Thu Jan 26 23:45:03 CET 2017
thank you very much for your reply, that really clarified a lot for me!
So let me rephrase my questions: Is there a general consens on how to
encode those accidentals or has every project its own rules? What
about the grouping of former ligatures in CMN? Does the <ligature>
element work in CMN?
Zitat von Andrew Hankinson <andrew.hankinson at mail.mcgill.ca>:
> Hi Daniel,
> You've (perhaps unknowingly) stumbled on one of the core tenets of
> MEI -- the separation of the semantic and the symbol.
> In MEI, you wouldn't encode the brackets; you would rather encode
> the function of the brackets, and leave it to a renderer to deal
> with adding the brackets around it.
> There are many 'semantic' places where you may see a bracket
> ('semantic' here is in reference to the function of the encoding in
> describing intent, rather than describing appearance). You could,
> for example, use elements such as 'supplied,' 'sic/corr', or
> 'orig/reg' to describe why the accidental should be drawn in
> brackets in an MEI-aware renderer.
> The same applies to your ligature question. You wouldn't place a
> line above a staff in MEI to indicate a ligature; you would instead
> find a way to encode the grouping of these notes into a ligature. It
> will then be up to the renderer to display that with a line above.
>> On Jan 26, 2017, at 10:40 PM, Daniel Alles
>> <DanielAlles at stud.uni-frankfurt.de> wrote:
>> New day, new questions - I hope this will get better soon...
>> Dear all,
>> is there a possibility to encode an accidental in brackets (if
>> possible above the staff)? I use them in my transcription of
>> mensural notation to indicate where I think might be missing one
>> but should be there. The Guidelines only mention "regular"
>> accidentals (without brackets).
>> How can I use brackets (in CMN) above the staff to indicate a
>> ligature in the MN-source? And what about coloration in the source?
>> For that I normaly use half brackets (see attached PDF). How can I
>> encode something similar?
>> I hope, someone can help me with that.
>> Best regards,
>> mei-l mailing list
>> mei-l at lists.uni-paderborn.de
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
More information about the mei-l