On 20-06-2013 22.15, Hartmut Lemmel wrote::
> The quintessence is: Windows does not invoke any glyph transformations
> for PUA characters.
>
> …
>
> It was also mentioned in this list that there are problems with
> diacritics or ligatures in html. So maybe we should drop the idea
> completely. That's a pity because I really liked the idea.
I like the idea so much, that I have made some tests. Indeed, ligatures
of PUA-characters work only in applications that do not rely Uniscribe
(Adobe Illustrator but also Sibelius 7 are examples). However, I managed
to make a font that is formally SMuFL-compliant (i.e. musical glyphs
have appropriate codepoints) and uses OpenType anchors and contextual
substitution for placing accidentals over/under ornaments. It works in
Word 2010 under Windows 7.
It has been done so, that the input is based on “lower ASCII”
characters; these characters are then substituted (by stylistic set
feature) to musical symbols. Word does apply substitutions and mark
positioning to these glyphs.
The font is here, just for reference (you may use it if you find it
useful, but the linespacing is wrong):
https://www.dropbox.com/s/vt0yabk7nwq2yow/GoudyBookletter%2BOrnaments.zipThe problem is, that the *text* (i.e. the special characters) is not
encoded, it still bases on ASCII. On the other hand, the input method is
much more convenient than inputting characters from PUA. Perhaps it
would helpful, if SMuFL could address this kind of usage in running
text, i.e. ASCII-based input for use in word processors.
--
Emil Wojtacki
#############################################################
This message is sent to you because you are subscribed to
the mailing list <
[hidden email]>.
To unsubscribe, E-mail to: <
[hidden email]>
To switch to the DIGEST mode, E-mail to <
[hidden email]>
To switch to the INDEX mode, E-mail to <
[hidden email]>
Send administrative queries to <
[hidden email]>
Locked
