Re: utf-8 encoding problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark and Joe, Mark Thomas wrote: Joseph Shraibman wrote: Mark Thomas wrote: request.setCharacterEncoding(UTF-8); Is this always safe? For responses I can (and do) check the accept-charset request [header], but I can't figure out how to

Re: utf-8 encoding problem

Christopher Schultz wrote: Setting the encoding of the response is sometimes necessary when the browser (stupidly, IMO) elects not to send the charset being used to the server. It isn't the browser's fault, its the spec's fault. See https://bugzilla.mozilla.org/show_bug.cgi?id=289060#c8

Re: utf-8 encoding problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joe, Joseph S wrote: Christopher Schultz wrote: Setting the encoding of the response is sometimes necessary when the browser (stupidly, IMO) elects not to send the charset being used to the server. It isn't the browser's fault, its the spec's

Re: utf-8 encoding problem

Try this then - this is my standard character encoding index.jsp test. %@ page contentType=text/html; charset=UTF-8 % !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN html head titleCharacter encoding test page/title /head body pData posted to this form was: %

Re: utf-8 encoding problem

Mark Thomas wrote: request.setCharacterEncoding(UTF-8); Is this always safe? For responses I can (and do) check the accept-charset request paramater, but I can't figure out how to tell what the request encoding should be.

Re: utf-8 encoding problem

This is an old problem. See https://bugzilla.mozilla.org/show_bug.cgi?id=18643 https://bugzilla.mozilla.org/show_bug.cgi?id=7533 Firefox and MSIE use a magic _charset_ paramater, but I can't use it because if I call request.getParamater(_charset_) I can't set the encoding after that!

Re: utf-8 encoding problem

Joseph Shraibman wrote: This is an old problem. See https://bugzilla.mozilla.org/show_bug.cgi?id=18643 https://bugzilla.mozilla.org/show_bug.cgi?id=7533 Firefox and MSIE use a magic _charset_ paramater, but I can't use it because if I call request.getParamater(_charset_) I can't set the

Re: utf-8 encoding problem

Joseph Shraibman wrote: Mark Thomas wrote: request.setCharacterEncoding(UTF-8); Is this always safe? For responses I can (and do) check the accept-charset request paramater, but I can't figure out how to tell what the request encoding should be. It should be reasonable unless the

RE: utf-8 encoding problem

@tomcat.apache.org To: Tomcat Users List users@tomcat.apache.org Subject: utf-8 encoding problem Date: Tue, 14 Aug 2007 22:24:28 -0400 My problem is this: One of my pages with an apostrophe was not displaying properly, so I added to my jsp: %@ page contentType=text/html; charset=UTF-8% When I did that my

Re: utf-8 encoding problem

Nathan Hook wrote: A few things... First, what type of apostrophe are you using? Are you using a typical ascii apostrophe (') or are you using the Microsoft slanted apostrophe that comes out of word documents (#8242;)? It's #8217; Here are two links that describe the problem:

Re: utf-8 encoding problem

Joseph S wrote: When I did that my content displayed correctly, but on form submission it got corrupted. POST or GET? Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: utf-8 encoding problem

POST Mark Thomas wrote: Joseph S wrote: When I did that my content displayed correctly, but on form submission it got corrupted. POST or GET? Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,

utf-8 encoding problem

My problem is this: One of my pages with an apostrophe was not displaying properly, so I added to my jsp: %@ page contentType=text/html; charset=UTF-8% When I did that my content displayed correctly, but on form submission it got corrupted. You can view the problem here: