Jeff Trawick wrote:
>
> Jim Jagielski <jim@jaguNET.com> writes:
>
> > Did the patch actually fix the problem? On pages where it
> > was using the default charset, did the below actually make
> > it use the "set" charset?
> >
> Jim:
>
> Can you get AddDefaultCharset charset-name to Do The Right Thing
> without the patch? I'd love to see an example. Without the patch,
> all I've been able to get AddDefaultCharset to do is enable/disable
> the iso-8859-1 string. With the patch, it seems to work as expected.
>
Yeah, I was able to get it to work correctly, but only in a general
sense. Now that I understand the exact bug, I agree the patch
makes sense.
--
===========================================================================
Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/
"Are you suggesting coconuts migrate??"
|