From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 4 May 2007 22:20:55 -0400 From: Kris Maglione To: 9fans@cse.psu.edu Subject: Re: [9fans] Mac p9p snarf buffer Message-ID: <20070505022055.GC62050@kris.home> References: <20070503212009.AE2591E8C1F@holo.morphisms.net> <20070504132902.D2551@mrwint.cisco.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Content-Disposition: inline In-Reply-To: <20070504132902.D2551@mrwint.cisco.com> User-Agent: Mutt/1.5.15 (2007-04-06) Topicbox-Message-UUID: 59ef9fd2-ead2-11e9-9d60-3106f5b1d025 --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 04, 2007 at 01:29:03PM +0100, Derek Fawcus wrote: >That sounds like a bug in the apple stuff. AFAICR "STRING" encoding >means 8 bit latin1 (8859-1) characters. So unless the apple code is >complaining about bytes for which there is no 8859-1 character, I'm >not sure what's happening. The behavior is undefined if a STRING is not in the 'Host Portable=20 Character Set', but it's not the X server which causes the problem, it's=20 the owner of the selection which converts it to a STRING from UTF-8. I'd=20 guess that most apps use iconv (ick) for the conversion. Some apps give=20 you a '?', some give \xXXXX, \uXXXX, or the like. Incidentally, snarfer is still broken in this manner. --=20 Kris Maglione If at first you don't succeed, try something else. --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGO+oHseQZD8Aui4wRAgkQAJ0YTgWGz5JWnhEtR0+PToTEc+k0EACeIqJE UZ3Jh4c3atlvKV2Nr/zx3fM= =2GKV -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR--