Re: (re)display problems after font backend merge

[Stephen Berman <Stephen.Berman@gmx.net>]

On Fri, 16 May 2008 09:57:42 +0900 Kenichi Handa <handa@m17n.org> wrote:

> In article <87fxsjmmo2.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
>
>> Since Kenichi Handa's font backend merge yesterday I see different, and
>> at least partly buggy, display and redisplay effects.  This shows up
>> clearly in some of my customizations, in particular of the mode line and
>> the Gnus Summary buffer.  The following screen shots show the
>> differences; the top image is post-merge, the bottom pre-merge:
>
>> [2 Post-merge display <image/png (base64)>]
>
>> [3 Pre-merge display <image/png (base64)>]
>
>> [4  <text/plain (7bit)>]
>
>> Here is a description of the differences I see:
>
>> - In the post-merge image, the underlining I use in the mode line is
>> broken, as is the underlining of the current article in the Gnus Summary
>> buffer, and the latter underlining touches the bottom of the characters
>> in the post-merge image, while there is a (IMO more pleasing) space in
>> the pre-merge display.
>
> Please show me how you customize Gnus, 

(setq gnus-summary-line-format "%U%R%z%((%4L) %-20,20f \x2502 %*%B%s%)\n"
      gnus-sum-thread-tree-root "\x25b6 "
      gnus-sum-thread-tree-false-root "\x25b7 "
      gnus-sum-thread-tree-vertical "\x2502 "
      gnus-sum-thread-tree-leaf-with-other "\x251c\x2500\x25b8 ..."
      gnus-sum-thread-tree-single-leaf "\x2570\x2500\x25b8 ...")

>                                        and exactly which
> font is used in the Gnus summary buffer by C-u C-x =.

For ascii:

-unknown-DejaVu Sans Mono-normal-normal-normal-*-12-*-*-*-m-0-iso8859-1

For the non-ascii characters:

-gnu-unifont-medium-r-normal--16-160-75-75-p-80-iso10646-1

This is post-merge, in the pre-merge buffer, the corresponding line of
the character description for both ascii and non-ascii characters is
this:

dejavu sans mono:pixelsize=12:foundry=unknown:weight=medium:slant=r:width=normal

>> - The fringe arrow in the Summary buffer is redisplayed in the mode
>> line.
>
> This is very strange.  The font-backend merge should not
> touch fringe displaying.

I cannot reproduce this; maybe it was a random redisplay glitch, which I
just happened to catch in the screen shot.  (In contrast, the broken
underlining persists.)

>> - The character size in the mode line is larger in the post-merge image
>> than in the pre-merge image (in both it is font family Helvetica).
>
>> - The appearance of the non-ascii characters I use for threading and
>> separation in the Summary buffer differs; in particular, the separator
>> forms a broken vertical line in the post-merge buffer, while it is a
>> continuous vertical line in the pre-merge buffer (except for the line
>> containing the Indic characters, which is also misaligned in both
>> images).
>
> Please do C-u C-x = on that vertical line to see which font
> is used in both version.

post-merge:

        character: │ (9474, #o22402, #x2502)
preferred charset: unicode (Unicode (ISO10646))
       code point: 0x2502
           syntax: _ 	which means: symbol
         category: c:Chinese h:Korean j:Japanese
      buffer code: #xE2 #x94 #x82
        file code: #xE2 #x94 #x82 (encoded by coding system utf-8-unix)
          display: by this font (glyph code)
     -gnu-unifont-medium-r-normal--16-160-75-75-p-80-iso10646-1 (#x2502)

pre-merge:

        character: │ (9474, #o22402, #x2502)
preferred charset: unicode (Unicode (ISO10646))
       code point: 0x2502
           syntax: _ 	which means: symbol
         category: c:Chinese h:Korean j:Japanese
      buffer code: #xE2 #x94 #x82
        file code: #xE2 #x94 #x82 (encoded by coding system utf-8-unix)
          display: by this font (glyph code)
     dejavu sans mono:pixelsize=12:foundry=unknown:weight=medium:slant=r:width=normal (#x858)


Steve Berman