X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=CtWs7tbrrkOqw0gq gK4AC1XYPzePE9ujtBWzNDUdRY6kFzYpJNGJlK/+CkmBT9TwP4DIC6+LYWvLRCen ZLV7JjGeyWQ/XFHRNyvmX7+febsx89e83GvUnM6EMRTPOG+JkrR3fIV3i345x+Il pChg28lM+WlkLGxxj4qO8qMeIwE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=AMgPXLv2SBWUMD9a7K+Uzx KZb0U=; b=MhE25hzOu9H0S1FKIXq0tGhu/FMA6LoR8b+2wlz6Bv+EzstaolKmKe 0J0dnulCWnsuIT9MmoUzX6NtAdluzmPNAAZdkN/9owa2mRHiYQE/vWML/UlHGTMg bUPV79vmWsADX02RjNUyM86fvgyae+7YPDUNIhXYUqQ9BG6CTA8Mo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,LIKELY_SPAM_SUBJECT,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock01.mail.cornell.edu X-CornellRouted: This message has been Routed already. Message-ID: <5411C446.3010005@cornell.edu> Date: Thu, 11 Sep 2014 11:48:22 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Daniel Colascione Subject: Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs References: <868um0dgfp DOT fsf AT somewhere DOT org> <54108F3C DOT 5010103 AT cornell DOT edu> <86a966bn5v DOT fsf AT somewhere DOT org> <87bnqmy0b4 DOT fsf AT Rainer DOT invalid> <867g1atq2j DOT fsf AT somewhere DOT org> In-Reply-To: <867g1atq2j.fsf@somewhere.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 9/11/2014 6:21 AM, Sebastien Vauban wrote: > Achim Gratz wrote: >> Both fonts you use as an example exist in multiple versions with >> differing UTF-8 support. If they don't have that glyph (which is >> likely, given the results you report), then Emacs would try to get it >> from another font with the same dimensions (I don't know if mintty >> does font substitution and if so, how) and the results very much >> depend on the font maps used. > > I didn't know about that mechanism. But, then, the question is: why does > Windows Emacs find a substitution, and not Cygwin Emacs (for the same > font)? It's clear that I was wrong when I said that this doesn't seem to have anything to do with emacs. The problem might be that the Cygwin-w32 build of emacs is a relatively recent invention and may still need some tweaking to get all the GUI features working properly. If you or someone else is motivated enough, I'm sure it would be possible to figure out how the Windows build finds a glyph for characters that don't have one in the chosen font, and to port that to the Cygwin-w32 build. I'm copying Daniel Colascione, the author of that build, to see if he has any comments. Dan, the thread starts here: https://cygwin.com/ml/cygwin/2014-09/msg00052.html Ken -- 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