[Padre-dev] localizing plugin documentation

[Adam Kennedy]

I can't think of any Perl/CPAN project that has ever tried to do i18n
at this level of depth, so I'm not too worried about us just trying
something, and having some false starts.

That said, might be interesting to ask around and see if anyone else
has managed to implement anything similar.

I wonder if we could just get away with something like

Padre/Plugin/Foo.pm
Padre/Plugin/Foo/PT.pod

That said, would doing things via POD make life unusually difficult
for the translators?

The solution that encourages contributions by making it as easy as
possible to do the translation is probably worthwhile targeting as the
first attempt.

Adam K

2009/4/29 Jerome Quelin <jquelin at gmail.com>:
> hi,
>
> now that we can localize plugins, i definitely think that plugin manager
> should display a localized documentation on the right pane, instead of
> just the plugin pod.
>
> especially if we decide to translate the plugin name and the plugin menu
> entry.
>
> to achieve this, i can imagine that we extend the plugin api with
>
>    plugin_documentation()
>
> which would return a hash:
>    author      => 'A. U. Thor <foo at example.com>',
>    description => Wx::gettext(...),
>    how_to_use  => Wx::gettext(...),
>    copyright   => 'Copyright (c) ...',
>    license     => Wx::gettext('You can redistribute this plugin ...'),
>    etc.
>
> (or whatever fields, i don't really care)
>
> and plugin manager would then display this.
>
> if no plugin_documentation() method is found, then the html-ized pod
> would be displayed instead, just as is done currently.
>
> note that it might be a good idea to allow html in the hash values, to
> allow plugin author to pimp up its doc. but in this case, i don't know
> how translators will cope with this.
>
> ==> wdyt?
>
> jérôme
> --
> jquelin at gmail.com
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>