RE: [PHP-DEV] Re: [php-icu] Graphemes and unicode vs intl extension

-----Original Message----- From: Hannes Magnusson [mailto:hannes.magnusson@gmail.com] Sent: Sunday, March 23, 2008 1:31 PM To: Tex Texin Cc: Marcus Boerger; Pierre Joye; php-icu@lists.zend.com; PHP Developers Mailing List Subject: Re: [PHP-DEV] Re: [php-icu] Graphemes and unicode vs intl extension On Sun, Mar 23, 2008 at 8:30 PM, Tex Texin <tex@yahoo-inc.com> wrote: > The first thing we did was look at the coding standard. OK. Well done then. I guess I was just very unlucky picking locale/locale_methods.c to view then. ========== Tex> that was among the first modules we wrote. But I don't think you have said what is not Tex> compliant with the standard. My suggestion is to file a bug against the intl extension so we can track issues and so they don't get lost in these email threads. > Stas explained the reason we chose the naming we did. Which is great. But you don't think it would have been better to decide this collaboratively in the open rather then on your enterprise 8-16 mailinglists? If it had been we wouldn't be having this discussion now. (btw; why are you replying to these mails today? I find it very odd, but you definitely deserve a cookie for it! :D) =============== Tex> The api was posted and open for review and collaboration, so no I don't think the Tex> existence of another list made a difference. I guess I shouldn't have phone discussions or beers with anyone working on php either so I don't risk having a non-collaborative discussion somewhere. Stas was doing a great job explaining and I didn't have a need to say more. I offered the info on the project history to try and clarify the one point. I would take the cookie but then people would accuse us of not being open and having some secret desire to topple PHP. > Having to work on other tasks is not abandonment. It reflects that we also have other > reponsibilities. And you replying on a Sunday, easter even, is awesome. But it is still scary thought you won't be actively around to follow bug reports or feature requests or whatever. As you know very few (if any) on this list have any clue on what you guys have been discussing or working on in your offlist talks. =========== Tex> This is a volunteer effort to solve a problem that PHP does not have sufficient Tex> internationalization. If the volunteers need to make a lifelong commitment to support the code, then Tex> maybe we should withdraw the submission. If you look at what we did, it is just a wrapper around ICU. There isn't a lot to decide. There isn't a lot of code. There isn't a lot to worry about for support going forward either. I think it would be better for people to stop expressing theoretical concerns for conspiracy and secrecy, maintenance problems, and the like, and look at the code and doc and state precisely and constructively what should be changed, file a bug report against the intl extension and let's move forward. > Can you be specific about which requests you think should still be made? So far the open item > is the naming convention. Is that it? Is this a reply to > > The manual documentation was announced by Stas for review to this list as well on Dec 4. > > > And the changes requested by us still haven't been made. ? If so, the DateFormatter documentation is one thing. File naming convention is another... =========== Tex> what is wrong with the DateFormatter doc? Please submit a bug. Filenaming is being discussed. Personally, I am not convinced there is a problem or a need to change it and in fact I think the current names are better than prefixing the quite extraneous Intl which adds no value and reduces the readability of the code. But if there enough people who feel strongly... Ouh, and btw: Please don't top-post again. That request is stated very clearly in our mailinglist rules. ========= Tex> ugh. -Hannes