From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa Newsgroups: gmane.emacs.help Subject: Re: emacs 22 on win XP, selection-coding-system, and copy & paste outside emacs Date: Thu, 3 Aug 2006 13:26:14 +0200 Message-ID: References: <1154597197.957129.171380@b28g2000cwb.googlegroups.com> <1154599512.945358.168520@h48g2000cwc.googlegroups.com> <1154600309.942065.263290@i42g2000cwa.googlegroups.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1154604410 12234 80.91.229.2 (3 Aug 2006 11:26:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 3 Aug 2006 11:26:50 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Aug 03 13:26:48 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G8bLX-0004S6-Px for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Aug 2006 13:26:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G8bLW-0000X3-Sn for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Aug 2006 07:26:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G8bLM-0000Wy-O4 for help-gnu-emacs@gnu.org; Thu, 03 Aug 2006 07:26:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G8bLJ-0000WK-2D for help-gnu-emacs@gnu.org; Thu, 03 Aug 2006 07:26:24 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G8bLI-0000WH-S6 for help-gnu-emacs@gnu.org; Thu, 03 Aug 2006 07:26:20 -0400 Original-Received: from [217.72.192.227] (helo=fmmailgate02.web.de) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G8bOc-0005p9-2q for help-gnu-emacs@gnu.org; Thu, 03 Aug 2006 07:29:46 -0400 Original-Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate02.web.de (Postfix) with ESMTP id 513E4DA119B; Thu, 3 Aug 2006 13:26:16 +0200 (CEST) Original-Received: from [84.245.184.166] (helo=[192.168.1.2]) by smtp07.web.de with asmtp (TLSv1:RC4-SHA:128) (WEB.DE 4.107 #114) id 1G8bLE-0000yD-00; Thu, 03 Aug 2006 13:26:16 +0200 In-Reply-To: <1154600309.942065.263290@i42g2000cwa.googlegroups.com> X-Image-Url: http://homepage.mac.com/sparifankal/.cv/thumbs/me.thumbnail Original-To: "std" X-Mailer: Apple Mail (2.752.2) X-Sender: Peter_Dyballa@web.de X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:36434 Archived-At: Am 03.08.2006 um 12:18 schrieb std: > By the way, is latin-9 a smart choice? (compared to latin-1, or other > utf-8 or -16...). I have no idea on these things. Depends =96 I use ISO Latin-9/ISO 8859-15 in LaTeX, because then I can =20= see =80 (ISO Latin-1 does not have the Euro currency), my usual =20 environment is UTF-8 based. GNU Emacs 22.0.50 still is not perfect in =20= UTF-8 use (a month name like M=E4r in dired is displayed as 'M=C3=A4r', =20= file names appear as 'RGB a=CC\210o=CC\210u=CC\210=C3=A6=C3\206U=CC\210O=CC= =20 \210A=CC210.txt' or 'Perl_und_Bu=CC\210cher'), the Unicode Emacs 23.0.0 =20= performs better, so I'd recommend so stay with some 8 bit encoding =20 like ISO Latin-9/ISO 8859-15. And use UTF-8 or UTF-16 for data =20 exchange with MS Windows XP applications. Both encodings are =20 "representations" of a file's contents. UTF-8 uses 8 bit words to =20 code this contents, usually using three or two of these words for =20 each character, only in case of ASCII or ISO Latin-1 use one such =20 word suffices. UTF-16 uses 16 bit words =96 so it can address the first =20= 64 K characters in Unicode uniformly, although it makes a difference =20 in which sequence/direction the two octets of bits are read, BE or =20 LE. Behind the Basic Multilingual Plane (BMP), UTF-8 and UTF-16 need =20 to use 32 bits to address the Unicode characters =96 just as UTF-32 =20 uses from the start. But of course each of these three systems uses =20 its own codes in this range(s)/plane(s) ... -- Greetings Pete Bake Pizza not war!