here ms_no = 'CAN-06-2483'
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Monday, August 13, 2007 5:24 PM
To: Tomcat Users List
Subject: Re: character encodingg problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Russo, Joe wrote:
>
> From: Ryan Shelley [mailto:[EMAIL PROTECTED]
> Subject: Re: character encodingg problem
>
> however, I noticed that when I redeploy my war, my custom
> it#idm.war context file is also removed
You can't use the manager app or any other conventional script I know of
t
2007 3:00 PM
To: Tomcat Users List
Subject: Re: character encodingg problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Russo, Joe wrote:
Of course, the existing data that is stored incorrectly can not be
viewed correctly. I thought by changing the filter you sent by
interrupting the char
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Russo, Joe wrote:
> Chris,
> Thank you very much for you response. I am going to try and look at how
> long it will take to do this type of conversion for 39 databases.
Ouch! Perhaps your database supports a query that might be able to do
thi
Subject: Re: character encodingg problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Russo, Joe wrote:
> Of course, the existing data that is stored incorrectly can not be
> viewed correctly. I thought by changing the filter you sent by
> interrupting the charset as ISO-8859-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Russo, Joe wrote:
> Of course, the existing data that is stored incorrectly can not be
> viewed correctly. I thought by changing the filter you sent by
> interrupting the charset as ISO-8859-1 for the response would work
> correctly.
No, the pr
From: Nathan Hook [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 2:13 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat5.0.28 character encodingg problem
Both Chris and Tim are giving great advice. We're actually just trying
to
internationalize our application for our next
d>
in last sentence
(Ã<83>Â<83>Ã<82>Â<83>Ã<83>Â<82>Ã<82>¢Ã<83>Â<83>Ã<82>Â<82>Ã<83>Â<82>Ã<82>Â<80>Ã<83>Â<83>Ã<82>Â<82>Ã<83>Â<82>Ã<82>¦
repeated endocytosis of
thanks chris,
our client doesn't want to upgrade to tomecat 5.5 - that's our problem.
Aleksey
From: Christopher Schultz [EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 5:55 PM
To: Tomcat Users List
Subject: Re: Tomcat5.0.28 character encodin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aleksey,
Aleksey Dayen wrote:
> Right now we using TomCat 4.1 with JDK 1.1.
Wow, really? I would think that JDK 1.2 would be the bare minimum for
Tomcat 4.1.
> Would our TomCat version work if we update to J2SDK 5.0 with Update 6?
Maybe. IIRC, Tomc
: Re: Tomcat5.0.28 character encodingg problem
I think my statement of "most browsers will ignore this value" might have
been a tad bit on the excessive side upon further reading and i was hoping
to have that read as don't only rely on using the meta tag.
>From my understanding
I think my statement of "most browsers will ignore this value" might have
been a tad bit on the excessive side upon further reading and i was hoping
to have that read as don't only rely on using the meta tag.
From my understanding there are broswers where they can set their own
content type no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
Nathan Hook wrote:
> - Set the meta type in each and every jsp to be utf-8. Now, most
> browsers will ignore this value from my understanding, but it shouldn't
> hurt to add it.
Really? The HTTP header should override any META tag, but the M
: Re: Tomcat5.0.28 character encodingg problem
Both Chris and Tim are giving great advice. We're actually just trying
to
internationalize our application for our next major release.
Here are the things we've learned.
- You have to change the URIEncoding on your Tomcat Connect
using utf-8.
In mysql you add the following to your jdbc url connection string:
useUnicode=true
characterEncoding=UTF-8
I hope all that information helps.
Original Message Follows
From: Tim Funk <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List"
To: Tomcat Users List
Subject: Re: Tomc
http://tomcat.apache.org/faq/misc.html#utf8
And you should first start with in server.xml:
-Tim
Joe Russo wrote:
I am getting the following error in the display of the JSP. To give a
little history, this application I am supporting, at the time the
developers thought they needed to encod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Joe Russo wrote:
> I am in the process of converting from using JRUN to Tomcat
Good for you! Welcome to the community.
> I have
> ran into the problem where these funky symbols are displaying. I can
> not find any stack traces that would expla
I am getting the following error in the display of the JSP. To give a
little history, this application I am supporting, at the time the
developers thought they needed to encode the characters to UTF-8 into
our Oracle DB. The developers were unaware they could have allowed the
DB Driver convert it
18 matches
Mail list logo
