Re: What "Unicode support" really means
| From: | Pierre Joye | Date: | Mon, 10 Mar 2014 07:01:33 +0000 |
| Subject: | Re: What "Unicode support" really means | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-73039@lists.php.net to get a copy of this message | ||
On Mon, Mar 10, 2014 at 7:52 AM, Lester Caine <lester@lsces.co.uk> wrote:
> Until there is some agreement here I don't think that the next stage can be taken forward.
I disagree here. Unicode support for identifiers (see below) is a very
small part of what is required to actually support Unicode. See my
initial mail about Unicode support, I think it would help to focus on
the design first, before going down (or better said, up) to the user
land details.
> If the core is ASCII only, then PHP requires other solutions to handling
> unicode material in databases ... that needs to be part of the roadmap.
>
> I will quite happily accept ASCII only core, but IS it the right way
> forward? Or just another quick fix to something people see as too difficult?
The core won't support ascii only, that's the whole point. But I only
referred to Unicode names for identifiers (variables, contants,
methods, classes or functions names).
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org