Von: Anke Lange

These are just little thinks, but I ask myself, if there are two different languagepacks for linux and for windows and if I could help with this somehow.

I don't see any English menu entries in 2.8.0 on Windows, except for third-party scripts and plug-ins - and that is expected.

HTH, Michael

On Tuesday, May 29, 2012, 13:25:21, Michael Schumacher wrote:

I don't see any English menu entries in 2.8.0 on Windows, except for third-party scripts and plug-ins - and that is expected.

There's a problem with Python scripts on 64bit Windows currently - they always appear in English.

Von: "Jernej Simončič"

On Tuesday, May 29, 2012, 13:25:21, Michael Schumacher wrote:

I don't see any English menu entries in 2.8.0 on Windows, except for third-party scripts and plug-ins - and that is expected.

There's a problem with Python scripts on 64bit Windows currently - they always appear in English.

Some of these scripts seem to include untranslated strings.

HTH, Michael

On Tuesday, May 29, 2012, 14:47:53, Michael Schumacher wrote:

Some of these scripts seem to include untranslated strings.

It happens even with those that have translations.

On 12-05-29 08:13 AM, Jernej Simončič wrote:

There's a problem with Python scripts on 64bit Windows currently - they always appear in English.

Is that due to a bug in pygimp or in some 64-bit version of a library (ie. gettext) used by pygimp?

On Tuesday, May 29, 2012, 17:42:23, Kevin Cozens wrote:

Is that due to a bug in pygimp or in some 64-bit version of a library (ie. gettext) used by pygimp?

Neither - PyGimp on Windows is always 32-bit, so I suspect it's looking for translations relatively to the 32-bit DLL directory.

Anke Lange wrote:

I have come across some differences in the translation of Gimp into German. For example:

The palettes kontex-menue, on the linux, everything is in German. On windows, there is still some english.

Hi Anke,

I just tried with 2.8 on Windows and everything is in German.

On the gradient-dialog, on Windows you can open a new picture, on Linux the translation is correkt.

You're right. This is confusing for two reasons: 1. 'open' and 'new' are two different things. 'New' means to create something not yet existing, while 'open' expects anything that's already there.
2. Hovering over the second icon in the button bar at the dialogs bottom I read 'Ein neues Bild erstellen'. First, it's very unexpected to create a new _image_ from a _gradient_ dialog, second it opens the gradient editor dialog. So, it should be 'Einen neuen Farbverlauf erstellen'. The en_us translation is right: 'Create a new gradient'. This simply seems to be an error in German translation.

Could your Windows regionale and language settings be wrong and cause this mixture? I read of a similar problem with Portuguese and English (see
http://sourceforge.net/projects/gimponosx/forums/forum/761056/topic/3454274) and the reason were wrong system settings.

Trying to reproduce this behaviour I found another confusing item: in the gradient context menu there is an item 'Save as CSS...' in the German translation. Selecting it opened an English dialog for the underlying Python script (I have a 32-bit Windows). I guess both still need to be translated. Shall I report a bug for this?

Best regards,

grafxuser

On 12-05-29 11:55 AM, Jernej Simončič wrote:

Neither - PyGimp on Windows is always 32-bit, so I suspect it's looking for translations relatively to the 32-bit DLL directory.

If a person wants to compile GIMP for 64-bit why is pygimp still only 32-bit? Known compatability issues? No one has gotten around to testing 64-bit? Or could it be as simple as no one has bothered to update the build method for pygimp?

It seems odd to me to mix 32-bit and 64-bit in parts of a program that all come out of the same source tree.

On 31 May 2012 12:53, Kevin Cozens wrote:

On 12-05-29 11:55 AM, Jernej Simončič wrote:

Neither - PyGimp on Windows is always 32-bit, so I suspect it's looking for translations relatively to the 32-bit DLL directory.

If a person wants to compile GIMP for 64-bit why is pygimp still only 32-bit? Known compatability issues? No one has gotten around to testing 64-bit? Or could it be as simple as no one has bothered to update the build method for pygimp?

It seems odd to me to mix 32-bit and 64-bit in parts of a program that all come out of the same source tree.

Last I checked, there is no native PyGTK+ for Windows 64bit, due to the fact the binary signatures used by GCC in win 64 (used in gobject, gtk+) and visualstudio (used for Python) are different.

I do not use Windows, and have no idea if this has changed. Since pyGIMP works as an off-process plug-in, if it works, it is the way to go, because there would not be a feasible work-around.

I intend to research and update pygimp to use gobject introspection during gimp 2.9 - maybe that can allow for a 64bit version of it on Windows.

(It is important to note that such problems do not happen under Linux - and that there are other problems due to not using gobject introspection under mac os x)

js ->

--
Cheers!

Kevin.

On Thu, May 31, 2012 at 1:55 PM, Joao S. O. Bueno wrote:

On 31 May 2012 12:53, Kevin Cozens wrote:

On 12-05-29 11:55 AM, Jernej Simončič wrote:

Neither - PyGimp on Windows is always 32-bit, so I suspect it's looking for translations relatively to the 32-bit DLL directory.

If a person wants to compile GIMP for 64-bit why is pygimp still only 32-bit? Known compatability issues? No one has gotten around to testing 64-bit? Or could it be as simple as no one has bothered to update the build method for pygimp?

It seems odd to me to mix 32-bit and 64-bit in parts of a program that all come out of the same source tree.

Last I checked, there is no native PyGTK+ for Windows 64bit, due to the fact the binary signatures used by GCC in win 64 (used in gobject, gtk+) and visualstudio (used for Python) are different.

I do not use Windows, and have no idea if this has changed. Since pyGIMP works as an off-process plug-in, if it works, it is the way to go, because there would not be a feasible work-around.

I intend to research and update pygimp to use gobject introspection during gimp 2.9 - maybe that can allow for  a 64bit version of it on Windows.

(It is important to note that such problems do not happen under Linux - and that there are other problems due to not using gobject introspection under mac os x)

  js  ->

--
Cheers!

Kevin.

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Not true. This was one of the reasons that I started my own builds. In my build, Python is 64-bit.

Partha

On 31 May 2012 19:19, Partha Bagchi wrote:

On Thu, May 31, 2012 at 1:55 PM, Joao S. O. Bueno wrote:

Last I checked, there is no native PyGTK+ for Windows 64bit, due to the fact the binary signatures used by GCC in win 64 (used in gobject, gtk+) and visualstudio (used for Python) are different.

  js

Not true. This was one of the reasons that I started my own builds. In my build, Python is 64-bit.

Partha

I am glad to know that --
so it is a matter of configuring the Windows builds.

js ->

On 12-06-01 07:34 AM, Joao S. O. Bueno wrote:

On 31 May 2012 19:19, Partha Bagchi wrote:

Not true. This was one of the reasons that I started my own builds. In my build, Python is 64-bit.

[snip]

I am glad to know that --
so it is a matter of configuring the Windows builds.

It would be a good idea to create a bug report in bugzilla about this so it doesn't get forgotten. Either that, or someone who knows what needs to be done can just go ahead and fix it or provide a patch to fix it.

On Friday, June 1, 2012, 16:37:59, Kevin Cozens wrote:

It would be a good idea to create a bug report in bugzilla about this so it doesn't get forgotten. Either that, or someone who knows what needs to be done can just go ahead and fix it or provide a patch to fix it.

The official PyGTK+ site doesn't have Win64 binaries. They are available in the OpenSuSE repo, but right now I'm using Python from www.python.org in my installer.

Hi,

I just wanted to butt in here:

On 29.05.2012 19:02, gfxuser wrote:

Could your Windows regionale and language settings be wrong and cause this mixture? I read of a similar problem with Portuguese and English (see
http://sourceforge.net/projects/gimponosx/forums/forum/761056/topic/3454274) and the reason were wrong system settings.

The thread indicates a problem with Gimp and specifically with the locale fallback logic, not a configuration error.

It is not an error to just specify a language without a region. The locale fallback should *never* produce a language mix with a third language (German in the thread). It should use the default fallback language, which should be English (probably US English).

Portuguese (BR) should fall back to Portuguese, which in turn falls back to default.

So either the GIMP translations for Portuguese regions were never properly made -- so there in fact is *no* Portuguese version and just Portuguese regional versions, which is a *mistake* -- or the fallback mechanism is simply misbehaving on MacOS.

You should check the latest version of Gimp and see if this error still occurs, then file a bug report.

Regards,

Robert Abel

On Fri, Jun 1, 2012 at 12:20 PM, Jernej Simončič wrote:

On Friday, June 1, 2012, 16:37:59, Kevin Cozens wrote:

It would be a good idea to create a bug report in bugzilla about this so it doesn't get forgotten. Either that, or someone who knows what needs to be done can just go ahead and fix it or provide a patch to fix it.

The official PyGTK+ site doesn't have Win64 binaries. They are available in the OpenSuSE repo, but right now I'm using Python from www.python.org in my installer.

-- < Jernej Simončič ><><><><>< http://eternallybored.org/ >

You are right of course. I use python from python.org as well. However, I just went ahead and built my own pygtk+. :)