From: Emfox Zhou <EmfoxZhou@gmail.com>
Subject: Re: Emacs antialiasing in X
Date: Sun, 15 Jan 2006 11:53:06 +0800 [thread overview]
Message-ID: <87irsmkuzh.fsf@emfox.3322.org> (raw)
In-Reply-To: 87oe2eisl2.fsf@boost-consulting.com
David Abrahams <dave@boost-consulting.com> writes:
> 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
> emacs-unicode-2.
>
> Any advice on that score? What about images?
>
> When I see something like
>
> ("%" . "໌")
> ("'" . "ງ")
>
> in XFT_JHD_BRANCH and
>
> ("%" . "^[(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.
>
I think emacs-unicode-2 is more recent, and a patch against emacs-unicode-2
to add XFT support is better. as a notice, I have tested both of the branches,
and find the XFT branch could not deal properly with chinese, while the unicode
one seems ok for everything.
> Thanks,
> --
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
next prev parent reply other threads:[~2006-01-15 3:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 14:34 Emacs antialiasing in X Bill Atkins
2005-08-09 14:35 ` Jan D.
2005-12-20 20:17 ` David Abrahams
2005-12-21 5:30 ` Richard M. Stallman
2005-12-21 13:17 ` David Abrahams
2005-12-22 9:38 ` Jan D.
2006-01-12 22:56 ` David Abrahams
2006-01-13 8:49 ` Jan D.
2006-01-13 21:32 ` David Abrahams
2006-01-14 18:15 ` David Abrahams
2006-01-15 3:53 ` Emfox Zhou [this message]
2006-01-15 8:31 ` Jan Djärv
2006-01-15 16:13 ` David Abrahams
2006-01-16 0:58 ` Kenichi Handa
2006-01-16 2:09 ` David Abrahams
2006-01-16 2:35 ` Kenichi Handa
2006-01-16 3:02 ` David Abrahams
2006-01-16 4:07 ` Kenichi Handa
2006-01-16 13:32 ` David Abrahams
2006-01-16 23:45 ` Lőrentey Károly
2006-01-16 8:14 ` Jan D.
2006-01-16 9:45 ` Miles Bader
2006-01-16 13:38 ` David Abrahams
2006-01-16 13:53 ` Jan D.
2006-01-16 16:31 ` David Abrahams
2006-01-16 19:04 ` Jan D.
2006-01-16 20:17 ` David Abrahams
2006-01-16 22:48 ` Miles Bader
2006-01-17 8:34 ` Jan D.
2006-01-17 15:20 ` David Abrahams
2006-01-18 0:41 ` Miles Bader
2006-01-20 1:51 ` David Abrahams
2006-01-28 13:23 ` David Abrahams
2006-01-17 15:19 ` David Abrahams
2006-01-16 16:51 ` Stefan Monnier
2006-01-16 18:01 ` David Abrahams
2006-01-16 15:57 ` Emfox Zhou
2006-01-16 4:28 ` Stefan Monnier
2006-01-16 13:32 ` David Abrahams
2006-01-16 8:52 ` YAMAMOTO Mitsuharu
2006-01-15 8:28 ` Jan Djärv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87irsmkuzh.fsf@emfox.3322.org \
--to=emfoxzhou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).