From: Richard Stallman <rms@gnu.org>
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org, jas@extundo.com, ding@gnus.org
Subject: Re: MML charset tag regression
Date: Fri, 23 May 2003 08:05:06 -0400 [thread overview]
Message-ID: <E19JBII-0006RJ-Kk@fencepost.gnu.org> (raw)
In-Reply-To: <200305220058.JAA06943@etlken.m17n.org> (message from Kenichi Handa on Thu, 22 May 2003 09:58:22 +0900 (JST))
The current Emacs still don't unify Unicode and the other
legacy charsets (e.g. iso-8859-2, jisx0208, gb2312)
automatically. So, for instance, if iso-8859-2 characters
arrive at Emacs with UTF8_STRING, they are decoded into the
charset mule-unicode-0100-24ff and treated differently
(e.g. in searching) than the characters of the charset
iso-8859-2.
Can you draw up something for us to send to the GTK people
to request a specific feature that we need?
next prev parent reply other threads:[~2003-05-23 12:05 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 15:28 Simon Josefsson
2003-04-24 15:50 ` Jesper Harder
2003-04-24 21:15 ` Kai Großjohann
2003-04-24 23:04 ` Simon Josefsson
2003-04-25 0:11 ` Jesper Harder
2003-04-25 9:09 ` Manoj Srivastava
2003-04-25 0:03 ` Jesper Harder
2003-04-25 13:38 ` Kai Großjohann
2003-04-24 16:23 ` Kai Großjohann
2003-04-24 23:00 ` Simon Josefsson
2003-04-25 13:24 ` Kai Großjohann
2003-04-25 13:46 ` Simon Josefsson
2003-04-25 14:19 ` Jesper Harder
2003-04-25 15:43 ` Simon Josefsson
2003-04-25 16:31 ` Simon Josefsson
2003-04-25 19:39 ` Jesper Harder
2003-04-26 0:37 ` Simon Josefsson
2003-04-26 10:50 ` James H. Cloos Jr.
2003-04-28 11:58 ` Kenichi Handa
2003-04-28 12:43 ` Stephen J. Turnbull
2003-04-28 12:59 ` Kenichi Handa
2003-04-28 23:05 ` Simon Josefsson
2003-04-29 7:12 ` Stephen J. Turnbull
2003-04-29 5:38 ` Richard Stallman
2003-05-20 12:47 ` Kenichi Handa
2003-05-20 19:42 ` Jan D.
2003-05-21 15:31 ` Richard Stallman
2003-05-21 16:23 ` Jan D.
2003-05-22 0:58 ` Kenichi Handa
2003-05-22 16:25 ` Jan D.
2003-05-23 1:33 ` Kenichi Handa
2003-05-23 7:45 ` David Kastrup
2003-05-23 22:48 ` Richard Stallman
2003-05-23 23:41 ` Jan D.
2003-05-24 0:31 ` Miles Bader
2003-05-25 16:40 ` Dave Love
2003-05-25 18:01 ` Richard Stallman
2003-05-25 16:38 ` Dave Love
2003-05-25 17:25 ` Eli Zaretskii
2003-05-30 8:39 ` Kenichi Handa
2003-05-30 9:23 ` Dave Love
2003-05-30 11:36 ` Kenichi Handa
2003-06-04 22:01 ` Dave Love
2003-06-05 1:16 ` Kenichi Handa
2003-06-11 12:33 ` Stephen J. Turnbull
2003-06-01 15:40 ` Eli Zaretskii
2003-06-04 22:04 ` Dave Love
2003-06-06 10:55 ` Eli Zaretskii
2003-05-26 13:49 ` Richard Stallman
2003-05-30 9:28 ` Dave Love
2003-05-25 16:32 ` Dave Love
2003-05-25 19:14 ` Jan D.
2003-05-30 9:23 ` Dave Love
2003-05-23 12:05 ` Richard Stallman [this message]
2003-05-25 16:31 ` Dave Love
2003-05-30 12:03 ` Kenichi Handa
2003-06-04 21:52 ` Dave Love
2003-06-05 1:36 ` Kenichi Handa
2003-05-25 16:27 ` Dave Love
2003-05-24 0:51 ` Kenichi Handa
2003-05-23 12:03 ` Richard Stallman
2003-05-23 12:21 ` Kenichi Handa
2003-05-24 23:18 ` Richard Stallman
2003-06-13 8:37 ` Kenichi Handa
2003-06-15 15:59 ` Richard Stallman
2003-06-17 11:06 ` Kenichi Handa
2003-04-25 16:43 ` Michael Teichgräber
2003-04-25 17:14 ` Simon Josefsson
2003-04-25 18:14 ` Jesper Harder
2003-04-25 23:40 ` Michael Teichgräber
2003-04-26 0:32 ` Simon Josefsson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19JBII-0006RJ-Kk@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=jas@extundo.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.
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 NNTP newsgroup(s).