[Padre-dev] localizing plugin documentation

[Jerome Quelin]

On 09/04/29 17:34 +1000, Adam Kennedy wrote:
> 2009/4/29 Jerome Quelin <jquelin at gmail.com>:
> > that's also my concern: gettext has the nice side effect that
> > translators are not looking up the code, but their translating tools
> > that they know.
> >
> > and let's not even mention the problem of "has the pod changed since
> > last time, and where?"
> 
> The main thing I worry about with this, is when exactly is all this
> content loaded into memory, and how much is the cost of it going to
> be.

well, this will only be loaded when opening the plugin manager and
selecting the plugin to enable it. once plugin manager window is closed,
memory is released.

> You can imagine if something like Padre::Plugin::Catalyst gets large
> and has a lot of features. While they can hide a lot of the
> functionality down in child packages that get loaded late, all of the
> (potentially large) manual  is going to be compiled into memory all
> the time... and then copied when it's returned to the plugin manager.

of course, there's the modules size question.

> And we could easily end up paying this cost even when the plugin is
> disabled.
> 
> If we made some kind of guideline that the description field should
> link out to a large manual, then THAT has to be in POD and we're back
> where we started...

indeed. i don't have any miracle thoughts, especially since i'm no l10n
master and don't know that much this topic.

jérôme 
-- 
jquelin at gmail.com