Your assemblies contain dozens of resource strings that shoudl be localized when localizing my Silverlight application. Unfortunately because of .NET signing this taks is not easy. There are many localization tools that can easily make a localized satellite assembly files. For example if I want to localize Telerik.Windows.Controls.dll into German I use my localization tool to create de\Telerik.Windows.Controls.resources.dll. This is the standard way to localize .NET applications.
Unfortunately because all Telerik assemblies are signed the localized satellite assemblies but be signed too in order to use them. What you should do is to make your key file public for localization purposes. That way user can sign the satellite assembly files and localization would turn a lot easier.
What you provide now is far from perfect. Because key is not ppublic your have written your own propiertary LocalizationManager class that use used to override the default English string. Of cource this works but it way too complicated. First I have to make my own .resx that contains the same items as your original Telerik.Windows.Controls.Strings resources. There are dozes of strings and it will take a lot of time to create the resx. Once I have the resx I have to add a line of code to override the original resources. All this is a waste of time and what is more important it is not the standard way to localize .NET applciation The standard way is the create a satellite assemblies for each assemblies that contain resources.
There is an easy solution for this: release you key file (.snk) so we can use the standard way to localize Silverlight application using your nice controls.
Regards,
Jaska
Unfortunately because all Telerik assemblies are signed the localized satellite assemblies but be signed too in order to use them. What you should do is to make your key file public for localization purposes. That way user can sign the satellite assembly files and localization would turn a lot easier.
What you provide now is far from perfect. Because key is not ppublic your have written your own propiertary LocalizationManager class that use used to override the default English string. Of cource this works but it way too complicated. First I have to make my own .resx that contains the same items as your original Telerik.Windows.Controls.Strings resources. There are dozes of strings and it will take a lot of time to create the resx. Once I have the resx I have to add a line of code to override the original resources. All this is a waste of time and what is more important it is not the standard way to localize .NET applciation The standard way is the create a satellite assemblies for each assemblies that contain resources.
There is an easy solution for this: release you key file (.snk) so we can use the standard way to localize Silverlight application using your nice controls.
Regards,
Jaska
2 Answers, 1 is accepted
0
Hi Jaska,
Actually when using a custom LocalizationManager you do not break the built in Telerik resources, you only extend them. In other words you will have to write only the localization strings that you want to add or override. You can find a sample project demonstrating this.
Having in mind the purposes for using a .snik file I don't think that we can provide it.
Regards,
Ivo
the Telerik team
Actually when using a custom LocalizationManager you do not break the built in Telerik resources, you only extend them. In other words you will have to write only the localization strings that you want to add or override. You can find a sample project demonstrating this.
Having in mind the purposes for using a .snik file I don't think that we can provide it.
Regards,
Ivo
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
YLS
Top achievements
Rank 1
Rank 1
answered on 20 Aug 2012, 03:48 PM
Hi Jaska,
I agree with you that using a localization tool to translation Telerik resources is much more standard, convenient and efficient, especially for a big project and multiple languages.
Using LocalizationManager requires a lot more work for each language, and it makes it harder for someone who's not a developer.
Regards,
Yalei
I agree with you that using a localization tool to translation Telerik resources is much more standard, convenient and efficient, especially for a big project and multiple languages.
Using LocalizationManager requires a lot more work for each language, and it makes it harder for someone who's not a developer.
Regards,
Yalei