Yep we tried that for the addDefaultCharset but the issue still crept up...
That`s why it pretty much to try and find a needle in a haystack.
-Sebastien
On 9/8/05, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
Even with the entities, character set issues pop up because browsers ,
and users, can be stupid.
i've had character entities show up wrong on browsers because of one
stupid setting or another. I think the last Safari upgrade to osx
messed them up.
I'd suggest doing a
AddDefaultCharset UTF8
or whatever charset needed to the appropriate host section of your
httpd.conf file
On Sep 8, 2005, at 12:40 PM, David Scott wrote:
> Um, guys, whatever happened to character entities for non-US ASCII
> characters (eg é for e-accent-aigu)? Seems to me it would be
> easy to write a filter to replace outgoing characters with their
> character entity equivalents, thereby avoiding character set issues.
--
"Vivre, c'est se reposer dans le présent."
Proverbe indien
