Can anyone tell me *why* this would be? And more to the point, why I wouldn't want to be able to specify a character set that works in all modes?
Here's the thing: because Apache wants to default to charset=iso-8859-1, that basically means any non-iso characters get mangled in the process. Because my company is very committed to its trademarks and the like, they insist on using those characters when they type into the content management system. Sure, I could code my way around all that for days, but if we have a clear UTF-8 pipe from database to server to client, I don't need to. But CakePHP is messing up the show in development environments. Again, I could change the default character set on my server, but if I have the control in CakePHP to bypass that whole thing, why wouldn't I want to do that? Because its screwing up in DEBUG mode, is why. I'm just wondering what the logic is? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
