Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29136
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.250 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tepzi7DVjjnlVyDLe5THtbIm5GTFUGqsQMnTPOfBRBCWQK98M81tUkVyLrOS1d9NQe/2tzqIrTxbkBLuHzEWw42eNoXG+hXP7mdEzN5pQfzVMWAhBy9/7dTnQ9YSE1U7TZ8G7z0zVa4ko3o9bIw78J7iGdZC3z+OLud9wzQ7VHQ=
Message-ID: <cd5680a20705030130s6a5c11bepb5bac7937dab31ea@mail.gmail.com>
Date: Thu, 3 May 2007 12:30:05 +0400
To: "Rangel Reale" <listas@rangelreale.com>
Cc: internals@lists.php.net
In-Reply-To: <006c01c78d26$beda26f0$0301a8c0@rangeldc>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <006c01c78d26$beda26f0$0301a8c0@rangeldc>
Subject: Re: [PHP-DEV] Trying to understand PHP6's unicode support
From: indeyets@gmail.com ("Alexey Zakhlestin")

php6 always handles all "internal work" in utf-8
But, from what I remember, there should be a way to specify encoding
in which you expect data to arrive (in this example from mysql_*)

I think, that someone who knows more will give you more details

On 5/3/07, Rangel Reale <listas@rangelreale.com> wrote:
> Hello!
>
> I am trying to understand how PHP6 handling of unicode works, I think I am
> missing something.
>
> My config is:
>
> ;;;;;;;;;;;;;;;;;;;;
> ; Unicode settings ;
> ;;;;;;;;;;;;;;;;;;;;
>
> unicode.semantics = on
> unicode.runtime_encoding = iso-8859-1
> unicode.script_encoding = iso-8859-1
> unicode.output_encoding = utf-8
> unicode.from_error_mode = U_INVALID_SUBSTITUTE
> unicode.from_error_subst_char = 3f
> unicode.fallback_encoding = iso-8859-1
>
> I use a mysql database, with iso-8859-1 (Portuguese - latin 1) text, with
> accented characters.
>
> What I was trying to understand was, because unicode.runtime_encoding =
> iso-8859-1, I tought that all internal operations were done in this
> encoding, and only when outputting (unicode.output_encoding = utf-8) data
> would be converted to utf-8. So to me, I did a mysql query with latin1, data
> comes to my variables as iso-8859-1, I use them, and only when I echo'ed
> them, they would become utf-8, from a iso-8859-1-to-utf-8-like function.
>
> But when I do query in any record that have accented characters I get this
> warning (using mysql_fetch_assoc):
>
> ----------
> Could not convert binary string to Unicode string (converter UTF-8 failed on
> bytes (0xE7) at offset 9)
> ----------
>
> for all accented characters in all fields.
>
> The strange thing to me, is the mysql_fetch_assoc function give this error
> even before I accessed the field values, as I understanded from the above
> explanation.
>
> If I changed the set names query to:
>
>   mysql_query('set names utf8', $this->mysql_link);
>
> then it works, but I would like to understand how this works, to make my
> program the right way from the start.
>
> Did I misundertood something?
>
> Thanks,
> Rangel
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Alexey Zakhlestin
http://blog.milkfarmsoft.com/