From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Ishtar.sc.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by sourceware.org (Postfix) with ESMTPS id 8651D3858D28 for ; Sun, 23 Jan 2022 20:26:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8651D3858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tlinx.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tlinx.org Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 20NKPVKl030115; Sun, 23 Jan 2022 12:25:33 -0800 Message-ID: <61EDB9C8.7000405@tlinx.org> Date: Sun, 23 Jan 2022 12:25:44 -0800 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: Ken Whitesell CC: The Cygwin Mailing List Subject: Re: Cygwin/X display scaling corrupting font display of typed characters; References: <02b8ba82-0a40-e9ea-c4e6-fe201097d957@comcast.net> <4f4d8d34-3e30-82fe-4be2-2926da2c1c6a@dronecode.org.uk> <61EAFAF1.9070405@tlinx.org> In-Reply-To: <61EAFAF1.9070405@tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2022 20:26:27 -0000 On 2022/01/21 10:26, L A Walsh wrote: ... To summarize, I am not sure that the original issue has anything to do with 2nd monitor, nor any changes in the Xorg-sources. In _my_ case it was a matter of how the Xserver was started, and what dpi settings it was started with. If server was started with incorrect dpi settings, it would cause problems with some Xclients having mangled or trunated characters at the bottom of their windows. For me, it was a matter of ensuring that my modified startX script was called instead of the stock script, as my modified script checks the windows DPI setting on startup. That said -- on Win10 it could be further complicated by having multiple monitors with different dpi settings. I seem to remember win10 having some provision for attaching a different DPI value to different monitors. That's likely to create a problem in 'X', since AFAIK, X hasn't been enhanced to allow different DPI values on different "screens".