Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 9215 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
After I installed an update I found that the user interface language had been reset to german (I have my region settings set to german under Windows 7). I was unpleasantly surprised by this behavior after I initially installed MonoDevelop.
I was doubly surprised to see the update override my original installation settings, causing me to have to spend time trying to find out where the UI language setting was hidden, rather than doing some useful work.
It is a good installation behavior to let the user set the UI Language to what they want, not to set it automatically to something inferred from a very weak indicator of what it might need to be.
Most products I use don't do this, for good reason.
I can repro this. I'm pretty sure it's a bug in gettext. I tried to work around it by setting LANGUAGE, LC_MESSAGES, LC_ALL env vars, but that didn't work. Nor did temporarily assigning CurrentUICulture to CurrentCulture while initializing gettext - as soon as I switched it back, gettext picked up the change.
It looks to me like libintl is using GetThreadLocale for all categories, but it should be using GetThreadUILanguage for the LC_MESSAGES category:
This should be a pretty easy fix but I have no idea how we're building our GTK+ stack on windows.
Cody, isn't this already fixed?