On Sun, 21 Oct 2001, _ _ wrote:
> There is a very serious problem with many X
> applications that has been bugging me for some time,
> and I'd like to know what you all have to say on the
> matter and what is being done about it. The problem is
> that if you create a fixed-width BDF font and have
> glyphs wider than the font's DWIDTH then X
> applications will under many circumstances fail to
> delete the glyph entirely when you backspace over the
> character (if the glyph extends to the left outside
> the bounding box) or will fail to draw the glyph
> properly when you first type the character (if the
> glyph extends to the right of the bounding box).
>
> For example, the "A" glyph (as well as all the
> accented "A"s and the "AE" ISO8859-1 glyphs) of the
> font:
> -Adobe-Courier-Medium-R-Normal--14-100-100-100-M-90-ISO8859-1
^
The applications you refer to have only beed designed to be
used with what the X spec calls "CharCell" fonts and identifies
with the character "C" instead of "M" in the above marked position
of the XLFD.
ftp://ftp.x.org/pub/R6.4/xc/doc/hardcopy/XLFD/xlfd.PS.gz
Such applications probably should output a warning if a users
tries to use them with the wrong type of font.
X ships with plenty of CharCell fonts that will work fine with
these applications with relatively simple rendering mechanics.
I'd say it is not an XFree86 issue, nothing is planned to be fixed
here. Contact the maintainer of the relevant application if you really
want it to erase monospaced (M) fonts properly.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
