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
