Ok now I get it! Since normally I don't have any troubles with fonst on my X I never gave it the time to understand the process of fonts. So if I'm getting this right, the issue is the following:
- Xvnc does not support ALL fonts - You ither use fontpaths or fontservers or boths I think I saw something about a font that Xvnc couldn't read in the log. Failed to load font: -*-gamow-medium-r-*-*-7-*-*-*-*-60-*-* It would be really bad luck if it is just the font my remote application is using. So it really doesn't matter how much my font path is exactly the same as my X-font path. There still be some fonts Xvnc will be unable to read properlly, right? My question now is, would an alternate font server (a more conservative on, the app is on an old SunOs machine) on my FreeBSD mashine solve the problem with showing the font right? Or viewed from another angle, would a font server make the font-showing work instead for Xvnc or is Xvnc still going to make some sort of translation, or what ever it might be called? In that case it would be a bonus for me to get a name on a practical fontserver. // Walter -----Ursprungligt meddelande----- Fren: Corni Beerse [mailto:[EMAIL PROTECTED] Skickat: den 25 oktober 2004 15:00 Till: Cruz Walter Dmne: Re: SV: SV: Fonts not showing right under VNC Cruz Walter wrote: > OooooooKkkkkk! > > I'm getting tired, been tryng most things I know of to get this > working. But it still doesn't work. A hint could be found by some > vnc-expert here if I present my working :0 display versus my :1 not working display. Ok, I was off for some days, I might have missed something. On top, Xvnc does not support all fonts. What happens with not-supported fonts is also depending on the configuration... What you should do for investigation is roughly the next: use the `xset` command to update the fontpath in the Xvnc session. See `man xset` for details: use `xset -query` in both displays to find the used fontpath. Then use `xset fp+` or `xset +fp` (in the Xvnc session) to add the font-drectories to the Xvnc session. Be carefull, a bad font-setting can ruin your view. Restart apps in the Xvnc session to see the results of the new fontpath. Once you have a decent fontpath, add it to the call to `Xvnc` (in `vncserver` for example). As told before, Xvnc does not support all fonts, some are not displayed at all, some are just sharper on the edges and some are mapped to others. > > I really can't find what the problem is. It might though be that my X > and Xvnc are not using the same font server. But I don't know how to > check which fontserver is running on my machine. Apparently it must be > a good server since my :0 Session is able to read the fonts correctly. If you use a font-server (fontdirectory is kind of 'machine:port' like 'unix:7100', then the used font-server might be able to translate fonts for you. Chenk the fontserver for details. Try the used X-server on the console. > > I'm now checking om the FreeBSD manual to see if I find a way to check > what server I'm running. As for Xvnc, I'm not sure if you can help me > find out which server it's using. If `xset -query` lists some directories, it is not using any fontserver... > > // Walter > > ________________________________ _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
