unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: tats@iris.ne.jp,  emacs-devel@gnu.org
Subject: [mew-int 00832] Re: How to add some more charsets to mew?
Date: 22 Apr 2002 12:40:31 +0100	[thread overview]
Message-ID: <rzqsn5oq7v4.fsf@djlvig.dl.ac.uk> (raw)

I got directed to this and am puzzled.

Werner LEMBERG <wl@gnu.org> writes:

> > > > On GNU Emacs 21.2, Mule-UCS 0.84 is very slow.  Debian's mule-ucs
> > > > 0.84-11 has fixed this problem.  Debian's mule-ucs is available at:

I doubt it's any slower than before, apart from loading un-define.
What's the evidence?  The only relevant patches in Debian 0.84-11,
which appears to be the current package version, are one of mine and
one of Toby Speight's which probably slows decoding if anything.
(It's unfortunate for various reasons that the origin of patches
doesn't get recorded.)

> > > > 
> > > >   http://packages.debian.org/mule-ucs
> > > 
> > > This is interesting, since some people already tried to debug that
> > > without success.  Can you give more details, please?
> > 
> > Dave Love had some success. He posted his patches to
> > gnu.emacs.sources and the mule@m17n.org mailing list on 29 March.
> > You even followed that up with a comment about Mule-UCS no longer
> > seeming to be maintained.
> 
> Dave said he had *some* success.

I don't know what that refers to.  I explained the problem on
emacs-devel (I think) when it was first raised, as well as when I
posted the patch.  I made the bug fix that avoided Mule-UCS-induced
lossage.  You could have more success with the loading speed by not
defining any of the coding systems you don't use.  If that's not good
enough, handa had a suggestion for a different change to
`register-char-codings', but I seem to remember it was somewhat
incompatible.

> The message above says that the problem has been fixed.  This is not
> the same.

If there's another problem that someone can explain, I might be able
to do something about it.  (himi isn't responding currently.)
Otherwise, perhaps it's just a case of things working better without
my name on. :-/.

Non-CJK users would probably do better for simply editing Unicode to
use the ucs-tables.el and modified utf-8.el I advertised recently.
CJK users could contribute to improving its CJK support, but that
requires the CCL patch to the Emacs core.

             reply	other threads:[~2002-04-22 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 11:40 Dave Love [this message]
2002-04-22 16:50 ` [mew-int 00832] Re: How to add some more charsets to mew? Werner LEMBERG
2002-04-29 22:31   ` Dave Love
     [not found] <20020413.193345.99454893.vostry@zoom-int.cz>
     [not found] ` <20020414.235532.125902697.05@tats.iris.ne.jp>
2002-04-15 10:12   ` Werner LEMBERG
2002-04-15 21:17     ` Jason Rumney
2002-04-16 13:17       ` Werner LEMBERG
2002-04-16 20:17       ` Richard Stallman
2002-04-16 21:28         ` Jason Rumney

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=rzqsn5oq7v4.fsf@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=tats@iris.ne.jp \
    /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).