rcb@cccvs1.ncsu.edu (Randy Buckland) (04/11/89)
Does anybody know where I could ftp a set for bdf format fonts for X11R3 that would be as usable as the decwindows terminal fonts. The decwindows fonts appear to be in a strange format that the standard X server won't read. Randy Buckland rcb@ncsuvx.ncsu.edu
klein@lupine.UUCP (Doug Klein ) (04/13/89)
In article <2817@ncsuvx.ncsu.edu>, rcb@cccvs1.ncsu.edu (Randy Buckland) writes: > Does anybody know where I could ftp a set for bdf format fonts for X11R3 > that would be as usable as the decwindows terminal fonts. The decwindows > fonts appear to be in a strange format that the standard X server won't > read. If you are using an R3 server, this problem is not difficult to overcome. What we have done to run DECWindows apps on a variety of servers is to use font aliasing to "fool" the programs into thinking they had DEC fonts. The missing fonts are the cursons and all of the fonts with either "TERMINAL" or "MENU" in the name - as far as I can tell, all of the others are in the 75dpi directory on the R3 release tape. One quick and dirty solution is: 1. On the DEC server, "xlsfonts > decfont.file", to get a list of all the font names you will need. 2. In your favorite editor, remove all lines without "TERMINAL" or "MENU" in them. Put quotes around the remaining lines to take care of embedded blanks. 3. At the end of each line, add some known font name. If you have great patience, you could try to find an "appropriate" font, but if you are like me, you'll just alias them all to a single font, and then go back selectively and patch up the file. 4. Add the result to the fonts.alias file in /usr/lib/X11/fonts/75dpi. 5. Add the line "decw$cursor cursor" to the fonts.alias file in /usr/lib/X11/fonts/misc. (This will give you working cursors, although the glyphs will be a little weird. Again, with patience, this can also be fixed.) Doug Klein Network Computing Devices klein@ncd.com -- Doug Klein Network Computing Devices uunet!lupine!klein