From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri,  4 May 2007 13:29:03 +0100
From: Derek Fawcus <dfawcus@cisco.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Mac p9p snarf buffer
Message-ID: <20070504132902.D2551@mrwint.cisco.com>
References: <20070503212009.AE2591E8C1F@holo.morphisms.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <20070503212009.AE2591E8C1F@holo.morphisms.net>;
	from rsc@swtch.com on Thu, May 03, 2007 at 05:20:08PM -0400
Topicbox-Message-UUID: 591e1afc-ead2-11e9-9d60-3106f5b1d025

On Thu, May 03, 2007 at 05:20:08PM -0400, Russ Cox wrote:
> + X11 selection formats
> 
> X11 allows (nay, encourages) selections to be arbitrary blocks of
> data.  When you fetch the snarf from an owner, the first thing you do
> is ask for a list of possible formats.  Then you look in the format
> list for one that sounds good to you.  The most common is "STRING".
> Other apps are free to make up names for other strings.  Most seem to
> have standardized on "UTF8_STRING" for a UTF-8 string, though some do
> things like "text/plain;charset=UTF-8".

( For anyone interested,  there are gory details at
  http://www.pps.jussieu.fr/~jch/software/UTF8_STRING/UTF8_STRING.text )

> Bug #3 (fixed).  It had been working okay to respond to all these
> various kinds of strings with UTF-8 data and to ask for plain "STRING"
> and hope it would be UTF-8.  Apparently on OS X that is not okay
> anymore -- when you ask for "STRING" from the X11 server it replaces
> non-ASCII characters with ?.

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.

DF