Re: Emacs antialiasing in X

[David Abrahams]

"Jan D." <address@hidden> writes:

>> That was the point of my posting.  The post I responded to seemed to
>> be from the initiator of the branch, and he seemed to have specific
>> plans.  I'm not volunteering to lead the effort, but I will help with
>> the programming.
>
> Well, the plan is to not do anything yet :-).  

I also thought the plan was to eventually use cairo:

  http://article.gmane.org/gmane.emacs.devel/34434/match=antialiased

> If you feel that you
> can contribute time and effort, please go right ahead and check in
> whatever changes you find time to do.  

I don't believe I've got commit privileges :-)

> The areas in most need of work is font selection, that is not
> handeled correctly.  The way Emacs faces specify fonts and how they
> map to X fonts needs to be handeled in a way that is appropriate for
> antialiased fonts as well.  Currently Emacs faces specify slant,
> size and such and then translate to/from XLFD (the
> -courier-normal-*-12-*-*- notation).  This is not appropriate for
> antialiased fonts.  

How so?

> The calculation of the size of the frame (lines => pixels) does not
> seem to be correct either, I suspect the calculation uses the wrong
> font.

Have any pointers into the code?

> People has reported various redrawing problems also.
>
> And then there is the whole i18n problem.  Specifically, Xft wants
> unicode characters, but Emacs has its own internal (Mule)
> representation.  I think we must integrate XFT and Unicode before
> this can be sorted out correctly.

What do you mean by "integrate XFT and Unicode?"  You just
said Xft already wants unicode characters, so I assume they're as
integrated as they're going to get.  Maybe you mean "integrate Mule
and Unicode?"

Thanks.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com