Thomas Weber

@kepper Shouldn't we remove `@fontname` and `data.FONTNAME` entirely? They are not only used by `att.typography` (which your commit handles), but also by `att.lyricStyle` and `att.textStyle`.

A little summary: One encoding that [has been proposed](https://github.com/music-encoding/music-encoding/pull/704#issuecomment-802800705): ```xml  ``` Or [without ``](https://github.com/music-encoding/music-encoding/pull/704#issuecomment-832653453): ```xml  ``` [CSS-like fallbacks](https://github.com/music-encoding/music-encoding/issues/716#issuecomment-1024179509) (e.g. `fontfam="Leipzig,Bravura,smufl"`) might work, too, though there were [objections](https://github.com/music-encoding/music-encoding/pull/704#issuecomment-802307164).

BTW, is it possible to define the signed types by referencing the unsigned types rather than duplicating the patterns?

`em` etc. only makes sense in the text context, I think. In HTML, these units are usable anywhere, but in HTML, in any context, there is a defined text size...

I share @ahankinson's opinion this should be encoded logically as ``. We could allow a bracket element inside ``, or probably even better ``. I see `` as a more...

@rettinghaus No, apparently I haven't.

But then this isn't an illustration of the `` element any more, so it needs to be replaced with something different.

This is of course not the whole picture as all the dynamics (forte, piano, ...) are input as Expression. We therefore have to analyize the content to generate `` for...

@lpugin Can you supply an example file for that? I don't think sibmei ever created `` elements. If I understand you correctly, you talk about ficta accidentals, which Sibelius has...

As we have a client who "ordered" MEI 4 from Sibelius input, I'd like to stick with MEI 4 for the things I'm going to do next. I'll be absent...