Hi,
My 2 cents:
- W3C recommends UTF-8
https://www.w3.org/TR/html40/appendix/notes.html#
non-ascii-chars
- HTML5 spec defaults to UTF-8
https://www.w3.org/TR/
html5/document-metadata.html#charset
- java.net.URLEncoder recommends UTF-8
https://docs.oracle.com/
javase/8/docs/api/java/net/URLEncoder.html
- I myself have advocated UTF-8 for almost a decade
http://balusc.omnifaces.org/2009/05/unicode-how-to-get-characters-right.html
- JSF/Facelets defaults to UTF-8
- Everyone keeps homebrewing servlet filters to force
request.setCharacterEncoding("UTF-8")
- And, as Mark mentioned, Tomcat switched to UTF-8 since 2014 and no one
complained
Cheers, B
On Wed, Sep 7, 2016 at 10:38 PM, Edward Burns <edward.burns_at_oracle.com>
wrote:
> >>>>> On Wed, 7 Sep 2016 16:50:15 +0100, Mark Thomas <markt_at_apache.org>
> said:
>
> EB> If the URI RFC is not itself clear, then I think we should not say
> EB> anything about using UTF-8 as the default encoding in the request.
>
> MT> I strongly disagree.
>
> MT> The web is moving (some might argue has moved) towards using UTF-8. We
> MT> should be moving with "the general consensus around the internet" and
> MT> using UTF-8 by default.
>
> MT> Tomcat has been using UTF-8 by default for URIs since early 2014 and I
> MT> don't recall a single issue being reported because of it.
>
> I'm willing to consider changing my position based on your disagreement,
> Mark, but I would love to hear from others on this one. Given the
> intentional design of UTF-8 with respect to compatibility with
> ISO-8859-1 and US-ASCII, we will probably be ok but I do want to hear
> from others.
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
>