[wp-hackers] Improving Plugin (and Theme) metadata
kingler at 72pines.com
Fri Feb 8 18:22:56 GMT 2008
I know you can install MO files in the top-level directory, but it
will be a huge mess.
Anyways, the problem you pointed out for the POEdit users will be a
hard one. It does impose extra work for plugin authors when preparing
the PO file. However, Nikolay was saying that it will be easy to do
with shell commands or in a web interface. So I guess an easy web
interface might be able to do the trick for the plugin authors who are
not thrilled with shell commands.
On Feb 8, 2008 10:19 AM, Jennifer Hodgdon <yahgrp at poplarware.com> wrote:
> kingler wrote:
> > First of all, I like the idea of using the gettext translation on the
> > metadata. It requires no extra effort from the plugin author and will
> > be backward compatible. However, one issue I can see is that it would
> > mean that each plugin will need a set of po/mo files, stored in a
> > folder structure. This will force some simple one-file plugin in the
> > folder /wp-content/plugins/ to be organized into subdirectories.
> Actually, even with MO files, you can install the plugin (and its MO
> file or files) in the top-level directory, so that isn't an issue.
> However, there is one issue I can see with this idea of scanning the
> header with a special script: some plugins are internationalized, so
> they already have PO/MO files. Those plugin authors would have to have
> a way of getting the header strings into their main PO/MO files.
> Normally, you use POEdit (or similar software) and tell it to scan the
> files -- it looks for text in __() and _e() PHP functions, not for
> plugin header information.
> Jennifer Hodgdon
> Poplar ProductivityWare * www.poplarware.com
> Web Databases/Scripts * Modeling/Analysis/Palm OS Software
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers