Felmon Davis wrote: use Xorg instead of X Xorg :0 -configure

Felmon Davis composed on 2017-08-03 17:34 (UTC-0400): Only the GTK3 version is relevant to the potential problem of GTK3-built apps not obeying your TDE font settings, which may have nothing to do with the tiny fonts you are actually seeing. Since about 11 years ago, Xorg has been forcing millimeters to whatever numbers are required to result in 96x96 DPI, unless manually configured to produce some other values. The theoretically /accurate/ value is in your laptop's specifications. You can get close enough with a ruler. For a 13.3" 16:9 display it should be about 294.4 X 165.6 for a 267.3 DPI result. http://fm.no-ip.com/PC/displays.html has a lookup table you can check against and make comparisons. 267 is clearly the highest density there listed, and the highest I've ever seen anyone discuss on a mailing list. The practical optimum can only be determined via experimentation. That's the unfortunate typical result of upstream Xorg for compatibility reasons retaining a virtually useless and broken tool. In modern releases it's useless 99%+ of the time. Most of the time automagic just works and no xorg.conf is needed. The main problem is "most of the time" turns into hardly ever with very HiDPI displays. Save http://fm.no-ip.com/Share/Linux/xorg.conf-minimal-EDID-workaround to use as an /etc/X11/xorg.conf template. Create in it an uncommented DisplaySize line. Using half the values reported above that produce 96x96 /should/ produce 192x192 as a place to start your experiments: DisplaySize 423 213 # 192 DPI @ 3200x1800 If that turns out to be overkill, try half as much increase: DisplaySize 635 320 # 144 DPI @ 3200x1800 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

On Fri, 4 Aug 2017 01:15:13 -0400 (EDT) Felmon Davis <davisf(a)union.edu> wrote: HorizSync and VertRefresh shouldnt affect font size at all. This are limits of what you monitor is capable off, they only affect what modes Xorg thinks are available. You normaly souldnt set them at all, they should be read from EDID, only tinker with them if some video modes that should be present are not. -- Nick Koretsky (nick.koretsky(a)gmail.com)

Felmon Davis composed on 2017-08-04 01:15 (UTC-0400): ... Jessie never shipped with GTK3 AFAICT, so likely its missing from Exegnu as well. Current Firefox and SeaMonkey versions downloaded directly from Mozilla.org depend on it. Linux distros, older versions at least, for the time being have the option to keep building with GTK2 instead, and probably all that provide ESR versions are doing so. LO might be using GTK3 already that far back, I don't know, but it provides its own means of manipulating font sizes anyway (and defaulting in every one of my installations to tinier than anything else). Not a surprise to me. Shock. :-( What did/do "xrdb --query | grep dpi" and "xdpyinfo | egrep 'dimen|ution'" report? Do they match what is reported if you load http://fm.no-ip.com/Auth/dpi-screen-window.html in a Gecko browser (Firefox, SeaMonkey, others) or Konqueror w/ KHTML, but not Chrom* or Opera. ... I should have told you that you should be able to comment away those lines. If that doesn't work, and it should, those values should be in the full specs for that laptop. hwinfo --monitor | grep -A6 'river Inf' should tell you what they are, and if it does, then it confirms they /should/ not be necessary, that is, if hwinfo even ships in Exegnu. Try: ddcprobe ! grep monitorr You can manufacture working ranges from the timings listed in Xorg.0.log, or from verbose xrandr output. OTOH, because that display is such high resolution, proper ranges might be unusual. It's probably superfluous, but couldn't hurt either. Another option is to /not/ use the native 3200x1800 display mode. On a 13.3" inch screen that's way out of normal range for most developers to try to emulate to make everything work nicely visually. Unless your eyes are extraordinary, you are likely not to notice much if any difference by employing 1920x1080 instead: Option "PreferredMode" "1920x1080" With any luck and good eyes, you wouldn't need to fuss with DPI or suffer extra tiny fonts. To go this route you should be able to dispense with xorg.conf entirely and make select that resolution in Trinity Control Center -> Peripherals -> Display -> Size & Orientation -> Screen Size. On such a tiny screen, you might find you like 1600x900 better yet. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

Felmon Davis composed on 2017-08-05 00:37 (UTC-0400): That's the expected result of using TDE Control Center to force 120 DPI (through Xft.dpi). Peculiar. 270x216 is a 1.25/1 ratio, 5/4, normally only seen with 1280x1024 resolution displays. 216 is a tad taller than that of a 1920x1080 17" screen. A bizarre ratio: 1.42:1. DPI and default font px size reporting require you let the scripts run. Interesting. Screen totals are correctly reported. Available and Viewport show exactly the values expected for a somewhat common screen size of 2560x1440. I have to wonder how you managed to get a Konq window to open at that size on a 3200x1800 screen. Odds must be astronomical that it happened by accident. That's about as close as Xorg ever gets to accurate. My calculator says a 13.3" screen should measure 294.44 by 165.62. Is that the result of using DisplaySize in xorg.conf set to manufacturer's screen size specifications? I don't see exegnu on DistroWatch, so without it installed, or more information on its web site than I've seen, I don't know if GTK3 is installed or what toolkit your LO or FF packages are built using. It looks like GTK apps are just not capable of reasonably responding to a display of such high DPI on exegnu, or maybe without being run in Gnome or Mate or other GTK DE or absent some unusual manual gtk configuration or additional package support. Your inability to find any gtk*3* packages installed is somewhat puzzling. A distro released only late last year ought to be providing at least basic GTK3 support. Maybe searching in OO or LO forums for HiDPI discussions would prove fruitful. Maybe we need to have a look at your xorg.conf if you're still using it. At least let's see Xorg.0.log generated by the best configuration you've come up with so far, with or without an xorg.conf. ... Assuming running at lower than native resolution won't be acceptable to you, that sounds like a good idea, unless you have really really good young eyes and better tolerance for things tiny than the existence of this thread suggests. It seems something in some software component, or maybe more than one, is just too broken for working on a 276 physical DPI screen. Is Windows still on it? What are its display/screen and font settings? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

Felmon Davis composed on 2017-08-05 02:42 (UTC-0400): Embedded in the page. Konq by default has scripts (JavaScript) disabled. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

Felmon Davis composed on 2017-08-06 18:33 (UTC-0400): Without knowing the content of xorg.conf, any optional startup xrandr command and seeing Xorg.0.log, there's nothing more for me to say about that response than what I wrote about it upthread. What's a terminal screen? The font used by an Xterm can be controlled, within limits, through ~/.Xresources. Mine have: xterm*faceName: Droid Sans Mono:antialias=true xterm*faceSize: 11 The font that is used on the vttys (traditionally tty[1-6]) can be changed multiple ways: 1-on a per boot basis, or repeatedly via bootloader configuration, by keeping the kernel's default size 16 font and applying a lower resolution video mode on the vttys through a cmdline option: a: vga= (e.g. 788, 0x317, 794) applicable if KMS is disabled, and for the initial boot message moments if not disabled b: video= (e.g. 1024x768 or 1440x900) applicable when KMS is not disabled, regardless of bootloader used (my preference) c: with grub2 and without KMS disabled, within limits, through /etc/default/grub (self-documenting) and grub2-mkconfig 2-by configuring vttys to use a font larger than size 16. setfont can do this on the fly using /usr/bin/setfont. (I never choose this method) ...> (b) if I kill X or boot into terminal, I get that teensy-weensy font As above. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

Felmon Davis composed on 2017-08-08 02:36 (UTC-0400): There are still not enough puzzle pieces collected together to get a decent handle on how to proceed. The Firefox UI and window decorations you omitted would have provided crucial context. Compare to having nothing altered except for TDE fonts enlarged from default 9 to 10 and TDE DPI set to 120: http://fm.no-ip.com/SS/KDE/felmon1-1800.jpg Was your Xft.dpi = 96 here? 120? Something else? (Force DPI in font settings sets Xft.dpi.) Which if any Firefox font settings have you changed? Do you have an xorg.conf, and if yes, does it have a DisplaySize set, and if yes, to what? Have you changed Firefox's layout.css.dpi and/or layout.css.devPixelsPerPx from defaults in about:config? The xrandr screen and the image of dpi-screen-window in Firefox can't fully be reconciled using the tools I have. Firefox says the screen is 1600x900 and font size is 16px because its applying a 2:1 device to logical px ratio. It's doing that because your 276 DPI screen falls short of a 3:1 ratio by 12px, and it rounds to lowest integer multiple of 96. Why the reported DPI is 56 I can't imagine. I think you need to figure out how to get all TDE fonts right first. As long as it's your default session type, it's your baseline. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

On Tue, 8 Aug 2017, Nick Koretsky wrote: so I've looked about, not sure I've found every nook and cranny, but haven't found settings in the places you've mentioned and elsewhere. have made some progress though. (1) I took measure of the screen; I think I could have used Felix's page but stumbled on <https://www.infobyip.com/detectdisplaysize.php> 9.6" diagonal; 8.3" width; 4.7" heigth I set '/etc/X11/xorg.conf/90-monitor' to: DisplaySize 294 165 (2) I turned off 'Force fonts DPI' in the Trinity Control Center and set dpi to 190 via echo Xft.dpi: 190 | xrdb -merge (3) did some settings in 'GTK Styles and Fonts' in TCC; GTK2 fonts are supposed to use Sans Serif 15, Redmond is style; GTK3 is on style TraditionalOk. fooled around re-sizing 'kicker' and with configs in some programs case by case. these measures cleared up most but not all problems. some programs still misbehave: (a) Gimp and LibreOffice have grotesquely large menu fonts. still can't quite find pertinent gtk or program settings. I have install Apache Office yet. (b) icons are too small in Pan; probably something can be fixed in its config. not terribly important. some other icons elsewhere also small. I believe there are a couple of other issues I don't find now in my notes. of course I haven't opened everything that's been installed by default, most of which I will remove anyway. ah, e.g. I see something called 'Music Player' has teeny fonts. I likely won't use it but I'm discontent that I haven't developed a more systematic way to get control of the interface. I guess some of this requires program-by-program skirmishing. I'll explore more and pin things down. Cinnamon runs ok; next run I'll reconnoitre its gtk settings. thank everyone for advice and help. f. -- Felmon Davis Most people are too busy to have time for anything important.

On Mon, 7 Aug 2017, E. Liddell wrote: for some reason your emails always get trapped as spam (by gmail) so I often overlook them! I'm not sure I only have a GTK configuration problem since tiny fonts and icons affect 'kicker' and various submenus and some KDE apps, e.g. Kate. I'll play with gtk-font-name, and the others. this is turning out being one of my trickiest installs. -- Felmon Davis Someday we'll look back on this moment and plow into a parked car. -- Evan Davis