From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Re: big fonts after Xorg update
Date: Mon, 19 Oct 2009 22:47:48 +0200 [thread overview]
Message-ID: <hbij9m$5pn$2@ger.gmane.org> (raw)
In-Reply-To: 58965d8a0910191338h6c6368a7o3e902b29f586009e@mail.gmail.com
* Paul Hartman (Mon, 19 Oct 2009 15:38:12 -0500)
>
> On Mon, Oct 19, 2009 at 3:18 PM, Thorsten Kampe
> <thorsten@thorstenkampe.de> wrote:
> > That was the solution. I checked the resolution before the upgrade with
> > "xdpyinfo | grep resolution" (Tip from the German list): 75 dpi.
> > Afterwards: 96 dpi. Setting it to 75 solved the issue.
> >
> > I'd still like to know what exactly changed and if 75 or 96 is the
> > "correct" value. Nevertheless, I have Xorg server 1.6 running and it
> > looks fine.
>
> Divide your screen resolution (pixels) by its visible area (inches) to
> get DPI. For example my monitor screen is 16 inches wide and 12 inches
> tall and I use 1600x1200 resolution. That is 100dpi. In my system this
> is autodetected when xorg starts (maybe the nvidia drivers do it?).
This is a VMware virtual machine using a virtual monitor on a physical
machine with two physical monitors. I'm not sure whether calculating DPI
that way would lead to meaningfull results for the virtual machine. This
whole "hard" setting of DPI for a monitor seems anachronistic to me.
Thorsten
next prev parent reply other threads:[~2009-10-19 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 23:22 [gentoo-user] big fonts after Xorg update Thorsten Kampe
2009-10-15 23:32 ` [gentoo-user] " Nikos Chantziaras
2009-10-19 20:18 ` Thorsten Kampe
2009-10-19 20:22 ` Alan McKinnon
2009-10-19 20:38 ` Paul Hartman
2009-10-19 20:47 ` Thorsten Kampe [this message]
2009-10-19 21:54 ` [gentoo-user] " Paul Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hbij9m$5pn$2@ger.gmane.org' \
--to=thorsten@thorstenkampe.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox