Adam Tkac wrote: > > If I start without -fp parameter all works fine. Btw newer Xorg > doesn't use xfs nor "standard" /usr/share/X11/fonts directory and > friends. > > I don't understand. What do you mean by "newer" Xorg? We're building Xvnc from our own Xorg code base, so why should it matter what version of Xorg is installed on the machine? Can you explain the new mechanism?
There were a couple of reasons why I added the font path auto-selection mechanism in TurboVNC 0.5: (1) The default behavior of Xvnc in TurboVNC/TightVNC was not to use xfs. It instead tried to use some hard-coded font path that was never correct. Thus, it was always necessary to pass some -fp argument to that version of Xvnc. Has this behavior changed in TigerVNC? What does it do if you don't pass -fp? (2) xfs is not available on all systems. In particular, it doesn't exist on OpenSolaris, nor on some Ubuntu and SuSE releases. Thus, using a default -fp argument of unix/:7100 was problematic. In order to verify the correct behavior, I ran xlsfonts and xfontsel with the font server and with the auto-generated font path and verified that they were reasonably similar. I'm certainly willing to change the behavior in vncserver-- I just need to understand what I'm changing. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
