J.Fine writes: > I'd find it helpful to know to what degree CSS and > Unicode would solve font selection problems for > printed pages. > > Excluding mathematics, of course. That has its > own issues. and excluding text ... :-) unicode doesn't solve anything other than providing a character naming inventory. which is fine and helpful but is not at the heart of what a font selection scheme is all about. fonts do not implement unicode, at best they allow the glyphs they contain to be accessed by unicode names. but they do not contain glyphs for all unicode chararacters so in reality each of them implements a different encoding which is a subset of unicode. as far as the "set of supported gyphs" problem is concerned unicode as such doesn't solve anything unless you are happy with finding printed question marks or black blobs in your output whenever you have addressed a character not available in the current font resource. in other words, somewhere there has to be a knowledgeable instance that decides what to do when a current font selection doesn't work for the requested characters because it is not part of the supported glyph set of that resource --- you can consider that part of the font selection intelligence and it is not resolved with a naming standard for characters eg unicode frank