Le 30/05/2010 20:09, Enrico Tröger a écrit :
Committed now to SVN.
Hey, that's cool! Thanks for committing :)
Regards,
Colomban
___
Geany-devel mailing list
Geany-devel@uvena.de
http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Fri, 14 May 2010 18:03:13 +0200, Enrico wrote:
Hi,
Hum, more seriously: I already tried (by using direct gettext calls)
and yes -- I would say of course -- it works fine. Even better, you
succeeded to make me hack Geany in order to implement it directly
(see attached patch) and yes
On Tue, 11 May 2010 00:54:36 +0200 (CEST), Colomban wrote:
On Mon, 10 May 2010 00:12:47 +0200 (CEST), Colomban wrote:
Hi,
I just wondered why my plugin's name and description wasn't
translated since every other part of my plugin was. But a little
thinking made me realize it's
Hum, more seriously: I already tried (by using direct gettext calls)
and yes -- I would say of course -- it works fine. Even better, you
succeeded to make me hack Geany in order to implement it directly
(see attached patch) and yes again, it works well (and don't need so
much code change
And finally, on the thread I see that you (global) say that when
the plugin gets loaded, the name and description are translated?
I don't
I think this is true only for plugins shipped with Geany itself as
those use Geany's gettext domain.
Well… for them, why wouldn't they
On Mon, 10 May 2010 00:12:47 +0200 (CEST), Colomban wrote:
Hi,
I just wondered why my plugin's name and description wasn't translated
since every other part of my plugin was. But a little thinking made me
realize it's completely normal: of course bindtextdomain() wasn't
already called for
