mouse@LARRY.MCRCIM.MCGILL.EDU (09/26/90)
I got a letter recently from someone saying that he'd used getbdf to get some fonts from some IBM server, which presumably has non-square pixels, and > I found that the heuristic for Y_RESOLUTION should really be xdpi (so > they match -- bdftosnf complains otherwise) rather than the > calculation that leads to the X_RESOLUTION if it can't find the > property. At present, if there is no Y_RESOLUTION property, getbdf calculates a value from the XDisplayHeight() and XDisplayHeightMM() return values. (Similarly, the X resolution is calculated from the display's widths.) I looked at the bdftosnf source code and found that yes, if the resolution values on the SIZE line differ, it produces a fatal complaint. Everywhere else in X, non-square pixels seem to be provided for. The sample server, for example, wants resolution values in both dimensions when using mfb or cfb to build ddx layers.... Why this apparent inconsistency? Anyone know? der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (09/26/90)
I looked at the bdftosnf source code and found that yes, if the
resolution values on the SIZE line differ, it produces a fatal
complaint.
This is a bug, please submit a bug report.