cable@ppgbms (Cable Pyen) (06/05/90)
Greetings! We have a slight problem inserting (adding?) a user defined font into an existing font set under OpenWin Version 2. We would like to extend an existing font with some primitive graphical charaters: four corners, a horizontal line and a vertical line. There are quite a few ostensible examples in the blue book that show how one might go about creating, re-encoding, and changing existing fonts. Thus no problem in PostScript, however, when we try to merge(?) two font sets into one, we are stuck because there seems to be no way of getting beneath the '/BuildChar' procedure, where we felt that we can retrieve the name of the array that holds the path construction procedures. The following lines run in 'psh' might help me to clarify my predicatment: /You_Name_The_Font findfont % puts it on the statck /BuildChar get == As you can see, /BuildChar is not a procedure according to the NeWS server, but rather a label for a fonttype. Why? Is it by design that we are deprived of knowing what the NeWS font machinary really is ? Or are we barking up the wrong tree? It would be most helpful if someone can tell us that 'there is no need for merging two fonts because there, already is one and it's called XXXXX font' or 'we had a same problem but we solved it by doing XXXXX'. What we don't want to do is font switching, for performance reasons. Other than that, any suggestions are appreciated. Thanks a gig! _____________________________________________________________ |Regards, One Campus Drive | |Cable Pyen PPG Biomedical Systems | |914-741-4626 Pleasantville, NY. 10570| ------------------------------------------------------------- path ppgbms!moe!cable@philabs.philips.com