On Sat, 2011-01-08 at 12:02 +0700, Ek kian wrote:

i usually modify menu directly from image-menu.xml, but that made menu is broken on other language than English.

what is the right steps to do menu modification so the menu still can be translateable to other language?

The right step is to get your changes upstream. What exactly are you changing and why?

Sven

On Tue, Jan 11, 2011 at 2:15 AM, Ek kian wrote:

i only create new "Photo" menu where consist of many photography related functions,
to speed up our workflow on editing photo rather than jumping around on the menu.

You are maybe better off creating this menu using script-fu. That would allow for very easy deployment in vanilla gimp and woudnt mess anything up. If you use strings that have translations in their original location, you may even get translation working, tho Im not sure how script-fu and localization interact specially in regard to lables. But since the menus do contain localized script names, it should be supported.

On 1/11/11, Alexia Death wrote:

anything up. If you use strings that have translations in their original location, you may even get translation working, tho Im not sure how script-fu and localization interact specially in regard to lables.

Checboxes and suchlike in FX Foundry scripts dialogs are partly translated, because some messages ara translated in po-script-fu/*.po.

Alexandre Prokoudine http://libregraphicsworld.org

On Tue, 2011-01-11 at 15:36 +0300, Alexandre Prokoudine wrote:

On 1/11/11, Alexia Death wrote:

anything up. If you use strings that have translations in their original location, you may even get translation working, tho Im not sure how script-fu and localization interact specially in regard to lables.

Checboxes and suchlike in FX Foundry scripts dialogs are partly translated, because some messages ara translated in po-script-fu/*.po.

Why doesn't FX Foundry install its own po files in its own translation domain? Script-Fu has support for registering an additional translation domain.

Sven

On 1/13/11, Sven Neumann wrote:

Why doesn't FX Foundry install its own po files in its own translation domain? Script-Fu has support for registering an additional translation domain.

Because you said it was impossible :)

http://www.mail-archive.com/gimp-developer@lists.xcf.berkeley.edu/msg19130.html

And Kevin agreed :)

Alexandre Prokoudine http://libregraphicsworld.org

On Fri, 2011-01-14 at 01:42 +0300, Alexandre Prokoudine wrote:

On 1/13/11, Sven Neumann wrote:

Why doesn't FX Foundry install its own po files in its own translation domain? Script-Fu has support for registering an additional translation domain.

Because you said it was impossible :)

http://www.mail-archive.com/gimp-developer@lists.xcf.berkeley.edu/msg19130.html

And Kevin agreed :)

Um, sorry. Somehow I was under the impression that it should work. But you are right, it's supported for plug-ins but not (yet) for Script-Fu scripts.

Sven

Sven Neumann wrote:

Um, sorry. Somehow I was under the impression that it should work. But you are right, it's supported for plug-ins but not (yet) for Script-Fu scripts.

Are translations enabled on all plug-ins? What about for Python scripts?

Having taken a look at a plugin just after I wrote those initial questions I remember we talked about adding a _ function (or something like that) so that Script-Fu would have a way to mark strings for translation allowing for getenv(?) to be called during runtime.

On Tue, 2011-01-18 at 00:29 -0500, Kevin Cozens wrote:

Sven Neumann wrote:

Um, sorry. Somehow I was under the impression that it should work. But you are right, it's supported for plug-ins but not (yet) for Script-Fu scripts.

Are translations enabled on all plug-ins? What about for Python scripts?

Python scripts are full-fledged plug-ins and can use the framework that exists for GIMP plug-ins. There's API to register a translation domain and this allows third-party plug-ins to install their own message catalogs.

Having taken a look at a plugin just after I wrote those initial questions I remember we talked about adding a _ function (or something like that) so that Script-Fu would have a way to mark strings for translation allowing for getenv(?) to be called during runtime.

Script-Fu has that already (and it's gettext that gets called, or actually dgetext). However so far the message is translated in the standard script-fu translation domain so this doesn't work for third-party scripts.

Sven