[wp-hackers] Internationalizing Plugins and Themes Solutions

Nikolay Bachiyski nbachiyski at developer.bg
Thu Mar 6 16:56:59 GMT 2008


2008/3/6, Jacob Santos <wordpress at santosj.name>:
> ...
>  Solution #3: Use WP based tool for translating the plugin metadata while
>  in the comment and create a .pot file from that.
>
>  Advantages: Any plugin that is added to the WordPress Plugin Repository,
>  will immediately have translated metadata for which any number of
>  translators can upload translations for. Will also allow for users to
>  download plugin in their language.
>  Disadvantages: While those Plugins on the WordPress Repository will be
>  helped out a great deal, those that exist outside will not. The tool is
>  not something that a novice will be able to wrap their mind around.
>
>  Creating a web interface will be an advantage, but getting the word out
>  about the tool might not reach everyone. Also, they will still have to
>  set up a system like what the WordPress Extend has anyway to support
>  multiple languages. How many will do that?

They can always use the method from #1 -- putting a noop gettext calls
for plugin name and description.

Happy hacking,
Nikolay.


More information about the wp-hackers mailing list