Re: Fwd: Re: [PHP-DEV] Woah
Zeev Suraski wrote: Ken - see my point? :) I have seen it all along. I just do not think that removing it is better than leaving it forever but discouraging it. And you cannot say that 'ugliness is not a metric' for anyone except yourself. Multiple people have brought that aspect up, so obviously it matters to *them*. Please do not dismiss those inputs unless you think they do not count, in which case I suppose we should just accept that you are inflexible and consider your opinion better than anyone else's. :-D -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ All right everyone! Step away from the glowing hamburger! -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Fwd: Re: [PHP-DEV] Woah
Ken - see my point? :)
Andrei - ugliness is not a metrics, anymore than disappointment is. Fact -
gettext(foo) is much less magical and much more understandable than _(foo).
Date: Sat, 8 Sep 2001 10:45:53 -0500
From: Andrei Zmievski [EMAIL PROTECTED]
To: Zeev Suraski [EMAIL PROTECTED]
Cc: Chuck Hagenbuch [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Woah
On Sat, 08 Sep 2001, Zeev Suraski wrote:
Again, by deprecating it now, the immediate action would be removing any
reference to it from the documentation (the very little there is). There
are a hell of a lot PHP users to come than there are existing users of
PHP,
so we might as well limit the scope of the problem. We can also advertise
that this function will not be staying with us in the future, and that
people should use gettext() instead. We can add an E_NOTICE to it, which
would make fixing it a trivial single command. When we actually remove
this
alias can be determined in the future.
To me personally, gettext('This is my string') is a lot uglier than
_('This is my String'). I think _() could be made an exception to the
function-naming rule.
-Andrei
Give a man a fish; you have fed him for today. Teach a man to fish;
and you can sell him fishing equipment.
-Author unknown
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: Fwd: Re: [PHP-DEV] Woah
On Sun, Sep 09, 2001 at 12:46:17AM +0300, Zeev Suraski wrote: Fact - gettext(foo) is much less magical and much more understandable than _(foo). I think the problem here is that internationalization is being considered a 'separate module', rather than a core piece of functionality that PHP should account for. Right now, wrapping _() around EVERY string is only the first step. Then you have to figure out how .po files, bindtextdomain, various environment variables, and all the other stuff that gettext imposes on the system actually work. So where have the PHP ideals disappeared to in simplying this? This whole _() argument is merely a symptom of the underlying problem that internationalizing PHP scripts is really actually quite difficult and intrusive. Fix that, and this particular problem goes away. If you really believe that deprecating _() is a good thing in the context of using gettext, I find it hard to believe that you've actually implemented i8n in PHP for a large project. Personally, I've only used it when Horde switched to it, and I think I'd go mad if I had to wrap every string in the full version of gettext() ! The GNU manual expresses this pretty well: the textual overhead per translatable string is reduced to only three characters: the underline and the two parentheses When we're talking about every single string in your project, that's pretty significant. Anil -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
