[wp-hackers] i18n of plugin description

[Stefano Aglietti]

On Thu, 24 Jan 2008 16:28:49 +0100, "Ozh" <ozh at planetozh.com> wrote:

>>Another solution would be to place only the English description in the 
>>plugin header and the foreign descriptions in a single file and parse 
>>this file. This would keep the header clear
>
>I like this solution. It keeps the header simple and readable.
>
>By the way you'd need to be able to translate the plugin description of 
>course, but also its name, and why not its URL for the (numerous) folks 
>who maintain their custom plugin doc in more than one language.

+1

This is the simplest solution, it's fully backward compatible, the
external file, if not created by authours that doens't care for I18N
(on plugins are lot less than in theme where 98% of theme are not
I18N) could be created by locale team, and as you said if the plugin
in locale is mantained in other sites these should be inserted in
locale translations.

The only problme I see about having alternative URL is version
management done by last WP version, i can have the XYZ plugin on my
locale site translated in italian at version 1.0 using this locale
version show up that there is a new version available but the one
people will download wont be the locale one (if exist) but an updated
version in english. It's true that plugin developper on worpress
repository often care a lot theyr products, managing locale version if
you send it to them etc.

-- 

Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431
Email: steve at 40annibuttati.it steagl at people.it
Sites: http://www.40annibuttati.it (personal blog)
       http://www.wordpress-it.it (WordPress Italia)