Short term, you could simply base64 encode them so that at least they go in as something you can do something with later...
On Tue, April 10, 2007 8:27 am, Edward Kay wrote: > I have an app that stores email messages in a database. The app and DB > are > UTF-8 but obviously the emails can be in a variety of character sets. > Most > can be converted easily using mb_convert_encoding or iconv but I have > some > emails encoded as ks_c_5601-1987, which neither of these two functions > handle. > > Googling for ks_c_5601-1987 doesn't help. Most people just say it is > an > invalid charset and can be ignored as spam, but we have genuine emails > that > need to be stored in the DB. > > If I don't convert the messages, they get truncated when inserted into > the > database. > > Any ideas? > > Edward > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
