> I hope Apple re-thinks this, because it makes PUA useless in plain text.
That's because it is. Without further specification, the PUA is completely ambigious. > end > users get to control display behavior by re-assigning PUA code points or > de-installing fonts, whereas they have no control and no visual > information if the OS just gives up. You can binary patch your OS to fix this behaviour. That's about as reasonable as reencoding your data or removing fonts until the system pseudo-randomly picks the right font. > So, for example, in Jaguar I had been using a PUA-based cuneiform font > for file and folder names, which I found to be very nice and very useful; Nice and useful? At least in my experiance, giving my folders names I can't write from the keyboard, that can't be displayed in many of the fonts on my system, is at best an affection. Using PUA characters for filenames is unportable and it's a marginal use, even among the uses of PUA characters. Given the choice between the private use area working right in wordprocessors and text editors or it working in filenames, I'd pick the first, and not be real sorry about disrupting the second. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
