<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Dear MEI user,
<p>are you using Sibelius, but the MEI output of <a
moz-do-not-send="true"
href="https://github.com/music-encoding/sibmei">Sibmei</a>
doesn't quite fit the needs of your project? Or are you looking
for Software that supports project specific specialties when
generating MEI?<br>
</p>
<p>If so, please get in touch with Anna Plaksin and me. We have
some plans for Sibmei, and before putting them into action we
would like to find out if the approach is sound and suitable for
addressing others' requirements as well.<br>
</p>
<p>Our primary motivation is to make Sibmei better suited for the
very special needs of the <a moz-do-not-send="true"
href="https://www.uni-muenster.de/CMO-Edition/cmo/cmo.html">Corpus
Musicae Ottomanicae</a>. As modifying Sibmei for project
specific needs is not a sustainable approach, our plan is to lay
the groundwork for an extensible Sibmei. The goal is a Sibmei API
that we can use to write project specific mini plugins on top of
Sibmei.</p>
<p>The cleanest way to address project specific needs with Sibelius
is to use custom symbols, text styles and line styles where
possible. That's what we will be focusing on. Our priority would
be custom text and symbols for the start.</p>
<p>This approach will not make careful planning how to use Sibelius
superfluous (on the contrary), nor will it guarantee that
post-processing MEI will be a thing of the past. But it will
allow exporting some information that couldn't be exported
before. And we expect to make things easier for Sibelius users
and postprocessing.</p>
<p>Looking forward to hearing from you!<br>
Thomas Weber<br>
</p>
</body>
</html>