Thanks for forwarding the report!

Yes, I this issue is well-known, and I'm working hard on a solution.

The "bug" being reported is due to the fixed 15% spacing I introduced
in all faces in order to stop the chopping of various high and low
characters, rendering much text unreadable.

It was a choice: What's worse?  What's the purpose of FreeFont?  How
much time do I have?

I think it is reasonable for most glyphs to live between the stated
vertical bounds of the font.  For the monospace font especially, such
a limitation is more important than aesthetic balance.
I have now forced that limitation now on the Roman monospace face and
am working on the others.  But it takes some time.

As to the ideal box-drawing in an xterm, there are various
complications, and cases of smoke and mirrors, on the part of xterm
implementations and console fonts.  I'm not sure if this is a goal I
want to pursue very far, because I think it is illusory.

But I have already improved it a lot, and mean to do more.

(I'll repeat this in a reply to the Debian bug report.)



On Tue, May 6, 2008 at 10:38 PM, Davide Viti <[EMAIL PROTECTED]> wrote:
> Hi Christian,
>
>
>
>  On Tue, May 06, 2008 at 07:11:05AM +0200, Christian Perrier wrote:
>  > Quoting Davide Viti ([EMAIL PROTECTED]):
>  > > Hi Steve,
>  > > just wanted to let you know about this bugreport recently sent to the 
> Debian
>  > > BTS
>  >
>  >
>  > Why not report it to upstream's BTS ? That would allow "linking" both
>  > bugs as, IIRC, upstream BTS is supported by our bts-link utility.
>  >
>
>  done it (see [1]) and set the (hopefully) proper forwarded tag
>  on the Debian BTS
>
>  regards,
>  Davide
>
>  [1] https://savannah.gnu.org/bugs/?23189
>


Reply via email to