During the process of localization, I'm struggling with the translation work of the Infragistics resource strings. I believe that the current situation imposes developers unnecesary extra boilerplate work and, what's worst, requiere us to pay translators for strings that our final users will never see.

Last week, I suggested Infragistics some alternatives to solve these problems for which they assigned the Feature Request Number FR12470. I proposed three things:

• Split or categorize the resources strings for each assembly in two subsets: runtime and designer mode. It's a burden cost to pay for translations of strings like the ones that are showed under the WinGrid Designer and a crazy work to cherrypick which ones go in and which don't.
• Provide downloadable files for such string resources in a suitable format (HTML it is *not*). CSV, RESX or any other ASCII format with a previously defined order will do. Hence, it will let us save them under a version control system and we would quickly know of any content change whenever Infragistics publish a new release.
• Add an iterator to the ResourceCustomizer API for the runtime subset of strings. Then we can safely call SetCustomizedString with a known string name and ignore or log an error if that name is not found in our CurrentCulture resources.

Did you face with these problems before? Do you find the proposal reasonable or do you have other ideas?

I think this is important because, unlike any other UI enhacement of the library with an abstract value, the impact of this request can be meassure in real money.

Regards,
-Hernán.

[Admins: Move this thread if you consider that this forum is not the correct one]