[wp-hackers] Improving Plugin (and Theme) metadata
peter.westwood at ftwr.co.uk
Fri Jan 25 18:46:06 GMT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Jennifer Hodgdon wrote:
| Peter Westwood wrote:
|> Jennifer Hodgdon wrote:
|> | As long as the plugin puts in its own text domain name, why would
|> | calling __() pollute the main catalog?
|> The call to __($variable_name) in the WordPress code will end up with
|> $variable_name in the catalogue AFAIK.
| Yeah, we already established you can't use variable names. The plan
| would be:
| Description: My great plugin that you need.
| (rest of header)
| $mydomain_desc = __("My great plugin that you need.", "mydomain" );
| Again, how will that pollute anything?
That code is fine from a plugins catalog point of view.
The problem is code like this is the current patch on #3089:
$description = __(trim($description), $text_domain);
This would be in the core WordPress code - and so the text within the
__() call would end up in the WordPress catalogue
http://blog.ftwr.co.uk | http://westi.wordpress.com
~ C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the wp-hackers