unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cheng Gao <chenggao@gmail.com>
Subject: Re: Successful build of emacs-unicode-2 under Windows with MinGW
Date: Tue, 21 Sep 2004 14:34:53 +0800	[thread overview]
Message-ID: <u8yb4m8oi.fsf@gmail.com> (raw)
In-Reply-To: buofz5cgohe.fsf@mctpc71.ucom.lsi.nec.co.jp

,----
| Probably not very.  It's more important to test the trunk, as it will be
| released much sooner.
| 
| [If you _want_ to use the unicode branch for some reason though, I do
| regularly sync it with the trunk, so general bug reports will probably
| still be pretty relevant to the trunk version.]
`----

One of the reason I test emacs-unicode-2 is I know you sync it with
trunk frequently. I keep my eye on emacs cvs log.

In fact from my purpose of using emacs, I dont have special reason to
use it. I just wanna test it.

I am from China mainland. From my reading, I know emacs-unicode-2
doesnot support CJK very well. At the same time, emacs trunk has very
good support of CJK.

After my short time test, at least I found there is interesting thing
for me to play with. Unicode-2 branch adds chinese-gbk and chinese-18030
charsets. There does exist some articles in some groups where messages
are posted in non-gb2312 charsets. Though I can use gb2312 to view them,
some characters can not be displayed (coz they are out of scope of
gb2312).
My experience with unicode-2 branch is too few. But since unicode-2 will
be base of next version, I think it's interesting to run it in parallel
with trunk version. After all, if you keep shared files (for example
files in site-lisp) byte-compiled with trunk version, it's very easy to
let them coexist.

CG

-- 
山中何所有
岭上多白云
只可自怡悦
不堪持寄君

  reply	other threads:[~2004-09-21  6:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20  6:42 Successful build of emacs-unicode-2 under Windows with MinGW Cheng Gao
2004-09-20 17:24 ` Cheng Gao
2004-09-21  5:37   ` Dhruva Krishnamurthy
2004-09-21  5:50     ` Miles Bader
2004-09-21  6:34       ` Cheng Gao [this message]
2004-09-22 13:59       ` Richard Stallman
2004-09-22 16:14         ` zrr
2004-09-23  4:22         ` Dhruva Krishnamurthy
2004-09-23 16:44           ` Richard Stallman
2004-09-24  6:21             ` Dhruva Krishnamurthy
2004-09-24  7:24               ` Cheng Gao
2004-09-24  7:43               ` Jason Rumney
2004-09-27  5:07                 ` Dhruva Krishnamurthy
2004-09-27  9:22                   ` Cheng Gao
2004-09-27  9:41                     ` Dhruva Krishnamurthy
2004-09-27  9:57                       ` Jason Rumney
2004-09-27  9:59                         ` Dhruva Krishnamurthy
2004-09-27 10:38                       ` Dhruva Krishnamurthy
2004-09-27 10:41                       ` Miles Bader
2004-09-27 11:04                       ` Cheng Gao
2004-09-28  0:11                   ` Paul Pogonyshev
2004-09-27 21:41                     ` Jason Rumney
2004-09-23  9:51         ` Cheng Gao
2004-09-23 10:07           ` Miles Bader
2004-09-21  8:56   ` Dhruva Krishnamurthy
2004-09-21  9:18     ` Cheng Gao

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=u8yb4m8oi.fsf@gmail.com \
    --to=chenggao@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).