From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David.Kastrup@t-online.de (David Kastrup) Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: MML charset tag regression Date: 23 May 2003 09:45:06 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <0F223D16-8C72-11D7-8F50-00039363E640@swipnet.se> <200305230133.KAA08801@etlken.m17n.org> Reply-To: dak@gnu.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1053676459 31142 80.91.224.249 (23 May 2003 07:54:19 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 23 May 2003 07:54:19 +0000 (UTC) Cc: jas@extundo.com Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri May 23 09:54:11 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19J7NS-00085P-00 for ; Fri, 23 May 2003 09:54:10 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19J7Z7-0007HK-00 for ; Fri, 23 May 2003 10:06:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19J7LF-0001z5-GW for emacs-devel@quimby.gnus.org; Fri, 23 May 2003 03:51:53 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19J7Ib-0000HX-Sq for emacs-devel@gnu.org; Fri, 23 May 2003 03:49:09 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19J7Hf-0008WL-D9 for emacs-devel@gnu.org; Fri, 23 May 2003 03:48:12 -0400 Original-Received: from mailout08.sul.t-online.com ([194.25.134.20]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19J7FN-0007kZ-Sy; Fri, 23 May 2003 03:45:50 -0400 Original-Received: from fwd02.sul.t-online.de by mailout08.sul.t-online.com with smtp id 19J7F7-0006DV-0B; Fri, 23 May 2003 09:45:33 +0200 Original-Received: from localhost.localdomain (520018396234-0001@[62.226.11.153]) by fwd02.sul.t-online.com with esmtp id 19J7Es-1ulCamC; Fri, 23 May 2003 09:45:18 +0200 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h4N7jCIp002542; Fri, 23 May 2003 09:45:13 +0200 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h4N7j6xR002538; Fri, 23 May 2003 09:45:06 +0200 Original-To: Kenichi Handa In-Reply-To: <200305230133.KAA08801@etlken.m17n.org> Original-Lines: 48 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Sender: 520018396234-0001@t-dialin.net Original-cc: ding@gnus.org Original-cc: rms@gnu.org Original-cc: jan.h.d@swipnet.se Original-cc: emacs-devel@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:14118 gmane.emacs.gnus.general:52797 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:14118 Kenichi Handa writes: > In article <0F223D16-8C72-11D7-8F50-00039363E640@swipnet.se>, "Jan D." writes: > >> 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. > > > Okay, that explains it. But playing the devils advocate a > > bit, does this not simply point out a problem with Emacs, > > not GTK? > > It's surely Emacs' problem that the same iso-8859-2 > character is represented in two ways internally. But, > incomplete support of COMPOUND_TEXT is GTK's (or some other > X client's) problem. As far as they react upon the request > of COMPOUND_TEXT, it should send the correct data (without > cutting off unsupported characters or replacing them with > '?' silenty). Otherwise, it shouldn't react upon that > request. Right. I have found it very annoying to find that I can cut&paste unicode strings from Emacs to galeon, but get only ? when doing it the other way round. > > If UTF8_STRING is the recommended thing to use, changing GTK would > > not help much, as there are other X toolkits out there (Qt, Motif, > > and so on), that will start to use UTF8_STRING also (Qt already > > does)? Isn't this an argument for getting the Unicode Emacs > > branch released, or unify charsets? > > Of course, with Emacs-unicode, there's no such problem, and I want > to release it as soon as possible. What's the state of it? Am I right in assuming that we would first be releasing a full-featured 21.4 (or, if really necessary, another bug fix 21.4 followed by a full 21.5)? In that case, probably another bug fix 21.xx series would have to follow, and one would probably make something like 22.0 the goal for a Unicode Emacs, with probably some alpha versions before that? Sorry to be using the "R" word here. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum