Just installed Bluefish for the first time. Using macOS 10.15 (Catalina) and installed it through brew cask.
For some reason the GUI is all in Dutch. I guess this is because I'm currently located in the Netherlands. However I'm not Dutch and my macOS is not Dutch either.
And I have been going through all the preferences but can't find a language option anywhere.
How do I fix this?
hmm we've done a lot of work to get the language from the OSX settings, but obviously this is not working on Catalina.. Are there any dutch settings left in your OSX language settings? I don't have a Mac so I can't reproduce it.
In the preference at "User interface" you can manually change the language.
Thanks for your fast reply. I'm not sure, I think I may have Netherlands as my location somewhere in my macOS settings. My macOS language is certainly not Dutch though.
This happens sometimes with other software as well, I notice how default language and location are often linked, or language assumed from location.
Anyway I have now found the option to change the language, however it is currently on "Automatisch" (Auto) and there are no other options?
Here's a screenshot of that setting with the options menu opened:
Last edit: Snæfríður Friðleifsdóttir 2020-04-25
Interface language is decided based on settings in System Preferences -> Language & Region.
There are settings of "Preferred Languages" and "Region". Could you tell what you are having here?
Bluefish should be at first looks in Preferred languages list, selecting top one on the list. If this is not available, then it selects one in Region.
Thanks, Preferred languages is English, Region is Netherlands:
Well, it seems detection is not working as expected. Could you try to set Region to USA or England, and then restart Bluefish?
I have noticed, that dialog now has "Apps" tab that probably would allow to configure language for each application. This is new feature, it is not present on my 10.14 Mojave. Could you check if Bluefish is available here and try to configure needed language?
Is there any new info on this? Or has it been solved? If no new info is made available, the ticket will be closed. Since some code updates have happened in the meantime, a new ticket would be wise if the problem occurs again.