I had some more thoughts on this. I'm curious how you manage to have
an encoding type mismatch. In JSP's, encoding is set with the
"<[EMAIL PROTECTED]>" or "" tags with "encodingType" or
"contentType" attributes. In servlets, it's set with
javax.servlet.ServletResponse.setContentType(String) th
Peter Crowther wrote:
>Ah! A good, soft solution!
It works around the underlying problem but that problem (encoding
mismatch) is still there which would still bother me if it was my app.
--Bill Davidson
-
To start a new topic,
On Mon, May 12, 2008 at 4:56 PM, Peter Crowther
<[EMAIL PROTECTED]> wrote:
> > From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED]
>
> > UPDATE currencies SET symbol = '£' WHERE ISO_CODE = 'GBP';
>
> Ah! A good, soft solution! I hope there was a semicolon in there just
> before the closing sin
> From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED]
> UPDATE currencies SET symbol = '£' WHERE ISO_CODE = 'GBP';
Ah! A good, soft solution! I hope there was a semicolon in there just before
the closing single quote, though!
UPDATE currencies SET symbol = '£' WHERE ISO_CODE = 'GBP';
Hi...
> Changing the encoding in the first. You want to change the second.
I changed the second.
> If they're writing XHTML rather than HTML, I'm not sure that entity exists -
> they need to check. That may be why they're writing the value directly,
> although £ would also do the job.
UP
> From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED]
> > What encoding are you using?
>
> The config files all used UTF-8. I've changed them to ISO8859-1 and
> restarted Tomcat, but I see the same behaviour.
What do you mean by "used UTF-8"? Remember that there are:
- The encoding in which t
Hi...
> What encoding are you using?
The config files all used UTF-8. I've changed them to ISO8859-1 and
restarted Tomcat, but I see the same behaviour.
> You can go hunting for all the places in which the encoding could be
> specified
At the Tomcat level?
> or you can tell the developers
> From: Yuval Perlov [mailto:[EMAIL PROTECTED]
> Use the £ to side step the issue. diff the old and the new page
> to see what changed (something must have, right?)
Not necessarily - the obvious thing to have changed is the encoding passed in
the Content-Type HTTP header. Diffing the bytes in th
Use the £ to side step the issue. diff the old and the new page
to see what changed (something must have, right?)
On May 12, 2008, at 5:33 PM, Stephen Nelson-Smith wrote:
Hello,
On Mon, May 12, 2008 at 3:30 PM, Yuval Perlov <[EMAIL PROTECTED]> wrote:
Probably the encoding has changed
Whic
> From: Stephen Nelson-Smith [mailto:[EMAIL PROTECTED]
> I've just upgraded from 4.1.37 to 6.0.16. My app works, but where my
> code usually displays a British Pound sign, I get an odd char - a ? in
> a diamond on Linux, an empty box on Windows.
>
> Here's the html that the app produces, shown in
Hello,
On Mon, May 12, 2008 at 3:30 PM, Yuval Perlov <[EMAIL PROTECTED]> wrote:
> Probably the encoding has changed
Which encoding? I don't believe the source code has changed.
How would I test and/or change this? Where?
S.
Probably the encoding has changed
On May 12, 2008, at 5:15 PM, Stephen Nelson-Smith wrote:
I've just upgraded from 4.1.37 to 6.0.16. My app works, but where my
code usually displays a British Pound sign, I get an odd char - a ? in
a diamond on Linux, an empty box on Windows.
Here's the html t
12 matches
Mail list logo
