Hi,

On Wed, 2006-06-28 at 01:20 -0300, Joao S. O. Bueno Calligaris wrote:

(http://bugzilla.gnome.org/show_bug.cgi?id=346001)

I consider this both sad and grave. IMHO, the build of python-fu by default, and support for it under Redmond OS is one of the greatest things in this development cycle.

Huh? I never suggested that the build of Python-Fu should be disabled or anything like that. I am only suggesting that it doesn't install any of its example plug-ins that don't serve any particular purpose but being examples for plug-in authors. Such plug-ins can very well be in the source tree, but they must not show up in the menus.

I will undertake i18n of the python-fu then, with no delays.

It's a bit late now to add another translation domain. I think this should wait for 2.6.

What else
do you consider important for the UI to have for it to keep up with gimp standards?

Have a look at one of the Python-Fu dialog windows. Any further questions?

Sven

Hi,

I have opened a bug report on what I believe to be the remaining issues with gimp-python:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

Even though I said earlier that's it's perhaps too late for adding i18n support, I feel now that we absolutely need to do this if we want to install any Python plug-ins by default.

But still, if i18n support is added, the usefulness of the plug-ins should be reviewed and only the plug-ins that are considered useful should be installed and have their strings marked for translation (and reviewed).

Sven

Moin,

Regarding http://bugzilla.gnome.org/show_bug.cgi?id=351287 some progress has been made in CVS. To avoid i18n problems, the procedure registration in pygimp has been changed (in a hopefully backwards compatible way). It shouldn't be too difficult to add i18n now. But still, there hasn't been any further progress on this. We urgently need this to happen so that we can enter string freeze. Any volunteers?

Sven

Hi,

the internationalisation of the Gimp Python bindings and plug-ins is still pending:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

Does this mean that noone is interested in having the existing Python scripts in GIMP 2.4? It should not be difficult to make the plug-ins use the existing gettext module for Python (http://docs.python.org/lib/module-gettext.html) and that's basically all that needs to be done.

Perhaps someone can look over the strings in the meantime and make sure that there are no typos or other errors?

Sven

Hi,

On Wed, 2006-09-13 at 10:31 +0200, Sven Neumann wrote:

the internationalisation of the Gimp Python bindings and plug-ins is still pending:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

We have come a good deal further here in the meantime. The framework for internationalisation is now in place. What's missing is the review of the strings (basically the same job as what's needed for Script-Fu, only much fewer strings) and marking them for translation. Any volunteer who wants to go over the python plug-ins, check that the strings are OK and that the procedure blurbs have the same style as what is used by the plug-ins? The files to look at are (from the plug-ins/pygimp/plug-ins folder):

clothify.py
colorxhtml.py
foggify.py
happy-valley-relief.py
palette-offset.py
palette-sort.py
palette-to-gradient.py
pdbbrowse.py
py-slice.py
shadow_bevel.py

This list does intentionally leave out plug-ins that are already internationalized or are not installed in a stable release and are only included as examples.

Sven

Hi,

On Sun, 2006-09-17 at 15:51 +0200, Sven Neumann wrote:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

In the meantime, while Carol is trying to steal your time with pointless mails, the Python i18n effort is basically done. It would be nice if someone could review the strings that have been marked for translation. I would like to point translators to the new set of translatable messages soon and they would probably appreciate if the strings would not have to be changed before 2.4.

Sven

Hi,

On Fri, 2006-09-22 at 00:16 +0200, Sven Neumann wrote:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

In the meantime, while Carol is trying to steal your time with pointless mails, the Python i18n effort is basically done. It would be nice if someone could review the strings that have been marked for translation. I would like to point translators to the new set of translatable messages soon and they would probably appreciate if the strings would not have to be changed before 2.4.

Should we consider the messages as fine then?

Sven

On 10/5/06, Sven Neumann wrote:

In the meantime, while Carol is trying to steal your time with pointless mails, the Python i18n effort is basically done. It would be nice if someone could review the strings that have been marked for translation. I would like to point translators to the new set of translatable messages soon and they would probably appreciate if the strings would not have to be changed before 2.4.

Should we consider the messages as fine then?

Does reviewing mean that someone goes through scripts, marks forgotten messages and err... unmarks those that should not be translated?

Alexandre

Hi,

On Thu, 2006-10-05 at 11:36 +0400, Alexandre Prokoudine wrote:

Does reviewing mean that someone goes through scripts, marks forgotten messages and err... unmarks those that should not be translated?

Sure, I might have forgotten a message or two. But the main point of such a review is that someone else, preferably a native speaker, looks over the messages and checks them for spelling and grammatical errors. The easiest way to do this is by looking at the gimp20.pot file in the po-python directory.

Sven