forked from rism-digital/verovio.org
-
Notifications
You must be signed in to change notification settings - Fork 0
/
doc.html
38 lines (33 loc) · 1.99 KB
/
doc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
---
mei-doc-root: http://music-encoding.org/documentation/3.0.0/
---
{% comment %}
{_% mei_supported_to_liquid supported-mei.yml %_}
{% endcomment %}
<p>
This page documents the elements and attributes that are currently supported by Verovio. It is also important to note that the hierarchy of elements supported by Verovio is limited and that it will also determine wherether an MEI document can be rendered or not.
</p>
<h4>MEI elements</h4>
<p>
Verovio supports a subset of MEI elements and attributes that are documented here. Additional elements and attributes will be added in the future.
</p>
{% for class in page.doc.classes %}
{% include mei-class.html %}
{% endfor %}
<h4>Page-based customization elements</h4>
<p>
A few elements supported by Verovio are defined in the page-based customization describe on the <a href="{{ site.baseurl}}/structure.xhtml">structure</a> page.
</p>
{% for class in page.doc.page-based-classes %}
{% include mei-class.html %}
{% endfor %}
<h4>Load-only MEI elements</h4>
<p>
Verovio can load both page-based customized and uncustomized MEI documents. When loading uncustomized MEI documents, some MEI elements are loaded by Verovio and converted to a page-based representation. Typically, <code><pb></code> milestone elements are converted to <code><page></code> container elements. Oppositely, <code><section></code> container elements are converted to <code><secb></code> milestone elements.
</p>
<p>
There are also some MEI elements that Verovio can load but only if they can be converted to an alternate MEI representation. For example, Verovio can load <code><tupletSpan></code> elements but only when then can be appropriately converted to <code><tuplet></code> elements. Verovio tries to perfom the convertions when loading the document. This has nothing to do with the page-based customization.
</p>
{% for class in page.doc.loaded-classes %}
{% include mei-class.html %}
{% endfor %}