-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 4/3/2009 6:43 PM, André Warnier wrote:
4) the HTML specs are distinct from the HTTP specs. [...] It also
seems to be superfluous and confusing considering (1) and (2) above.
(Like, what if (1) and (4) specify different
Something more to consider relating to specifying charsets in meta tags :
It's of course ok that a server sends http headers specifying in what
charset the page is encoded but when the user comes to saving that web page
on local drive there's nothing left that meta tags to inform browsers the
page
I am using Tomcat 6.0.18 with Eclipse. It says the port is being used.
Where do I change?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Not as much unrelated to the topic that my interventoion was - sorry didn't
see it had already been addressed.
On Mon, Apr 6, 2009 at 10:00 PM, Chris Lenart clen...@comcast.net wrote:
I am using Tomcat 6.0.18 with Eclipse. It says the port is being used.
Where do I change?
Gregor Schneider wrote:
And it's getting really nuts, when it comes to UTF-8: Talking about
UTF-8 with or without BOM? Even the specs are not clear about that.
Actually, a UTF-8 stream should /never/ need a BOM, because there is no
byte-order, UTF-8 being by definition byte-oriented.
The only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oscar,
On 4/2/2009 1:30 PM, Je suis la poubelle wrote:
On Fri, Mar 27, 2009 at 5:34 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
While it's not a terrible idea to specify the encoding in both places,
you should consider the
Hi.
One of my preferred subjects...
1) as per the HTTP specs, the server should send a Content-Type header
along with any response to a browser. If the response is of the general
type text, then this Content-Type header should also contain a charset
attribute, indicating the character set
Christopher Schultz:
The problem is when the web server sends a response, it sends it using a
particular character set (let's just say UTF8 for argument's sake). If
you also report that the character set is UTF8 in the META tags, then
it's only valid if the client saves the file to the disk
On Fri, Mar 27, 2009 at 5:34 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oscar,
On 3/27/2009 10:35 AM, Je suis la poubelle wrote:
1. In those mentioned web pages, I noticed that none of them explicitly
specified the
On Thu, Apr 2, 2009 at 7:30 PM, Je suis la poubelle laps...@gmail.com wrote:
On Fri, Mar 27, 2009 at 5:34 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
Setting charset/encoding is to specify computerized information. It's
not just a matter of language. If setting charset in
My few cents...
1. In those mentioned web pages, I noticed that none of them explicitly
specified the following HTML header:
head
meta http-equiv=Content-Type content=text/html; charset=utf-8
/head
Yes, I understand that the same info is sent in HTTP header, but well,
that's in theory,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oscar,
On 3/27/2009 10:35 AM, Je suis la poubelle wrote:
1. In those mentioned web pages, I noticed that none of them explicitly
specified the following HTML header:
head
meta http-equiv=Content-Type content=text/html; charset=utf-8
/head
/catalina.bat and catalina.sh
(http://answers.google.com/answers/threadview?id=580467) and it still
doesn't work.
Anyone know what the problem is?
--
View this message in context:
http://www.nabble.com/Tomcat-5-and-UTF-8-tp22726898p22726898.html
Sent from the Tomcat - User mailing list archive
From: hellokk [mailto:kw...@hotmail.com]
Subject: Tomcat 5 and UTF-8
I have installed Tomcat version 5.028
Which hasn't been supported for quite some time. Can you try with a current
level and see what happens?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
I have tried with the 5.5.27 version, and I still get the same error.
Caldarale, Charles R wrote:
From: hellokk [mailto:kw...@hotmail.com]
Subject: Tomcat 5 and UTF-8
I have installed Tomcat version 5.028
Which hasn't been supported for quite some time. Can you try with a
current
15 matches
Mail list logo