From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: font-backend branch Date: Fri, 02 May 2008 21:16:41 +0900 Message-ID: References: <48190539.4010508@gnu.org> <481AFB40.1050205@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1209730628 5034 80.91.229.12 (2 May 2008 12:17:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 May 2008 12:17:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 02 14:17:43 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JruCq-0005bx-Va for ged-emacs-devel@m.gmane.org; Fri, 02 May 2008 14:17:41 +0200 Original-Received: from localhost ([127.0.0.1]:33884 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JruC9-0001np-NC for ged-emacs-devel@m.gmane.org; Fri, 02 May 2008 08:16:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JruC6-0001nk-21 for emacs-devel@gnu.org; Fri, 02 May 2008 08:16:54 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JruC3-0001nQ-K9 for emacs-devel@gnu.org; Fri, 02 May 2008 08:16:52 -0400 Original-Received: from [199.232.76.173] (port=49914 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JruC3-0001nN-Gd for emacs-devel@gnu.org; Fri, 02 May 2008 08:16:51 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JruBy-00065T-Au; Fri, 02 May 2008 08:16:46 -0400 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id m42CGgix010643; Fri, 2 May 2008 21:16:42 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp4.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id m42CGgKY026243; Fri, 2 May 2008 21:16:42 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id m42CGgGY015133; Fri, 2 May 2008 21:16:42 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1JruBt-0000Oi-W5; Fri, 02 May 2008 21:16:42 +0900 In-reply-to: <481AFB40.1050205@gnu.org> (message from Jason Rumney on Fri, 02 May 2008 12:30:08 +0100) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96321 Archived-At: In article <481AFB40.1050205@gnu.org>, Jason Rumney writes: > At which point is the build failing now? The same point as I wrote before. > It might simplify things to > copy your lisp directory from another plaform to avoid the need to > bootstrap, as that is where most subtle problems with Windows build > environments come up. Ah, that's a good idea. I've just done it, and now I have running Emacs on Windows. > I think I have fixed the font selection problem, by adding code to copy > the entries from font_entity to the new font_object in > w32font_open_internal. Ah, thank you for finding out that. I have forgotten to do that when I modified w32font.c. :-( [...] > > After that, there is always a garbage character following the boxes > > that indicate a missing font. If the cursor is anywhere on the line, > > then the garbage character changes, at the same rate the cursor is > > blinking at. > This is fixed by your change to w32term.c. That's good. > Now only the initial display > corruption is a problem, so I will debug that and see if I can > differentiate between errors that mean the font cannot use glyph codes, > and other errors that only apply to specific characters, which we could > indicate by treating that character as missing in the font. Thank you. By the way, could you make the `open' function of each font-driver to set XLFD name in font->props[FONT_NAME_INDEX]. Currently only the family name is set there, but it seems that some people has a code that expects XLFD name in the return value of (frame-parameter nil 'font). --- Kenichi Handa handa@ni.aist.go.jp