[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Two (or much more) cursors bug debugged (simple test case)
From: |
Kenichi Handa |
Subject: |
Re: Two (or much more) cursors bug debugged (simple test case) |
Date: |
Wed, 28 Nov 2001 20:14:09 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
address@hidden (Pavel Janík) writes:
>> I can't reproduce it with my iso8859-2 font. Could you send
>> me the BDF file of courR12-ISO8859-2.pcf.gz?
> This file is generated with the following command from the file courR12.bdf
> in the XFree86's tree 4.1:
> perl ../../../fonts/util/ucs2any.pl courR12.bdf
> ../../../fonts/util/map-ISO8859-2 ISO8859-2
> Both of these font files are now on
> http://www.janik.cz/tmp/courR12.bdf
> http://www.janik.cz/tmp/courR12-ISO8859-2.pcf.gz
Thank you. With the above font, now I can reproduce the bug
both with 21.1.30 and 21.1.50, but not with 21.1.
address@hidden (Pavel Janík) writes:
> It is very suspicious, the same happens when you insert characters like ď,
> É, É but it does not when you insert one of ěščřžýáíé. It is also font
> dependent. When I'm using another font, nothing will happen (everything is
In that font, the topmost pixels of diacritical marks on t,
d, and E don't fit within the area of FONTBOUNDINGBOX, but
those on e, s, c, etc all fit within the area of
FONTBOUNDINGBOX. I believe this difference is the reason of
the above strange phenomenon.
Gerd, doesn't it ring a bell? As 21.1 works correctly with
that font, some of recent changes to xdisp.c or xterm.c
should be the reason of this bug.
---
Ken'ichi HANDA
address@hidden