I don't want to argue per-se (that doesn't do anyone any good), so if your mind is made up, that's cool... still, I think there's some value in exploring the options, so read on if you're so inclined.
On Wed, 2004-08-11 at 04:40, Dan Sugalski wrote:
> Converting Unicode to non-Unicode character sets will be > lossless where possible, and will attempt to encode the name of > the character in ASCII characters into the target character set.
Gack. No, I think this'd be a bad idea as the default behavior.
Well ok, why not make an exception the default behavior then? Just reverse what I suggested from the default to the option. It's still mighty handy for a language (any Parrot-based language) to be able to render a meaningful string in any ASCII-capable encoding from any Unicode subset.
If it's that handy then someone can write a library routine. This feels very much to be in the same category as running a speech-to-text algorithm if you send WAV data to a text filehandle.
Not going to happen. Charset conversion mismatches either throw an exception or falls back to a default bogus character.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
