[Top][All Lists]

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

Re: Emacs antialiasing in X

From: David Abrahams
Subject: Re: Emacs antialiasing in X
Date: Sat, 14 Jan 2006 13:15:37 -0500
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

David Abrahams <address@hidden> writes:

> "Jan D." <address@hidden> writes:
>>>> 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?"
>> Unicode refers to the Emacs unicode branch.  So it means integrate
>> those two branches.
> meaning "emacs-unicode-2" and "XFT_JHD_BRANCH?"

I've started trying to merge these two, and I have a few questions.
It's pretty tough to figure out what to do about ChangeLog, NEWS, etc.
There are many differences, it isn't clear to me which branch is more
current, and I'm not so involved with emacs development that I can
make judgements about each item.  Certainly XFT_JHD_BRANCH seems to
contain several cleanups and corrections to text present in

Any advice on that score?  What about images?

When I see something like

    ("%" . "໌")
    ("'" . "ງ")


    ("%" . "(1l(B")
    ("'" . "(1'(B")

in emacs-unicode-2, do I want to keep the latter, since the
character representation is changing?

Also, would it be better to come up with a patch against
emacs-unicode-2 that adds XFT support, or vice-versa?  I am inclined
towards the former.

Dave Abrahams
Boost Consulting

reply via email to

[Prev in Thread] Current Thread [Next in Thread]