Cannot make pt-BR Localization work

Sure!

using System;
using System.Globalization;
using System.Resources;
using System.Threading;
using Wisej.Web;

namespace Localization
{
	public partial class Window1 : Form
	{
		public Window1()
		{
			InitializeComponent();
		}

		private void Window1_Load(object sender, EventArgs e)
		{
			SetValues();

			// get notified when the browser is refreshed.
			Application.ApplicationRefresh += Application_ApplicationRefresh;
		}

		void Application_ApplicationRefresh(object sender, EventArgs e)
		{
			SetValues();
		}

		private void comboBox1_SelectedIndexChanged(object sender, EventArgs e)
		{
			// refresh the browser using the new language.
			string[] languages = {"auto","en","de", "it", "fr", "es", "pt-BR"};
			Application.Navigate(Application.StartupUri.ToString() + "?lang=" + languages[this.comboBox1.SelectedIndex]);
		}

		private void SetValues()
		{
			this.labelNumber.Text = 12345678.ToString("c");
			this.labelCurrency.Text = 12345678.ToString("c");
			this.labelDateTime.Text = DateTime.Now.ToString("F");

			var loAssembly = this.GetType().Assembly;

			var RS1 = new ResourceManager("Localization.Resources", this.GetType().Assembly);
			this.Text = RS1.GetString("Title");
			this.button1.Text = RS1.GetString("ShowMessageBox");

			var lcCancel = RS1.GetString("$Cancel");
			var lcShowMessageBox = RS1.GetString("ShowMessageBox");

			var lcCulture = Application.CurrentCulture;

			MessageBox.Show("The buttons are localized", buttons: MessageBoxButtons.YesNoCancel, modal: false);
		}

		private void button1_Click(object sender, EventArgs e)
		{
			CultureInfo ci = new CultureInfo("pt-BR");
			var RS2 = new ResourceManager("Localization.Resources", this.GetType().Assembly);
			var lcCancel = RS2.GetString("$Cancel", ci);
			var lcShowMessageBox = RS2.GetString("ShowMessageBox", ci);

			var lcCulture = Application.CurrentCulture;

			MessageBox.Show("The buttons are localized", buttons: MessageBoxButtons.YesNoCancel, modal: false);
		}
	}
}

The MessageBox in the SetValues shows the Message Buttons properly localized.
On the other hand, the MessageBox in the button1_Click doesn’t. Using the ResourceManager within this Click works properly if I force the CultureInfo, otherwise, it doesn’t.
I tested the Thread.CurrentThread.CurrentCulture inside it and it was properly set as “pt-BR”.

The default language in my Dev machine and in the Google Server is English already.

But, I have a feeling you are on the right track here… In the Control Panel Region, I had (and have to have it) Portuguese (Brazil) as the “Format”, which gives us the right Currency, numbers, dates formats. The Google Servers are also set for this Format. I changed my Dev machine to English (United States) and all worked fine. So, maybe the ResourceManager is not really using the Thread.CurrentThread to get this setting, I would bet.

ResourceManager uses the Thread.CurrentThread.CultureInfo. All of .NET localization uses the thread’s culture.

The question is why it fails for you and not for any other machine we tried including azure servers.

Can you check or change the default language on your server to en-US? However I guess that google’s vm is already en-US. In which case it must be a deployment issue.

Can you send the code you just tried and loaded the wrong resource for you?

Some more info.

If I force the CultureInfo to be used by the ResourceManager GetString method inside the button click, it finds the strings properly, but still shows the MessageBox with the generic/wrong content.

			CultureInfo ci = new CultureInfo("pt-BR");
			var RS2 = new ResourceManager("Localization.Resources", this.GetType().Assembly);
			var lcCancel = RS2.GetString("$Cancel", ci);
			var lcShowMessageBox = RS2.GetString("ShowMessageBox", ci);

If I don’t mention the CultureInfo and let the ResourceManager use what it considers to be the current culture, it fails. But Application.CurrentCulture shows pt-BR inside the button click properly. So, I guess ResourceManager is getting the CultureInfo from somewhere that is not set after the trip to the server.

Thanks Luca, here are the results:

1 – I removed the bin/pt, but as soon as I run the sample, it gets automatically created back.

2 – Added the code. the ResourceManager doesn’t seem to be able to find the strings in the pt-BR resource file. However, the Application.CurrentCulture still returns pt-BR as the current culture.

I have also tried renaming pt-BR to pt, no luck.

Then, I thought of putting a MessageBox inside the SetValues method, which runs whenever ApplicationRefresh is triggered. And it works fine from there. (!)

Right after I see it working there, once I click on the button to show the MessageBox that is coded in it, it doesn’t work anymore, and Application.CurrentCulture still returns pt-BR properly, but the strings from its resource file are not correct, apparently coming from a generic resource as if it didn’t find the pt-BR resource file.

Try this on a dev machine:

1. Remove the bin/pt directory and leave only the bin/pt-BR

2. Add code in the button click that shows the message box that uses a ResourceManager to read the localized strings you added: $ok, etc. and check the name of Application.CurrentCulture.

I will send you a different test app to check what is loaded.

The ResourceManager class in .NET is the one loading the resources. Wisej is not doing anything other than using it to read the localized strings. It’s all part of standard .NET.

There may be a collision between /pt and /pt-BR.

You can also try to rename your localized assembly to be pt instead of pt-BR.

Hi Luca.

There is something really weird from my side, I am sure. Just can’t think of what could be.
Yes, the DLL is deployed to the Google Cloud server, I have attached a picture.

The warnings are normal.

I simply clicked Publish in VS and published this:

https://wisejlocalization.azurewebsites.net/

Make sure that /bin/pt-BR/Localization.resources.dll is deployed.

Hey Levie.

Happy New Year!

So, I turned all Common Language Runtime Exceptions on but nothing was thrown when I changed the Localization.
Yes, I have tried on a completely different environment, you might have missed it, but I deployed it to a Google Cloud VM where you can try yourself (http://pfnwj.test.profilme.net), also had the MessageBox labels not translated.
I had a look at the Console on Chrome and noticed the warnings once I clicked on the button to show the MessageBox. I have attached a picture. However, I am not setting any theme to this test application.
Any thoughts?

Hi Levie.

This is really strange. I might have a haunted machine on my desk. 😀
I’m on Wisej 2.2.25.0. I have attached a picture and you can see the buttons. Also, I have a different icon for the message, is it a different Theme you are using? I have also restarted my machine, just in case… I am drawing a blank here.

Hi Ivan,

I just ran the sample you provided using the latest version of Wisej and it seems to be working ok. It uses the localization file you created and placed in the root directory. I attached an image of the outcome.

What version of Wisej are you using?

Best,

Levie