<div dir="ltr">Hi,<div><br></div><div>In the next version of MEI there will be a <ligatureSpan> for this. See <a href="https://github.com/music-encoding/music-encoding/issues/274">https://github.com/music-encoding/music-encoding/issues/274</a></div><div><br></div><div>Best wishes,</div><div>Laurent</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 27, 2017 at 2:38 AM, Craig Sapp <span dir="ltr"><<a href="mailto:craigsapp@gmail.com" target="_blank">craigsapp@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Giuliano,<br><br></div>One possibility is to use the type attribute:<br><br></div><span style="color:rgb(153,0,255)"><line type="ligature"></span><br><br></div><div>Also the "label" attribute seems like a possibility:<br><br></div><div><span style="color:rgb(153,0,255)"><line label="ligature"></span><span class="HOEnZb"><font color="#888888"><br><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div>-=+Craig<br><br></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 26 January 2017 at 17:19, Di Bacco, Giuliano <span dir="ltr"><<a href="mailto:gdibacco@indiana.edu" target="_blank">gdibacco@indiana.edu</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div>
<div>Thanks for reminding us about this, Craig; this does need discussion indeed.
<br>
<br>
</div>
<div>I can live with the ligature element that remains specific to the mensural module, but then in CMN I would expect an attribute on line to indicate a transcription of notes originally in a mens.ligature, otherwise an important piece of information would
be lost in translation. Any line (bracket) has a "function" , isn't it? <br>
<br>
<br>
</div>
<div><font size="1"><font size="1">--</font></font><br>
<br>
</div>
<div><font size="1"><font size="1">Giuliano Di Bacco</font></font><i><font size="1"><font size="1">
</font></font></i><br>
<i><font size="1"><font size="1"><font size="1">from a small mobile device: excuse brevity and typos</font></font></font></i><font size="1"><font size="1">
</font></font></div><div><div class="m_-779595372959607203h5">
<div class="gmail_quote">On Jan 27, 2017, at 01:32, Craig Sapp <<a href="mailto:craigsapp@gmail.com" target="_blank">craigsapp@gmail.com</a>> wrote:
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Here is a note from Perry from Sept 2015 to the MEI-L mailing list about this topic:
<br>
<br>
<span style="font-size:11pt;font-family:"calibri","sans-serif""> </span>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">Line is the appropriate entity. I can hear the sighs now, but the
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">ligature</span> element in <span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">
MEI</span> is not intended for these <span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">
brackets</span> – “The <span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">ligature</span> element should not be used for
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">brackets</span> in modern notation that indicate notes that were part of a
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">ligature</span> in the original source.” (from the description of
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">ligature</span> in the schema) and so it’s currently in the
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">MEI</span>.mensural module – it disappears when
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">MEI</span>.mensural is not invoked. Creation of a similar entity for CMN or merging of
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">ligatures</span> in both repertoires is a possibility, but the topic needs discussion.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">Currently, a line can only be positioned relative to the objects referenced by its @startid and @endid attributes using @start(ho|to|vo) and @end(ho|to|vo). But, I don’t think
there’s any reason not to allow @tstamp, @tstamp2, @staff, @layer and @place. Even so, I think the best (that is, most precise) way to position lines is by associating them with specific events or time stamps. The @staff, @layer, @place attributes can only
be useful for making sure the lines associated with a particular staff are considered when processing that staff’s data, for instance when rendering a single staff (e.g., part extraction).</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">In any case,have a look at the
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">mei</span>-all_anyStart.odd in /develop-perry. Line has undergone some significant changes. Its new attributes:</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">form: dashed, dotted, solid, wavy</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">width: narrow, medium, wide, or numeric value + unit (cm|mm|in|pt|pc|px|vu)</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">endsym: angledown -- 90 degree turn down (similar to Unicode 231D at end of line, 231C at start).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">angleup -- 90 degree turn up (similar to Unicode 231F at end of line, 231E at start)</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">angleright -- 90 degree turn right (syntactic sugar for "angledown" for vertical or angled lines).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">angleleft -- 90 degree turn left (syntactic sugar for "angleup" for vertical or angled lines).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">arrow -- Filled, triangular arrowhead (similar to SMuFL U+EB78).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">arrowopen -- Open triangular arrowhead (similar to SMuFL U+EB8A).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">arrowwhite -- Unfilled, triangular arrowhead (similar to SMuFL U+EB82).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">harpoonleft -- Harpoon-shaped arrowhead left of line (similar to arrowhead of Unicode U+21BD).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">harpoonright -- Harpoon-shaped arrowhead right of line (similar to arrowhead of Unicode U+21BC).</span></p>
<p class="MsoNormal" style="margin-left:0.5in;text-indent:0.5in"><span style="font-size:11pt;font-family:"calibri","sans-serif"">none -- No start symbol.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">endsymsize: 1-9 (relative size)</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">startsym: [same as endsym]</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">startsymsize: [same as endsym]</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">Andrew, when you say you’re supporting
<span class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945gmail-il">MEI</span> 3.0.0 in SibMEI, are you using these new attributes?</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 26 January 2017 at 13:57, Andrew Hankinson <span dir="ltr">
<<a href="mailto:andrew.hankinson@mail.mcgill.ca" target="_blank">andrew.hankinson@mail.mcgill.<wbr>ca</a>></span> wrote:
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Daniel, <br>
<br>
You've (perhaps unknowingly) stumbled on one of the core tenets of MEI -- the separation of the semantic and the symbol.
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
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. <br>
<br>
-Andrew <br>
<div>
<div class="m_-779595372959607203m_-1157455005656602243m_6204305444615194945h5"><br>
<br>
<br>
> On Jan 26, 2017, at 10:40 PM, Daniel Alles < <a href="mailto:DanielAlles@stud.uni-frankfurt.de" target="_blank">
DanielAlles@stud.uni-frankfurt<wbr>.de</a>> wrote: <br>
> <br>
> New day, new questions - I hope this will get better soon... <br>
> <br>
> Dear all, <br>
> <br>
> 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). <br>
> <br>
> 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?
<br>
> <br>
> I hope, someone can help me with that. <br>
> <br>
> Best regards, <br>
> Daniel <br>
</div>
</div>
> <01_heugel_magnificat_cmn.pdf> ______________________________ _________________
<br>
> mei-l mailing list <br>
> <a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a>
<br>
> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">
https://lists.uni-paderborn.de<wbr>/mailman/listinfo/mei-l</a> <br>
<br>
<br>
______________________________ _________________ <br>
mei-l mailing list <br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a>
<br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">https://lists.uni-paderborn.de<wbr>/mailman/listinfo/mei-l</a>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div></div></div>
<br></div></div>______________________________<wbr>_________________<span class=""><br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">https://lists.uni-paderborn.de<wbr>/mailman/listinfo/mei-l</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" rel="noreferrer" target="_blank">https://lists.uni-paderborn.<wbr>de/mailman/listinfo/mei-l</a><br>
<br></blockquote></div><br></div>