[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#39997: marked as done (xfonts-cyrillic: fonts' bounding boxes incorrect)



Your message dated Tue, 20 Mar 2007 22:30:42 +0100
with message-id <46005282.20100@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xfonts-cyrillic
Version: 3.3.3.1-4
Severity: normal


At some point (I guess in upstream Xfree86-3.3.3)
some cyrillic fonts (I only checked several charcell fonts)
have increased character bounding boxes.
As a result 10x20 font actually have characters that take 11x20 cells,
12x24 will take 13x25 cells etc.
This causes the latin part cyrillic 10x20 look different from
regular 10x20 font, etc.
The characters themselves do not appear different,
just the spacing between them.
Even if there is a good reason for this change, at least the name
of the font should be consistent with its size.
To fix this FONTBOUNDINGBOX for the font and DWIDTH and possibly SWIDTH
have to be returned to the values they had before
(in slink the size was correct).


-- System Information
Debian Release: potato
Kernel Version: Linux eagle 2.2.10 #1 Sun Jun 20 14:02:34 EDT 1999 i586 unknown

Versions of the packages xfonts-cyrillic depends on:
ii  xbase-clients   3.3.3.1-9      miscellaneous X clients

--- End Message ---
--- Begin Message ---
Closing since the submitter didn't reply to the ping that have been sent
more than a month ago. If anybody ever reproduces this problem, feel
free to reopen.

Brice


--- End Message ---

Reply to: