[wp-hackers] Internationalizing plugin meta-data...

[Samuel Bortle]

Hey Jen,

I am new on this list and don't know much about WordPress yet(except, of
course that it is awesome!)

take a look at [ http://svn.automattic.com/wordpress/trunk/wp-includes/pomo/]

I hope this is what your looking for. For some reason these are not in my
local install of wp, which i thought was the bleeding-edge-2.8. do not all
files get exported from svn? I thought i read something about a no export
list. not sure. as i said, i am still a noob.

If this is what your looking for, make sure to update the docs on the site
to make note of this.

On Mon, Mar 16, 2009 at 7:33 PM, Jennifer Hodgdon <yahgrp at poplarware.com>wrote:

> I'm trying to follow the instructions in
> http://codex.wordpress.org/I18n_for_WordPress_Developers for how to get
> the plugin meta-data into my plugin's POT file, for a plugin that is not in
> the repository.
>
> This involves running a PHP file
> http://svn.automattic.com/wordpress-i18n/tools/trunk/makepot.php
>
> That file doesn't run, though... First, there's a required file
> "not-gettexted.php", which isn't mentioned in the instructions -- this is
> not a huge deal, as it could be downloaded from the same location.
>
> However, that second file requires "pomo/po.php" and "pomo/mo.php". Neither
> of those is in evidence. Where can I get these? And are there any other
> files required by these includes that I would need? And does this script
> work once the required files are there? Has anyone tested it?
>
> Thanks,
>   Jennifer
>
> ps: I don't think this discussion belongs on the Polyglots mailing list.
> This is an issue for all plugin developers, as every plugin should be
> internationalized, whether the author wants to provide translations or not.
>
> --
> Jennifer Hodgdon * Poplar ProductivityWare
> www.poplarware.com
> Drupal, WordPress, and custom Web programming
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>