Fri 15 Dec 2017 09:14:31 PM UTC, comment #5:
Many valid Unicode strings are nonsense and there is no reason for a font to support them. For example, if you put a flag before a stem, it looks bad in FreeSerif; but that is a problem with the string, not the font.
I agree that a tremolo on a sixty-fourth note is probably too impractical for anyone to use it, so it is not worth spending much effort on that combination. If you did want to support something like that, I suppose you’d have to find an attestation, or do something reasonable-looking if it is unattested.
For combinations which are valid and attested, but which Unicode does not explain in enough detail, there are a few possible solutions. You could deduce what the standard should say, based on similar characters in other blocks and based on the relevant proposal. Often the proposal goes into great detail which the standard summarizes in one page.
Alternatively, you could report the omission to Unicode and hope they clarify things in the next version.
The particular case of tremolos on stemless notes, though, I don’t think is a matter of personal feelings. It is clear what the Unicode encoding is (because nothing else would make sense and because one of the proposals explicitly calls this case out) and what it should look like (because it is attested in sheet music).
|