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

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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[1] = __(trim($description[1]), $text_domain);

This would be in the core WordPress code - and so the text within the
__() call would end up in the WordPress catalogue

westi
- --
Peter Westwood
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

iD8DBQFHmi5uVPRdzag0AcURAhYfAJoC93VLpwvT1w0X0d1k1F7ZdMIRXwCdH4JI
RApTikPErMY578sKNmqeRO4=
=mAxO
-----END PGP SIGNATURE-----