From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: James Cloos Newsgroups: gmane.emacs.devel Subject: Re: X11 Compound Text vs ISO 2022 Date: Thu, 29 Jul 2010 11:51:21 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1280419838 3109 80.91.229.12 (29 Jul 2010 16:10:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Jul 2010 16:10:38 +0000 (UTC) Cc: david@harpegolden.net, emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 29 18:10:34 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OeVgd-0003y2-Rt for ged-emacs-devel@m.gmane.org; Thu, 29 Jul 2010 18:10:29 +0200 Original-Received: from localhost ([127.0.0.1]:45637 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OeVgZ-0002xT-Md for ged-emacs-devel@m.gmane.org; Thu, 29 Jul 2010 12:10:19 -0400 Original-Received: from [140.186.70.92] (port=58483 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OeVgT-0002tN-8G for emacs-devel@gnu.org; Thu, 29 Jul 2010 12:10:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OeVgL-0007Rk-P3 for emacs-devel@gnu.org; Thu, 29 Jul 2010 12:10:09 -0400 Original-Received: from eagle.jhcloos.com ([207.210.242.212]:60944) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OeVgL-0007R9-KO for emacs-devel@gnu.org; Thu, 29 Jul 2010 12:10:05 -0400 Original-Received: by eagle.jhcloos.com (Postfix, from userid 10) id D96FC403B5; Thu, 29 Jul 2010 16:09:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com; s=eagle; t=1280419803; bh=TsLONvIdOql0nvY73FQB4qC7mPfZewQnOZwVSVaj/tg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=X74sff0pg/X2OgQMZH1Sx7fXpXTCjPlzoQAK/PVeNxIfj0bNreQEwew1Gw6+b1A5P 7vZA12RQxhdWCXgI2RzwWbB6Rcd4Odkt4OyB7jTJEiTN1yvou0Cpuq6s6VPQO2ENYQ n1WanUZwXE4KIKV1n3yD+VgjSq3EmrCCwvOqml9M= Original-Received: from carbon.jhcloos.org (localhost [127.0.0.1]) by carbon.jhcloos.org (Postfix) with ESMTP id 9826A1CE016; Thu, 29 Jul 2010 15:51:21 +0000 (UTC) In-Reply-To: (Kenichi Handa's message of "Thu, 29 Jul 2010 21:36:31 +0900") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAI1J REFUOE+lU9ESgCAIg64P1y+ngUdxhl5H8wFbbM0OmUiEhKkCYaZThXCo6KE5sCbA1DDX3genvO4d eBQgEMaM5qy6uWk4SfBYfdu9jvBN9nSVDOKRtwb+I3epboOsOX5pZbJNsBJFvmQQ05YMfieIBnYX FK2N6dOawd97r/e8RjkTLzmMsiVgrAoEugtviCM3v2WzjgAAAABJRU5ErkJggg== Copyright: Copyright 2009 James Cloos OpenPGP: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 Original-Lines: 58 X-Hashcash: 1:30:100729:handa@m17n.org::WZvm12mHAs0RUZrc:00N0fwA X-Hashcash: 1:30:100729:emacs-devel@gnu.org::4NeUFwgm1AUXG9zd:00000000000000000000000000000000000000000PPVqu X-Hashcash: 1:30:100729:david@harpegolden.net::jCUgRLWWgdTmUreX:000000000000000000000000000000000000000CuNQ6 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:127968 Archived-At: >>>>> "KH" == Kenichi Handa writes: KH> Very sorry for the late response on this matter. That is OK. KH> I added more KH> character sets to it for cut&paste between two running KH> Emacses. Understood. And, now that you have mentioned it, I think I even remember (vaguely) a post or a discussion about it from back then. KH> It's fairly easy to limit charsets of ctext. But, I care KH> the backward compatibility. As ctext is the only coding KH> system that is compatible with iso-8859-1 and can encode KH> many other character sets, there will be old users who still KH> uses it for file/process encodings. I was not aware of that. KH> And, anyway ctext is not used for selection, I has to be used for X selection, yes? How else could X selection of text work than using data tagged with X's STRING, COMPOUND_TEXT or UTF8_STRING atoms? KH> I'd rather just document that ctext is not fully compatible X's KH> COMPOUND_TEXT spec, but is the extended vesion. KH> For WM_NAME, etc, yes, we should use ctext-with-extensions, KH> and as ctext-with-extensions is not intended to be used KH> directly by users, I think it won't cause actual problems KH> even if we change it so that more characters are encoded KH> using UTF8-extended-segment. So, I'll work on it soon. ctext-with-extesnions already supports the UTF8 extended segment; the bug is that it uses JISX 0213 for some characters. The earlier JISX versions (0201, 0208 and 0212) are OK, but 0213 is not. KH> The only problem with ctext-with-extensions is that it is KH> now implemented by Elisp, and thus it may cause GC. I'm not KH> sure it is safe to call Lisp at the place we convert WM_NAME KH> etc. If it is not safe, I'll implement KH> ctext-with-extensions in C. the WM_NAME code already has to gc protect to do the conversion to utf8 for the gtk call (when compiled for gtk) and the new code to set the UTF8_STRING _NET_WM_NAME and _NET_WM_ICON_NAME properties; I presume it could do a conversion to ctext-with-extensions within that same protect? Then it just needs to prefer utf8 over jisx0213. Thanks for looking at it. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6