npn@cbnewsl.att.com (nils-peter.nelson) (03/12/91)
mho may indeed be the wrong character for conductance, but the orginal problem is still interesting. The following applies specifically to DWB 3.1. First, check the Adobe PostScript book for the character of interest. Some characters have font positions in the printer but are unknown to troff. These can be printed by using \N'number'. The width and ascender/descender info should be in the font table to assure troff leaves the proper space for it. (Rules are in the documentation.) Second, for completely new characters, you can install a PostScript program in /usr/lib/font/devpost/charlib. The character must also appear in one of the font tables (eg., S1, the special font). Easiest way to explain this is to just look at the files in /usr/lib/font/devpost/charlib. This is how we install our AT&T logo, ligatures, and replacement versions of characters we don't like in the RIP. The major problem with this approach is you either need write permission on /usr/lib/font, or you need to duplicate the entire directory structure in your own space and use the '-F' option on troff. Alas, we have not provided a trivial way for non-superusers to add custom characters. Maybe DWB 3.3... On the plus side, unlike earlier DWB's, in 3.1 all files are editable ASCII. No need for special software to make those awkward .OUT files.