???????? wrote: > ... > When I first saw the utf-8 encoding description, it was an epiphany of sorts.
Yes, it does have some nice characteristics. > > > > Normally, you should not have to ever convert strings between > > > encodings. > > > > Then how do you process, say, a multi-part MIME body that has parts > > in different character encodings? > > Excellent example. Email is absolutely something that you can work > with on a byte-by-byte basis and have no need for considering > characters. What operations are you excluding when you say "work with?" You're being quite non-specific. Maybe that's part of the cause of our arguing. Certainly searching for a given character string across multiple MIME parts requires handling different encodings for different parts. And searching with a regular expression containing "." to match any character requires some encoding-cognizant processing somewhere in the processing path (either in decoding byte sequences to character sequences, or in implementing the regular-expression matching if it operates directly on, say, UTF-8). Daniel -- Daniel Barclay [EMAIL PROTECTED] -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
