GNU bug report logs - #15138
Font rendering error on OSX

Previous Next

Full log

Message #67 received at 15138-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Kenichi Handa <handa <at> gnu.org>
Cc: 15138-done <at> debbugs.gnu.org, darren.hoo <at> gmail.com
Subject: Re: bug#15138: revno: 114089 change causes cjk characters not shown
 correctly
Date: Thu, 5 Sep 2013 18:34:19 +0200

Hello.

5 sep 2013 kl. 15:49 skrev Kenichi Handa <handa <at> gnu.org>:

> In article <7FEF1248-81A6-4E06-8F08-29A02CE72E00 <at> swipnet.se>, Jan Djärv <jan.h.d <at> swipnet.se> writes:
> 
>> Good, closing.
> 
> I have another question about this change.
> 
>      /* Fonts often have characters in other scripts, like symbol, even if they
>         don't match script: symbol.  So check if the character is present
>         in the current face first.  Only enable for NS for now, but should
>         perhaps be general?  */
>      Lisp_Object font_object;
>      XSETFONT (font_object, face->font);
>      if (font_has_char (f, font_object, c)) return face->id;
> 
> With it, face->font may vary depending on the preceding
> character.  So if you have these lines:
>  abc•
>  あいう•
> the two "•"s will be displayed by different fonts.  Isn't it
> better to try the font selected for ASCII as this:
> 
>      XSETFONT (font_object, face->ascii_face->font);


I don't know, I never had that situation.  I guess if the goal is to show same glyphs, ascii_face->font is a better choice.  But if it is to have a consistent look with the surrounding text, it it not.

Consider a buffer where only  あいう• is entered.  I would assume the current font would be a better choice in this case.

	Jan D.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.