Comment 12 for bug 8357

> The wysiwyg argument is a bit of a strawman. If an application is trying to
[...]

I'm not an expert in this topic, so I won't try to discuss the
technical necessity. However, when reading your following statement:

> Now if we put aside the wysiwyg argument and look at "the size of fonts used to
> draw the UI", then it is pretty clear that the physical resolution is not that
> important. What is important is to make a font of size "12" look about the same
> on whatever screen you are using, which means you want to callibrate the angular
> resolution instead (which depends on both the physical DPI and the distance from
> the screen). Unfortunately the X server can't tell us what that value is, which
> is why the user can adjust it in the control panel.

..it seems obvious to me that:

a) the setting should be named something like "fontsize"
If the value is only used for drawing fonts and has no direct connection
to the physical DPI than this would be a much more descriptive name which
doesn't lead to errors like mine.

b) the setting shouldn't be absolute but rather a corrective factor for
the actual X11 DPI value.
Currently, we are asking to user for a value depending on two factors:
DPI and distance. However, we already know the DPI. This is a source for
problems. Why don't we only ask the user for the variable we don't know?