On 25 Nov, Michael Natterer wrote:
> Well, I don't know how to solve this...
> ...but I'd vote to put the gimp + plugin + perl +
> whatever-is-in-cvs-gimp into _one_ catalog.
Hm, but how would you do this... don't forget that some of the plugins
are built conditionally
> What do you thi
On 24 Nov, Marc Lehmann wrote:
> How do I get the perl menupaths into the gimp .po file? it is no
> problem to mark them, but the standard xgettext program is not able to
> parse perl source.
> Should these go into the gimp-std-plugins-file? Should I put all
> translations into that file then?
Marc Lehmann wrote:
>
> How do I get the perl menupaths into the gimp .po file? it is no problem
> to mark them, but the standard xgettext program is not able to parse perl
> source.
Well, I don't know how to solve this...
> Should these go into the gimp-std-plugins-file? Should I put all
> tra
How do I get the perl menupaths into the gimp .po file? it is no problem
to mark them, but the standard xgettext program is not able to parse perl
source.
Should these go into the gimp-std-plugins-file? Should I put all
translations into that file then?
--
-==-
