Non-localizable controls

[a-sanders]

Hello,
It would be good to have the ability to mark some control as "non-localizable" for the Localizer (GetText.WindowsForms).

Regards.

[perpetualKid]

(admin note)
I've moved that to discussion section (which is new btw) to have further discussion, instead of having that an open issue.
(/admin note)

It would be great to understand the scenario or use case.

[a-sanders]

I noticed that the problem is even wider than I thought. In fact, any TextBox controls will be revert to their original condition after
Localizer.Revert(this, store)
have called. It looks like wrong logic at all.
I guess any user-input controls should not be localized as default.
Does it make sense?

[perpetualKid]

.... BTW, the same way can be applied to specify a list of additional properties for localization, like EmptyListMsg...

that's what I thougth as well, just providing some list of properties (names) to the Localizer. The challenge however is the extractor...

[perpetualKid]

I noticed that the problem is even wider than I thought. In fact, any TextBox controls will be revert to their original condition after
Localizer.Revert(this, store)
have called. It looks like wrong logic at all.
I guess any user-input controls should not be localized as default.
Does it make sense?

I can clearly see where/why this is failing for you.
The typical use case for the forms licalizer is to load localization once (at startup), not to change frequently at runtime.

In your scenario, it might be better to not use the localizer, but only assigned the required localizations manually

label1.Text = catalog.GetString(label1Text);
//textBox1.Text // not translated
etc.

At the very end, the localizer is just encapsulating to iterate all controls and load the translation from catalog.GetString*.
What you are asking is some advanced customization which controls/properties are localized or not.

[a-sanders]

The typical use case for the forms licalizer is to load localization once (at startup), not to change frequently at runtime.

Initially, we are not talking about changing the interface language frequently...

I see at least two possible approaches when the user changes the language by selecting the appropriate language with some control (radio button, combo box, menu, etc) - to require restarting the program or not.
I prefer the second approach whenever possible.

The current logic of the localizer resets controls like text boxes and so I have to ask a user to restart a program or write some workarounds to prevent data loss...

Anyway, I sure the localizer should not touch text box controls because they use for user data input.

[perpetualKid]

"re-opening" ... seeing some more cases where this impacts usability, so will need to think about some improvements. Converting back to issue for now