RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

i18n in an external pack of scripts

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.
i18n in an external pack of scripts Alexandre Prokoudine 16 Nov 21:54
  i18n in an external pack of scripts Sven Neumann 16 Nov 22:14
   i18n in an external pack of scripts Alexia Death 17 Nov 09:20
Alexandre Prokoudine
2009-11-16 21:54:59 UTC (about 15 years ago)

i18n in an external pack of scripts

Hi,

Supposing there is a somewhat popular bunch of scripts distributable as one package. If I get it right, to make them translatable I would have to:

1. Somehow set package name for gettext that follows a particular scheme, e.g. 'gimp20-my-pack-of-scripts'. Requires a proper build environment perhaps (recommendations?).

2. Create po/POTFILES.in and a PO file (for testing purposes first).

3. Somehow make GIMP understand that it has to load gimp20-my-pack-of-scripts.mo files.

Step 2 is a no-brainer, but how do I do 1 and 3?

Alexandre

Sven Neumann
2009-11-16 22:14:29 UTC (about 15 years ago)

i18n in an external pack of scripts

On Mon, 2009-11-16 at 23:54 +0300, Alexandre Prokoudine wrote:

3. Somehow make GIMP understand that it has to load gimp20-my-pack-of-scripts.mo files.

For a plug-in this is easy. The plug-in would have to make sure that it calls the gimp-plugin-domain-register procedure. A Script-Fu script however runs in the Script-Fu interpreter and can't do this. As long as Script-Fu doesn't provide support for internationalisation of third-party scripts, there is no way to do what you are aiming for.

Short answer: forget about Script-Fu and use Python instead.

Sven

Alexia Death
2009-11-17 09:20:33 UTC (about 15 years ago)

i18n in an external pack of scripts

On Mon, Nov 16, 2009 at 11:14 PM, Sven Neumann wrote:

On Mon, 2009-11-16 at 23:54 +0300, Alexandre Prokoudine wrote:

3. Somehow make GIMP understand that it has to load gimp20-my-pack-of-scripts.mo files.

For a plug-in this is easy. The plug-in would have to make sure that it calls the gimp-plugin-domain-register procedure. A Script-Fu script however runs in the Script-Fu interpreter and can't do this. As long as Script-Fu doesn't provide support for internationalisation of third-party scripts, there is no way to do what you are aiming for.

Short answer: forget about Script-Fu and use Python instead.

Can we haz a long answer? Because porting entire FX foundry to python is not feasible. Perhaps the script-fu component can be altered.