From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: MML charset tag regression Date: Tue, 29 Apr 2003 01:38:56 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <8465p3kgpl.fsf@lucy.is.informatik.uni-duisburg.de> <84bryuogke.fsf@lucy.is.informatik.uni-duisburg.de> <200304281158.UAA10974@etlken.m17n.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1051594918 30572 80.91.224.249 (29 Apr 2003 05:41:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 29 Apr 2003 05:41:58 +0000 (UTC) Cc: jas@extundo.com Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Apr 29 07:41:55 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 19ANsJ-0007wl-00 for ; Tue, 29 Apr 2003 07:41:55 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19AO0o-0005Hz-00 for ; Tue, 29 Apr 2003 07:50:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19ANt9-0003Rf-0C for emacs-devel@quimby.gnus.org; Tue, 29 Apr 2003 01:42:47 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19ANqj-0002WF-00 for emacs-devel@gnu.org; Tue, 29 Apr 2003 01:40:17 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19ANqL-00026E-00 for emacs-devel@gnu.org; Tue, 29 Apr 2003 01:39:55 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19ANpU-0001gC-00 for emacs-devel@gnu.org; Tue, 29 Apr 2003 01:39:00 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.10) id 19ANpQ-0003Pb-00; Tue, 29 Apr 2003 01:38:56 -0400 Original-To: Kenichi Handa In-reply-to: <200304281158.UAA10974@etlken.m17n.org> (message from Kenichi Handa on Mon, 28 Apr 2003 20:58:34 +0900 (JST)) Original-cc: ding@gnus.org 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:13539 gmane.emacs.gnus.general:51937 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:13539 Recently, many gtk clients start supporting UTF8_STRING without making COMPOUND_TEXT support better. It may cause no problem between gtk clients because they will request only the type UTF8_STING. But, it's a too shortsighted manner. :-( Is this an issue I should raise with the GTK developers? Could they, should they, do something to encourage app developers to handle COMPOUND_TEXT properly? Perhaps, we should make Emacs to request UTF8_STRING at first if the locale is UTF8, and if that request fails, request COMPOUND_TEXT. If we do this, it should be controlled by a Lisp variable, not by the locale. Perhaps the Lisp variable could default based on the locale. Is there a reason not to do this unconditionally, always?