trunk now supports setting the dpi with "xpra --dpi=NN", details here:
https://www.xpra.org/trac/ticket/163#comment:7
Cheers
Antoine
On 08/02/2012 01:58 AM, Antoine Martin wrote:
On 08/02/2012 01:53 AM, Neal Becker wrote:
If I do this with xdummy, it's better. Fonts still look crappy compared
to running emacs directly (or via ssh -X).
Can we continue this discussion on the ticket?
https://www.xpra.org/trac/ticket/163#comment:6
(apologies to the list readers)
You can attach screenshots there of what your "crappy" fonts look like.
Be aware that since the rendering is done to a virtual screen, certain
font features like smoothing/anti-aliasing and sub-pixel rendering will
be difficult or simply impossible.
Antoine
On Wed, Aug 1, 2012 at 2:33 PM, Antoine Martin <anto...@nagafix.co.uk
<mailto:anto...@nagafix.co.uk>> wrote:
On 08/02/2012 01:20 AM, Neal Becker wrote:
If I comment out xvfb= from /etc/xpra/xpra.conf, it's better. I
guess
this is the old Xvfb version. Still wrong dpi, but not as bad
as with
xdummy.
Found a solution for you, just run this on your client before
connecting with xpra:
echo "Xft.dpi: 96" | xrdb -
Looks like your DE (which one do you use?) or X11 startup scripts
are not setting the Xft.dpi, so applications fallback to
xdpyinfo-like data from somewhere (Xlib?) which has the wrong value.
I will make a proper solution for trunk and 0.5.0 release.
Thanks!
Antoine
_______________________________________________
shifter-users mailing list
shifter-users@lists.devloop.org.uk
http://lists.devloop.org.uk/mailman/listinfo/shifter-users
_______________________________________________
shifter-users mailing list
shifter-users@lists.devloop.org.uk
http://lists.devloop.org.uk/mailman/listinfo/shifter-users
