php-i18n Digest 8 Jul 2008 00:22:14 -0000 Issue 403

Topics (messages 1269 through 1271):

Re: intl 1.0.0RC1
        1269 by: Texin, Tex
        1270 by: Stanislav Malyshev

intl merged into core
        1271 by: Stanislav Malyshev

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------
--- Begin Message ---
Are we keeping the 5.2 names in 5.3 as well or is the proposal that 5.2 apps 
get rewritten for 5.3?

I don't really see the need to make changes for 5.3 for the sake of satisfying 
this particular naming convention.
For php 6, it can make sense given the other changes being required.


tex
 

> -----Original Message-----
> From: Norbert Lindenberg ☮ [mailto:[EMAIL PROTECTED] 
> Sent: Friday, June 13, 2008 11:34 PM
> To: Guillaume Rossolini
> Cc: Norbert Lindenberg ☮; Darren Cook; Stanislav Malyshev; 
> [EMAIL PROTECTED]
> Subject: Re: [PHP-I18N] intl 1.0.0RC1
> 
> I like Guillaume's proposal - use Collator and Locale as is 
> for 5.2, make them Intl::Collator and Intl::Locale when 
> namespaces are available, i.e., from 5.3.
> 
> Would that work for everybody? How much effort is it to 
> implement this?
> 
> Norbert
> 
> 
> On Jun 10, 2008, at 02:44 , Guillaume Rossolini wrote:
> 
> > Hi,
> >
> > Here's my user point of view, if you don't mind.
> >
> > I think your argument is about namespaces, which will be in 
> 6 but not 
> > 5.2...  So you might want to have IntCollator and IntLocale 
> in 5.2 to 
> > avoid possible collisions, but you would rather have something like 
> > Intl::Collator and Intl::Locale from 5.3 and 6 onward.  I guess the 
> > question is:
> > can you
> > bear with Collator and Locale until we have namespaces?  I 
> know I can.
> >
> > Guillaume Rossolini
> >
> 
> -------------------------------------
> Norbert Lindenberg
> Yahoo! Internationalization Architect
> 
> 
> 
> --
> PHP Unicode & I18N Mailing List (http://www.php.net/) To 
> unsubscribe, visit: http://www.php.net/unsub.php
> 
> 

--- End Message ---
--- Begin Message ---
Hi!

Norbert Lindenberg ☮ wrote:
I like Guillaume's proposal - use Collator and Locale as is for 5.2, make them Intl::Collator and Intl::Locale when namespaces are available, i.e., from 5.3.

Would that work for everybody? How much effort is it to implement this?

If we make this exclusively, this would mean that 5.2 and 5.3/6 users would have incompatible code. I don't think it's a good idea.

We may make Intl::Collator as alias for Collator in 5.3+, and that'd be easy, but I'm not sure that'd what people here want.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED]   http://www.zend.com/
(408)253-8829   MSN: [EMAIL PROTECTED]

--- End Message ---
--- Begin Message ---
Hi!

Following more than a year of planning and development, and the release of version 1.0.0 on PECL, I have merged today the intl extension into PHP core. The list of its current capabilities is here: http://php.net/intl - please try it out and enjoy. Version compatible with 5.2.x starting 5.2.4 is available from PECL, and for 5.3 is in the CVS tree.

I would like to say big thanks to everybody who contributed to this project, by helping to design it, write the code, test it or provided feedback and bug reports. Thanks a lot!

With this, it is not by any means the end of the road for this project. There's still much to be done. We need to integrate it much better with PHP 6, improve support for other modules like DateTime, and support more capabilities of ICU, like resources, calendars, IDN - and you probably could think of more. And, of course, bugfixes :)

If you have any comments, wishes, feedback etc. please tell. And if you encounter a bug or have specific feature request please go to http://pecl.php.net/package/intl and go to "Package Bugs"->"Report new bug".

--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED]   http://www.zend.com/
(408)253-8829   MSN: [EMAIL PROTECTED]

--- End Message ---

Reply via email to