On Wednesday 27 Oct 2004 20:56, Steve Harris wrote: > I dont know about this font in particular, but fonts shouldn't be > resuing other symbols to do things they need, they can use the > unicode glyphs for typesetting symbols. That's fine for new fonts, but it's not much help when using existing fonts. Lilypond's Feta and those from Coda and Sibelius usually have a different range of glyphs from the Unicode set, so they can't be directly remapped. For example they may have a combining flag symbol (a single flag that can be drawn as many times as required onto a note stem) instead of separate glyphs for 1, 2, 3, 4 or 5 -flag notes as in Unicode, and they often include single glyphs for things like mordents that are composite in the Unicode set. A practical problem for people using Qt is that you can't address the musical symbols range at all using Qt's character class, which only supports UCS-2 (16 bits without surrogate pair support). There's no way around that except to use something other than Qt for rendering. (That's one reason Rosegarden uses Xft directly... that and a few other dumb things Qt does that make it really hard to use any font that doesn't have a full complement of latin1 symbols.) Chris
