Localization support for separate nuget packages

[Enrico]

What is the suggested way to use the built-in localization for separate nuget packages. I can't find any localization dll inside.

If i would use the big single nuget package the dll for my language is included. By the way, this is not an option to me.

Kind regards,

Enrico

[Yana]

Hi Enrico,

Indeed, currently the localization dlls are not available when using the separate NuGet packages, we will definitely include them either inside the Telerik.Windows.Controls package or as a separate package.
I will write additionally with more details on the exact approach.

Regards,
Yana
Telerik

 

 

[Enrico]

Can you tell something about a possible timeline? 

[Yana]

Hello Enrico,

The localization files will be available as separate NuGet packages starting from our next release - Q2 2014 SP.

Thank you for sending your feedback and sorry for any inconvenience caused.

Regards,
Yana
Telerik

 

 

[Daniel Knoll]

Hi, how can i install the german resources via nuget?

I have installed "Telerik.Windows.Controls.de.for.Wpf" Package (additionally to all my required packages) and set the CurrentUICulture and CurrentCulture to "de". The language is still english. 

Kind regards

[Yana]

Hi Enrico,

When you install the required NuGet packages there is a packages folder created inside your solution folder, so you will need to go inside the Telerik.Windows.Controls.de.for.Wpf.40.2014.2.0729/lib/net40 and copy the de folder ( together with the resource file in it) inside the same folder where Telerik.Windows.Controls.dll is located (it should be Telerik.Windows.Controls.for.Wpf.40.2014.2.0729\lib\net40 ).

Please try it and let us know whether this helps.

Regards,
Yana
Telerik

 

 

[Sven J]

Hi,

there is a description on nuget (https://docs.nuget.org/create/creating-localized-packages) how to define localization nuget packages. Telerik doesn't match these definitions. If you please adapt name and dependency in localized nuget  package it would work out of the box!

Best regards
Sven

[Martin Ivanov]

Hello Sven,

Thank you for the feedback. We will have it in account when we make the planning for our next release.

Regards,
Martin
Telerik

 

 

[Sven J]

Hi,

any progress you can tell us? Version 2015.2 still has problems (=doesn't work) accessing the resource dlls as the resource packages still contains wrong meta-data.

Further suggestion: Remove the Version from the Package Id and use nuget internal Framework-Target-Version. This makes switching to the next .NET Version more easy. 

 

[Martin Ivanov]

Hi Sven,

We already prioritized the tasks for our next release and we weren't able to include this one in our planning. In other words, currently, there is no progress on it. However, we have this task logged in our system and we will implement it as soon as we can.

About the Package Id, thank you for your feedback. Our features/issues log also contains a feature request for possibility to create common package for both framework versions (.NET 4 and 4.5).

Regards,
Martin
Telerik

[Tim]

Hi,

is there a sample project demonstrating this behavior? I have trouble getting my silverlight project translated when using seperate NuGet Packages.

Best regards,

Stefan

[Sven J]

Hi Stefan,

cannot demonstrate my project because it's closed source. But I've made 2 screenshots of my nuget resource package which show how to change the default nuget resource package from telerik to make it work out of the box.

Good luck

Sven

[Tim]

Hi Sven,

thanks a lot for your help. It's really strange that Telerik doesn't provide an out-of-the box solution since this topic is about two years old. Modifying the native NuGet packages will lead to an error prone update process and additional manual work each time I update the Telerik compoenents.

I hope that someone from Telerik staff will write an update about how they will deal with this in the future.

Thanks again for your input!

Stefan

[Kalin]

Hello Stefan,

Thanks for your feedback. We will be get back to you with more details next week.

If you have any other question or concerns, please let us know.

Regards,
Kalin
Telerik

[Kalin]

Hello guys,

Thanks for your patience.

The development team has started working on improving our nuget packages and I can assure you that the feedback from this thread will be considered. Currently I cannot give you a time frame when this will be done, but as soon as we have some more details regarding the estimated release date I will post again in this thread, so please stay tuned.

Hope this helps.

Regards,
Kalin
Telerik

[Kalin]

Hi,

Good news - we are in process of testing the updated localization nugets! The new packages will automatically move the localization dlls into the correct location. They will be live with the next official release (mid September), so stay tuned.

Please do not hesitate to share any feedback as soon as the release goes live and you have checked the new nugets.

Regards,
Kalin
Telerik by Progress

[Daniel]

Hello Kalin,

are there any news on this thread?  The latest version "UI.for.Wpf.45.2019.2.510.nupkg" still does not contain the localized resource files.

Regards,

Daniel

[Daniel]

I just see that previous versions (e.g. UI.for.Wpf.45.2019.1.116.nupkg)  do contain them - but in the latest version 2019.2 they are missing again.

[Kalin]

Hi Daniel,

Thanks for bringing this to our attention.

Actually they have been included since my post, however due to an issue they are missing in the latest 2 releases (R2 and R2 SP). We are working on a fix and they will be available again in one of the next internal builds. 

I will reply back with more details next week. I have updated your Telerik points for your involvement.

Regards,
Kalin
Progress Telerik

[Kalin]

Hi Daniel,

Thanks for your patience. The issue has been resolved and the internal build today will include the missing files, so please give it a try later today.

If you have any other questions or concerns, please let me know.

Regards,
Kalin
Progress Telerik

[Daniel]

Hi Kalin,

the latest build 708 contains the language files again. Thank you.

Regards,
Daniel

[Alexander]

 

...