| Summary: | For God's sake, please ignore EDID DPI and just default to 96! | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Tom Horsley <horsley1953> |
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | enhancement | ||
| Priority: | high | CC: | martin, mike, mrmazda, sbrabec |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Tom Horsley
2009-03-08 13:56:14 UTC
Personally, I always set dpi at the startx command line.
My startup script looks essentially like:
startx -- -dpi 133 -retro -nolisten tcp "${*}"
Yea, I used to be able to do that until GDM "improved" so much that you can't control the server options. And a global setting probably isn't as good as a per-monitor setting for a multi-monitor setup (since the monitors might have radically different resolutions). "I've never found a monitor where 96 DPI fonts were not readable." I own one. It's called a Sony Vaio P. 1600x768, 8" monitor. Its natural DPI is around 180. Set to 96, fonts at normal sizes (9-12pt range) are so small as to be more or less unreadable (if you look for reviews of the Vaio P, this is a common complaint from reviewers, who are apparently unaware of the intricacies of resolution dependence in font sizing). There are other similarly high-resolution displays for which 96dpi is a terrible setting, and they will only become more common over time. Particularly where X is deployed on e-ink displays... Seems to me DPI ought to be directly configurable on a per display basis via xorg.conf to the exclusion of all other methods. DPI can be defaulted to the greater of 96 or DDC/EDID provided display characteristics, but overriding either directly (for those wanting some particular DPI, e.g. 'Option "DPI" "132x132"') or indirectly (e.g. 'DisplaySize 495 310') should be enforced regardless of gfxchip or driver. Those who want to use some GUI tool to handle the configuration it can have some GUI tool change a local xorg.conf, with a possible option as superuser to change it globally. The current DPI customization settings elsewhere in X, Gnome, KDE & anywhere else should be abandoned. Xrandr could be used to make changes to an active session, but this/these should not survive a session restart without being integrated into xorg.conf, if then, so that control of any global non-default setting can be found in one single FHS location, or non-globally in one single location in the user's home tree (e.g. ~/.config/xorg.conf). Alternatively, /etc/X11/Xresources & ~/.xresources could be be used instead of xorg.conf, but it/they would have to be enforced by Xorg as the only valid place(s) for overriding DDC/EDID calculated or 96 DPI defaults. Idea in the bug 23577 is partially related to this issue. Yawn. (In reply to Tom Horsley from comment #0) > I've never found a monitor where 96 DPI fonts were not readable. It's because you're cheapskate buying junk to look at. And if you had any brains you'd probably understand that it's not gonna help to shoot the messenger (suppress DPI) but there might be a need to provide a UI magnification knob which is *completely* irrelevant to the physical DPI question. And your fanatical/idiotical/younameit "rationale" at https://home.comcast.net/~tomhorsley/game/dpi.html#Rationale doesn't even get that it's the COMMON case that should be optimized for, not the CORNER (aye I've worked with X11 on several large plasma displays and tuned things up a bit, but that was expected as the setup was quite custom anyways). Ah, and the disclaimer: I can testify for each word *characterizing* you, no need to even feel offended by someone grumpy over there looking at a 166dpi :0. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.