https://bugzilla.novell.com/show_bug.cgi?id=373090
User mhopf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=373090#c16
--- Comment #16 from Matthias Hopf
The simplest workaround for these is what Stefan wronte in comment #12:
If the DisplaySize detected by DDC results in a dpi smaller then 75 dpi, ignore the true DisplaySize and calculate a faked one which results in 75 dpi. This gives resonably big fonts on such screens.
Sounds reasonable. This sort-of gives the best of both worlds. However, this should be implemented in the toolkits, because some applications want to know the *real* screen size (e.g. to implement a 100% zoom for formats with physical measurements e.g. in screen readers or DTP).
A better solution (which would give perfect results), would be to let the user change the distance to his screen is. E.g. Sax2 could have an entry field in the monitor section for the distance with a default value of 80 cm. If the user doesn’t change that default, Sax2 writes
I'd rather have the user specify the default font size in pixels. That is typically well understood, and users won't understand that they have to change this value if they don't like the font size, and they won't understand, that changing this value would result in fake dpi values.
¹ And projectors only if they are used as the main display, when they are used for presentations the problem does not occur as the dpi calculation (and therefore the font size calculation) is done for the main display (e.g. the laptop display) and the projector just shows the same picture which usually shows reasonably sized fonts then.
Actually, it isn't, because RandR has no notion of a "primary" screen :-( What happens in these circumstances is up to the driver. If the projector isn't attached on Xserver startup (what is typically the case), you're right, though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.