Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58880
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
Sender: mikegstowe@gmail.com
In-Reply-To: <4F5E15D6.6080302@lerdorf.com>
References: <4F5D9C77.3030000@lerdorf.com> <4F5DA152.10109@sugarcrm.com>
 <4F5DA894.8060606@lerdorf.com> <4F5DAB49.3030808@sugarcrm.com>
 <4F5DAFCE.8020600@lerdorf.com> <CAGa2bXbNOqoDdQsmyWrXR+Qw8E6o2uxWbrnKXBwJewwjtpMJ_g@mail.gmail.com>
 <4F5E15D6.6080302@lerdorf.com>
Date: Mon, 12 Mar 2012 10:39:54 -0500
Message-ID: <CAH8KiXLRpecDGs9e1xskGCd+y5O84QHxMNT_H_vGs5fHgBhoyw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=90e6ba6e86ea0eb43e04bb0d8f7f
Subject: Re: [PHP-DEV] default charset confusion
From: me@mikestowe.com (Michael Stowe)

--90e6ba6e86ea0eb43e04bb0d8f7f
Content-Type: text/plain; charset=ISO-8859-1

I think the ini directive, while adding another to the list, may be the
most unobtrusive method to address this issue, at least for developers.

I definitely agree with Rasmus that this could be one of the bigger
headaches in transitioning to 5.4 (for non-UTF8 sites) and unless we can
come up with a better solution, I say let's move forward with it for 5.4.1.

- Mike





On Mon, Mar 12, 2012 at 10:27 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 03/12/2012 03:05 AM, Yasuo Ohgaki wrote:
> > Hi
> >
> > I think following PHP 5.4.0 NEWS entry is misleading.
> >
> >   . Changed default value of "default_charset" php.ini option from
> ISO-8859-1 to
> >     UTF-8. (Rasmus)
>
> Yes, I have fixed that now.
>
> > I thought default_charset became UTF-8, so I was expecting
> > following HTTP header.
> >
> > content-type  text/html; charset=UTF-8
> >
> > However, I got empty charset (missing 'charset=UTF-8').
> > So I looked up to source and found the line in SAPI.h
> >
> > 293   #define SAPI_DEFAULT_CHARSET        ""
> >
> > Empty string should be "UTF-8", isn't it?
>
> No, we can't force an output charset on people since it would end up
> breaking a lot of sites.
>
> >  - php.ini's default_charset should be UTF-8.
> >  - determine_charset() should not blindly default to UTF-8 when there
> > are no hint.
> >
> > Old htmlentities/htmlspecialchars actually determines charset from
> > default_charset/mbstring.internal_encoding/etc. I think old behavior
> > is better than now.
> >
> > How about make determine_charset() behaves like 5.3 and set the
> > SAPI_DEFAULT_CHARSET to "UTF-8"?
>
> PHP 5.3's determine_charset behaves exactly like 5.4's. In 5.3 we have:
>
>    if (charset_hint == NULL)
>                return cs_8859_1;
>
> and in 5.4 we have:
>
>    if (charset_hint == NULL)
>                return cs_utf_8;
>
> So there is no difference in their guessing when there is no hint, the
> only difference is that in 5.4 we choose utf8 and in 5.3 we choose
> 8859-1 in that case.
>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
-----------------------

"My command is this: Love each other as I
have loved you."                         John 15:12

-----------------------

--90e6ba6e86ea0eb43e04bb0d8f7f--