[RFC] Merge charsets and encodings
Patrick R. Michaud
pmichaud at pobox.com
Wed Aug 25 13:16:03 UTC 2010
On Wed, Aug 25, 2010 at 02:44:03PM +0200, Nick Wellnhofer wrote:
>
> I think the separation of charsets and encodings in the string code
> doesn't make sense. The way I see it, the only charset that's used
> in Parrot is Unicode. ASCII and ISO-8859-1 are subsets of Unicode,
> so they could be treated like the other UTF and UCS encodings.
...in other words, you're proposing that Parrot declare that it will
never use any character sets other than Unicode? What about ebcdic,
iso-8859-*, KOI8-*, etc?
I'm not opposed to such a change... I just want to verify that
this is in fact what you and others are proposing in this thread.
Just because Parrot doesn't support other character sets today
doesn't automatically imply that we'll never want to support them.
Pm
More information about the parrot-dev
mailing list