QNX RTOS v4 Knowledge Base
QNX RTOS v4 Knowledge Base
| Title |
Phindows Font issues |
| Ref. No. |
QNX.000009516 |
| Category(ies) |
Configuration |
| Issue |
1: Display of characters on the Phindows screen looks odd, with characters overlapping in places.
2: Fonts not displaying over a Phindows link.
3: Some fonts (like the one used to login user/password initially) display badly after the first few characters (they overlap?). All versions I have tried seem to do this. PHAB text entry windows often do it too.
4: Use of Japanese mincho fonts with Phindows
5: Some fonts look different in Phindows than in Photon.
|
| Solution |
Issue 1: Display of characters on the Phindows screen looks odd, with characters overlapping in places.
This was solved by deleting all the font files on the MS client machine (held in usrphotonfont), forcing new font files to be loaded as they were encountered.
Another possibility that would give this mismatch of font "metrics" (dimensions) would be unusual options on the Photon font mangager (phfontpfr or phfontphf). For example, if you were trying to force anti-alias always, or always use scalable fonts, there could be disagreements resulting from differing understandings between the Photon session and the Windows machine about what the metrics of a given font were.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 2: Fonts not displaying over a Phindows link.
This can be caused by one of two things.
The first thing to check is the Phindows.ini file in the Windows directory of the system. Check the Dir entry in the ini file and make sure that it points to the fonts directory on C:usrphotonfont
The other possibility, is that the fonts being transmited are scalable fonts (.pfr). If that is the case, phindows does not transmit these types of fonts, which would cause a blank where the fonts should be.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 3: Some fonts (like the one used to login user/password initially) display badly after the first few characters (they overlap?). All versions I have tried seem to do this. PHAB text entry windows often do it too.
The fontmap files on the QNX node needed to be "fixed" with fontcfg.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 4: Use of Japanese mincho fonts with phindows
You must have phindows 1.20 and the Japanese version of Windows95/NT on the MS side in order to see mincho fonts. Only bitmap fonts (14 point) will work if you don't have the Japanese vesion. You also need phjp on the QNX side.
Phindows will connect the Bitstream mincho fonts to the Microsoft mincho fonts which have very similar metrics. If you need an exact match, you will need to make the Bitstream mincho font available on the Windows machine. See the question on "fonts not displaying over a Phindows link" for further details.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 5: One of our customers develops Photon applications via Phindows. He has recently discovered that some Fonts (e.g. Helv16) are displayed differently via phindows or directly under Photon.
There is no helv16.phf on the QNX side; if there was it would have been downloaded by Phindows to the Win95 machine and used as an exact bitmap. I suspect that if you look in the user "fontmap" file there will be a line "helv = *swiss", which instructs the font server to use a scalable .pfr font to supply any missing helv font with a scaled swiss font (otherwise it would round down to helv14). Normally this is fine, but since we can't transmit Bitstream fonts, Phindows will substitute arial, so if you need _exact_ similarity between QNX and Windows you should disable these font mappings. You can use PfQueryFont() to query what actual font will be used by the server for any specified font name (real or missing or made-up).
|
|
