Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of joseph.millet@gmail.com
 designates 209.85.219.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=vATymcN5bQkn6+IAEXFlumdrCja4GwWzXPawGy6hI1zDVON6sfOxciMn0tcQABNjd9
         rntX1ry4V7xSvNaUF8HOpdFpvhNNGxbTdbZlLXz2gaoHwYaFdNsWcfmzt3kL/LAj8JD0
         2ckuFx/JU0S9t6gzcZRBBcqnjTHyy9OfgDHXU=
MIME-Version: 1.0
In-Reply-To: <49DA505F.2060309@christopherschultz.net>
References: <22726898.post@talk.nabble.com>
	 <0AAE5AB84B013E45A7B61CB66943C17215E69187A9@USEA-EXCH7.na.uis.unisys.com>
	 <22730558.post@talk.nabble.com> <49CBEBEC.5020407@apache.org>
	 <ba45aea10903270735n261b849andf3e45e83333cecf@mail.gmail.com>
	 <49CCF1E8.8060200@christopherschultz.net>
	 <ba45aea10904021030i59825143gee5bd3f627047f0a@mail.gmail.com>
	 <49D68185.2090404@christopherschultz.net>
	 <49D69113.2070000@ice-sa.com>
	 <49DA505F.2060309@christopherschultz.net>
Date: Mon, 6 Apr 2009 21:15:45 +0200
Message-ID: <7549877b0904061215l3717fce6o238130a55cb86976@mail.gmail.com>
Subject: Re: Tomcat 5 and UTF-8
From: Joseph Millet <joseph.millet@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=0016e6dbe920ab89cc0466e7b974

--0016e6dbe920ab89cc0466e7b974
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 is encoded in utf-8. So depending on wether your app's users are likel=
y
to save locally served contents it might be a good thing to also consider
putting this piece of information directly into the html doc.

On Mon, Apr 6, 2009 at 8:56 PM, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andr=E9,
>
> On 4/3/2009 6:43 PM, Andr=E9 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 charsets/encodings ?).
>
> The HTML spec says that the Content-Type wins the argument ;)
>
> > Why hasn't a proposal for HTTP 2.x / HTML 5.x
> > come about, reconciling those aspects and establishing Unicode/UTF-8 as
> > the default (or only) encoding, for URLs as well as content ?
>
> http://dev.w3.org/html5/spec/Overview.html
>
> > 8) What is also missing in my view, is some more general proposal
> > covering the format of text files (and text streams), anywhere.  To
> > alleviate any ambiguity, each text file/stream should contain at least =
a
> > short prefix indicating its MIME type and its charset/encoding.
>
> I always thought this was a good idea:
> http://en.wikipedia.org/wiki/Resource_fork
>
> > All the above is why I keep on seeing my name echoed back to me as
> > Andr=C3=A9, even on some well-known supposedly international websites.
>
> :(
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknaUF8ACgkQ9CaO5/Lv0PAqHACfbVa11mljL/B7U6oLkkUI5/8k
> 3uEAn3wEFNHyTYjdYLAey+gbzffz1Vv6
> =3D5qZ1
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--0016e6dbe920ab89cc0466e7b974--