On Mon, 8 Jan 2001, Kingpin wrote: > > > I18N::Charset was created as a step toward solving that problem... > > > > As in: "Let's create yet another slightly incompatible standard"? :-) > > Basically, it maps charset names and aliases to the IANA registry > names. Hmmmm....Sounds like something I should add support for to Unicode::MapUTF8. I am trying to make it as transparently DWIM as possible. -- Benjamin Franz ... with proper design, the features come cheaply. This approach is arduous, but continues to succeed. ---Dennis Ritchie
- RE: Source data for perl encodings Ed Batutis
- Re: Source data for perl encodings Nick Ing-Simmons
- RE: Source data for perl encodings Mark Leisher
- RE: Source data for perl encodings Nick Ing-Simmons
- Re: Source data for perl encodings Owen Taylor
- Re: Source data for perl encodings Jarkko Hietaniemi
- Re: Source data for perl encodings Kingpin
- Re: Source data for perl encodings Jarkko Hietaniemi
- Re: Source data for perl encodings Nick Ing-Simmons
- Re: Source data for perl encodings Kingpin
- Re: Source data for perl encodings Benjamin Franz
- Re: Source data for perl encodings Jarkko Hietaniemi
- Re: Source data for perl encodings James
- Re: Source data for perl encodings Philip Newton
- ISO 10646-1:2000 affordable Markus Kuhn
- Re: Source data for perl encodings Nick Ing-Simmons
- Re: Source data for perl encodings Markus Kuhn
- RE: Source data for perl encodings Ed Batutis
- Re: Source data for perl encodings Ed Batutis
- Re: Source data for perl encodings Ed Batutis
- Re: Source data for perl encodings Jarkko Hietaniemi