WPFLocalizeExtension slow to start #431
Unanswered
whitelined
asked this question in
Q&A
Replies: 1 comment
-
Hello, @whitelined. Please check Startuptime for Available Cultures Search with Resx Provider. (LocalizeDictionary.Instance.DefaultProvider as ResxLocalizationProvider).SearchCultures =
new List<System.Globalization.CultureInfo>()
{
System.Globalization.CultureInfo.GetCultureInfo("de-de"),
System.Globalization.CultureInfo.GetCultureInfo("en"),
System.Globalization.CultureInfo.GetCultureInfo("he"),
System.Globalization.CultureInfo.GetCultureInfo("ar"),
}; If I don't mistake, localization engine doesn't have other reliable ways to understand all supported cultures. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Got a WPF windows application for a plugin. When I started developing the app all worked perfectly until I started using WPFLE. The app still works fine, but WPFLE is adding nearly 4-5 seconds to display the window initially - if I close the window and re-open it's quicker, but it's that initial slow start-up that's the problem. I read somewhere that it could be where WPFLE is trying to preload every culture info and associated resource? could that be the case to the problem? If so, any plans to perhaps dynamically load only what's needed rather than load the everything?
One of the suggestions I saw was modifying ResxLocalizationProviderBase, roughly between 525-533, and force the locals you've only used, which could work, it is a bit of hack that will work, but it is a hack all the same.
Regards
Aaron
Beta Was this translation helpful? Give feedback.
All reactions