From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.mail.mew.general Subject: Re: [mew-int 01596] Re: windows 1252 Date: Fri, 14 Nov 2003 21:02:20 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200311141202.VAA07254@etlken.m17n.org> References: <87llqzuvaj.fsf@tleepslib.sk.tsukuba.ac.jp> <20031104.111334.60445673.kazu@iijlab.net> <200311070713.QAA24793@etlken.m17n.org> <20031110.161123.49979847.kazu@iijlab.net> <200311100742.QAA29290@etlken.m17n.org> <87ekwdilwx.fsf@tleepslib.sk.tsukuba.ac.jp> <200311130101.KAA04554@etlken.m17n.org> <87he18grg9.fsf@tleepslib.sk.tsukuba.ac.jp> <200311140257.LAA06613@etlken.m17n.org> <87vfpndwnl.fsf@tleepslib.sk.tsukuba.ac.jp> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1068812199 17775 80.91.224.253 (14 Nov 2003 12:16:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 Nov 2003 12:16:39 +0000 (UTC) Cc: mew-int@mew.org, kazu@iijlab.net, d.love@dl.ac.uk, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Nov 14 13:16:35 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AKcsN-00030G-00 for ; Fri, 14 Nov 2003 13:16:35 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AKcsM-00026F-00 for ; Fri, 14 Nov 2003 13:16:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AKdpK-0003JI-Vg for emacs-devel@quimby.gnus.org; Fri, 14 Nov 2003 08:17:30 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AKdiM-0007oo-AH for emacs-devel@gnu.org; Fri, 14 Nov 2003 08:10:18 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AKdhl-0007bx-T0 for emacs-devel@gnu.org; Fri, 14 Nov 2003 08:10:14 -0500 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AKdhj-0007bI-1U for emacs-devel@gnu.org; Fri, 14 Nov 2003 08:09:39 -0500 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by mx20.gnu.org with esmtp (Exim 4.24) id 1AKcfB-0003RI-6t for emacs-devel@gnu.org; Fri, 14 Nov 2003 07:02:57 -0500 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/3.7W-20010518204228) with ESMTP id hAEC2Kh00297; Fri, 14 Nov 2003 21:02:20 +0900 (JST) (envelope-from handa@m17n.org) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.6/3.7W-20010823150639) with ESMTP id hAEC2Ks20238; Fri, 14 Nov 2003 21:02:20 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id VAA07254; Fri, 14 Nov 2003 21:02:20 +0900 (JST) Original-To: stephen@xemacs.org In-reply-to: <87vfpndwnl.fsf@tleepslib.sk.tsukuba.ac.jp> (stephen@xemacs.org) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17819 gmane.mail.mew.general:548 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17819 In article <87vfpndwnl.fsf@tleepslib.sk.tsukuba.ac.jp>, "Stephen J. Turnbull" writes: > According to the standard, apps that implement compound text must > implement extended segments, and if you implement utf-8 anyway, this > would be trivial to support. But that doesn't mean they do. The ctext spec says: The name of the encoding should be registered with the X Consortium to avoid conflicts and ... But, the "registry" file included in X11R6.6 doesn't contain UTF-8 nor "ISO-8859-15". > Isn't UTF8_STRING also XFree86 only? I don't think so. The above "registry" file have this note at the tail. [134] In R6.6 X.Org is reserving the string UTF8_STRING for use as an ICCCM property type and selection target. The ICCCM spec will be updated in a future release to fully specify UTF8_STRING. --- Ken'ichi HANDA handa@m17n.org