pe-ro
pe-ro
TEI uses a NCNAME as the datatype for `@reason`. But changing the datatype for MEI may break backward compatibility in some cases. To encourage more TEI-like values in the `@reason`...
To be more in line with TEI, the values allowed by `att.regularMethod/@method` should be "silent" and "markup". Typically, correction that isn't carried out silently is accomplished by using elements, but...
As indirectly suggested by @craigsapp in https://github.com/music-encoding/sample-encodings/issues/9.
The `` element and its `` children support the encoding of chord tablature grids like those found in pop sheet music. For example,  can be encoded as ``` ```...
Support for _jianpu_ (and other number notations) would be a useful addition to MEI. For background on this topic, see #1680 . > Hi @craigsapp, your suggestion comes at an...
Currently, `incipCode/@form` uses the value "parsons" to indicate that the incipit contains an encoding of melodic contour. A better value here would be "melodicContour", defined as > "Representation of 1]...
As part of a non-MEI project, I created an XSL transform [tagAnalysis.zip](https://github.com/user-attachments/files/18241382/tagAnalysis.zip) that generates a "census" of elements and attributes (as well as their values) from an XML instance. The...
There's currently no method for indicating that a word/syllable has an extension line. Making `` a member of att.extender will permit mark up like the following -- ``` Je ```...
Restricting the struc-unstrucContent macro will allow fewer sub-elements in those places where the macro is used; that is, mostly in metadata elements in the header. If more markup granularity is...
`` was given its name as a companion to ``; that is, as an auditory alternative to the MEI encoding in the way that a facsimile is a visual alternative....