[wp-hackers] wordpress.org *.pot file feature for plugins gets broken by PoEdit
Stephen Rider
wp-hackers at striderweb.com
Sun Jul 19 15:37:53 UTC 2009
Am I correct in thinking this would only work if the plugin is
active? This info needs to work for inactive plugins too. Also it
seems to require double-entry of data, which to me is a bad idea.
Stephen
On Jul 19, 2009, at 8:54 AM, Heiko Rabe wrote:
> ...
> This dissenting message entry creation is not standardized and won't
> work with normal gettext pasing applications.
> There should be introduced a safe way this can also be handled by re-
> scanning with gettext applications, otherwise this feature is
> worthless.
> One option would be a section of code only for purpose of getting
> this right by gettext processors like:
>
> function my_plugin_data($plugin_data) {
> $plugin['Name'] => __('....', 'custom-field-images'),
> $plugin['Title'] => __('....', 'custom-field-images'),
> $plugin['PluginURI'] => __('....', 'custom-field-images'),
> $plugin['Description'] =>__('....', 'custom-field-images'),
> $plugin['Author'] => __('....', 'custom-field-images'),
> $plugin['AuthorURI'] => __('....', 'custom-field-images'),
> $plugin['Version'] => __('....', 'custom-field-images'),
> $plugin['TextDomain'] => __('....', 'custom-field-images') ,
> $plugin['DomainPath'] => __('....', 'custom-field-images')
> return $plugin_data;
> }
> add_filter('wp_plugin_data-' .'custom-field-images',
> 'my_plugin_data');
More information about the wp-hackers
mailing list