[wp-hackers] Improving Plugin (and Theme) metadata

Omry Yadan omry at yadan.net
Sat Feb 9 11:34:52 GMT 2008

This sounds like a patch feature request for a bigger issue:

what will it take to have

__($str) and _e($str) just work without having to specify the
translation domain?

IE: what if they used the translation of the current plugin automatically?

I suggestion a solution for this 9 months ago here:


be sure to go through the thread mentioned to understand the context of
the proposed solution.

Ozh wrote:

> On Feb 9, 2008 1:53 AM, Ryan Boren <ryan at boren.nu> wrote:
>> and maybe the plugin repo can offer pot generation so that
>> no tool is needed.
> That would be a really cool feature, and yet another incentive for
> people to get hosted.
> My 2 cents feature request: the parser should be able to parse for
> __(), _e() or any custom string. I like to use myplugin__() as an
> alias for __($string, 'myplugindomain')
> Ozh

More information about the wp-hackers mailing list