On Fri, Mar 18, 2011 at 8:28 AM, John Joyce <dangerwillrobinsondan...@gmail.com> wrote: > You might also consider using HTML entities for those, as you never know what > the browser/user-agent has set for encoding...
You do if you generate correct HTML and your web server emits the correct Content-type header. Charles, since it sounds like you're in control of the entire pipeline, the correct solution is to store the UTF-8 data in the MySQL database, and fix your web frontend to correctly output UTF-8 with the proper Content-type header. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com