public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: XWin: Tiny fonts on high resolution display
Date: Sat, 29 Sep 2018 04:19:00 -0000	[thread overview]
Message-ID: <dcd87518-5857-6c71-e766-5284f9815ffa@SystematicSw.ab.ca> (raw)
In-Reply-To: <0e46d9b2-eb1c-f062-643b-1f6fe90b3037@cornell.edu>

On 2018-09-28 20:25, Ken Brown wrote:
> On 9/28/2018 8:06 PM, Thomas Dickey wrote:
>> On Friday, September 28, 2018 6:32:25 PM, Ken Brown wrote:
>>> A Google search shows that this is a very frequently asked question (e.g.,
>>> https://sourceware.org/ml/cygwin/2016-07/msg00247.html), but I haven't found a
>>> good answer, except perhaps to use Gnome or some other desktop environment.  (I
>>> haven't tried that yet.)
>>> I just got a new laptop with a 3840x2160 display.  When I start the X server via
>>> startxwin, xterm and emacs open small windows with tiny fonts.  Here are the
>>> xterm and emacs settings in my .Xresources:
>> But none of those are for fonts. With bitmap fonts, you generally can use
>> 10x20 (12x24 is not so good). Otherwise, your choice would be a TrueType
>> font (which generally have poor coverage of Unicode -- a problem since
>> xterm loads only one font).

DejaVu Sans Mono has pretty good UTF-8 glyph coverage and is regularly updated:
DejaVu has been my font family of choice everywhere for a few years.
The Unicode Font Resources page has other font suggestions with higher glyph
counts, but most are not as readable, especially for developer content.
Windows font linking allows fallback fonts to be used where glyphs are missing.

>> If you don't need to read CJKV, that's okay though...
>> With TrueType fonts, you can scale it:
>> 
https://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize

> Thanks.  The 10x20 font was still too small, but I was able to get a reasonable 
> xterm by adding
>    XTerm*faceName: Lucida Console
>    XTerm*faceSize: 24
> to .Xresources.  The only remaining problem is that the menus are still tiny.  I 
> saw https://invisible-island.net/xterm/xterm.faq.html#tiny_menus, so I changed 
> 'XTerm*geometry:  80x45' to 'XTerm.VT100.geometry:  80x45'.  But that didn't 
> help. Do you know how I can fix the menu fonts?

If you are having problems getting apps to display e.g. 10pt fonts looking like
10pt, 8pt etc., you might want to try Windows Settings/Display/Scaling designed
to help with app high res display issues.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2018-09-29  4:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  0:07 Thomas Dickey
2018-09-29  2:25 ` Ken Brown
2018-09-29  3:03   ` Eliot Moss
2018-09-29  4:19   ` Brian Inglis [this message]
2018-09-29 12:35   ` Thomas Dickey
2018-09-29 12:49     ` Ken Brown
  -- strict thread matches above, loose matches on Subject: below --
2018-09-28 22:32 Ken Brown
2018-09-29  2:21 ` Eliot Moss

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=dcd87518-5857-6c71-e766-5284f9815ffa@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).