After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 771951 - gimp-2.8.18-x86_64 UI is in Sanskrit, not English
gimp-2.8.18-x86_64 UI is in Sanskrit, not English
Status: RESOLVED DUPLICATE of bug 770708
Product: GIMP
Classification: Other
Component: User Interface
2.8.18
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-09-25 18:17 UTC by bobby.fritze
Modified: 2016-10-29 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The UI and Preferences panel of GIMP 2.8.18 in a totally random language than the default user language. (160.14 KB, image/jpeg)
2016-09-25 18:17 UTC, bobby.fritze
Details
Correspondance with English preferences (183.78 KB, image/jpeg)
2016-09-26 11:51 UTC, Jehan
Details

Description bobby.fritze 2016-09-25 18:17:55 UTC
Created attachment 336229 [details]
The UI and Preferences panel of GIMP 2.8.18 in a totally random language than the default user language.

Running OS X El Cap 10.11.6.
Just installed GIMP 2.8.18.

Everything is in Sanskrit (I believe); it looks similar to Thai.

I tried opening the package contents and modifying the file "GIMP inside the folder "MacOS" by adding:
     export LANG=en_US.UTF-8
before the final exec line but I must have done it wrong because that didn't work.

Right now 2.8.18 is totally useless.

The documentation is $#!† too (https://docs.gimp.org/en/gimp-fire-up.html)
My OS language is already on English.
The user shouldn't have to run CLI commands just to be able to read the &@ç#ing preferences and dialogs.

Good job sending more customers away to Adobe.
Comment 1 Jehan 2016-09-25 21:53:43 UTC
Looks as it may be the same issue as bug 770708 (and possibly bug 769843). Apparently for some reason in OSX, GIMP would grab the second language in your list.

Is your second language in the OSX preferences Sanskrit by any chance?
Comment 2 bobby.fritze 2016-09-25 22:03:17 UTC
Hi Jehan, thanks for checking this.
I double checked System Preferenceso > Language & Region > Preferred Languages and English is the Primary; there are no others.

Do you happen to know any Terminal commands I could try to address this locally?

Also please excuse my frustration and profanity :/
Comment 3 Jehan 2016-09-25 22:17:54 UTC
> Hi Jehan, thanks for checking this.

I won't personally since I have no OSX machine. But we have a OSX dev aware of the issue. Hopefully he will find some time to fix it soon.

> Do you happen to know any Terminal commands I could try to address this locally?

As a workaround, you can simply select the language you want in GIMP preferences. Apparently the language bug happens with the default ("System Language" maps to the wrong language for some yet unknown reason on OSX), but if you explicitly specify another lang, it will work (according to other users' report).

This language list should be available in the second section in your screenshot (the "Interface" section, see the screenshot there to map to your preferences in Sanskrit: https://docs.gimp.org/fr/gimp-pimping.html#gimp-prefs-dialog). There select "English" explicitly and you'll be fine. :-)

If you absolutely need a command line rather than settings through the GUI, "normally" running GIMP like this should work:

> LC_ALL=en_US.UTF-8 gimp-2.8

But since I don't know the root of the bug, maybe it won't and I can't test because (as I said) I have no OSX machine. In Linux at least, that would work.

> Also please excuse my frustration and profanity :/

It's all right. :-)
Comment 4 Michael Schumacher 2016-09-25 22:22:55 UTC
We went through some questions on Twitter, btw: https://twitter.com/bobbyfritze/status/780101867133022209
Comment 5 Jehan 2016-09-25 22:23:11 UTC
If you confirm that the workaround works for you (through the preferences dialog is probably the easier), I think I will just mark this bug as a duplicate of bug 770708, which I think is the same.
Comment 6 bobby.fritze 2016-09-25 22:47:06 UTC
I have no idea what to click on in the Prefs panel to change language though. And I think modifying the package contents did not work b/c I did it wrong or b/c I had to open the file as text and maybe it didn't save correctly/ in the same encoding but idk.
Comment 7 Jehan 2016-09-26 11:51:36 UTC
Created attachment 336260 [details]
Correspondance with English preferences

I don't speak this language as well, which is why I showed you the English GUI for correspondence. So I attach a new image where I circled the right spot in your first screenshot to make it correspond to the English one. I hope it's clearer now. :-)

Also if you absolutely prefer the script version, and if setting "LANGUAGE" instead of LANG (as I told you on twitter) does not work, you should be able to get English by setting at least "LC_ALL=C". This should disable localization (and since the default is US English, by disabling localization, you would get what you want).
Comment 8 Michael Schumacher 2016-09-26 12:45:38 UTC
We still don't know what the environment really looks like, btw - e.g. the output of the env command.
Comment 9 bobby.fritze 2016-09-26 20:29:02 UTC
Thanks for the screenshot Jehan. However when I open that panel, all the options in the drop down menu still display I'm Sanskrit, so it's tough to tell which to choose to switch to English.

I have not yet tried modifying the file in the Package Contents, but will provide documentation of it once I do so. Thanks
Comment 10 bobby.fritze 2016-09-26 20:29:34 UTC
Thanks for the screenshot Jehan. However when I open that panel, all the options in the drop down menu still display I'm Sanskrit, so it's tough to tell which to choose to switch to English.

I have not yet tried modifying the file in the Package Contents, but will provide documentation of it once I do so. Thanks
Comment 11 Michael Schumacher 2016-10-29 11:11:27 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 770708 ***