by Michael S. Kaplan, published on 2007/09/22 09:41 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/09/22/5055160.aspx
The purpose of marking properties in WinForms as localizable is to make sure that properties that localizers would posisbly need to change can be exposed to them.
All well and good, but it is easy to miss properties that are in retrospect obvious ommissions.
Like just the other day when Kollen mentioned:
We are in the process of localizing for Spanish and noticed that the DropDownWidth property on the ComboBox is not showing up in WinRes so we are unable to resize drop-downs to accommodate longer Spanish items.
While the work around is to subclass, override the property and add the attribute, that can be difficult especially since this probably wouldn't get noticed by teams until they start the localization process after code freeze.
Kollen is completely right, and it is an obvious ommission that will hopefully be addressed in some future version of WinForms....
I'll talk more about the general issue another day (I have to get to Shul now, sorry!).
This post brought to you by ͅ (U+0345, a.k.a. COMBINING GREEK YPOGEGRAMMENI)
go to newer or older post, or back to index or month or day