Thanks, Hans, for the suggestion. It works quite well, except the \ae{} macro starts producing a lowercase j. My guess is this refers to an encoding issue, since I found that using \sc tends to not do small caps except for using Computer Modern. I did RTFM, but I'm just not making the connection. If someone can point me to a document on fonts that I can work through ... the section in the manual left me a little confused. After using Pagemaker, Quark, and InDesign, I kinda get the approach but it seems to be a culture shock like Metafont was and remains. I copied the examples from the manual when I did a book mock-up for work and that worked real well. Everyone was impressed by what ConTeXt could do, although the official workflow will remain Incopy and InDesign. Still, I uotdid an experienced graphic designer using Adobe CS3 with my little bit of code for schemas. ConTeXt and friends have some unique benefits. So if I could solve the font mystery, I would be grateful. I have some books, for example, that I would like to reproduce with ConTeXt by scanning the Fraktur and OCR'ing with tesseract, then doing the layout with ConTeXt. I have an Ernestine Bible (Das Weimarische Bibelwerk) for which the binding is shot but the pages are good. This way will take much less than scanned images, although some images will remain. Ultimately I would like to make something like yfonts, but with unicode or some standard encoding to allow either umlauts or superscript e. In my own library I have books from the early eighteenth century on, and Google books has more, so there's no lack of subjects to scan into Fontforge. Charles