Andrew KeepCoding

Thanks for the suggestion. I guess there are 2 considerable options here: 1. Add `l:Uids.Target`: ```xaml ``` 1. Make it work within `l:Uids.Uid`: ```xaml ``` This was actually suggested a...

I'm not sure if I can find time to consider and implement this anytime soon. 😵

I don't understand. If you have access to the target element, you should be able to localize strings. The new feature about extending the `x:Uid` is a different thing. Can...

By the way, you can still use the WinUI3Localizer in your markup extension: ```cs [MarkupExtensionReturnType(ReturnType = typeof(string))] public class LocalizedString : MarkupExtension { public string Key { get; set; }...

@Pietro228 In order to keep consistentcy with `x:Uid`, I'm afraid I'm going to go with the 3rd option which is leave it as it is. I hope you understand.

Reopening this for v3.

Sorry for the delay. I just published v2.3.0-alpha. Can you give it a try if it works for your requirements? (Make sure to check the **Include prerelease** checkbox.)

Thanks @Pietro228 ! Now I just need to make time for v3.🙂

Hi @viktor-bov! Thanks for trying out the WinUI3Localizer. I created a sample app [here](https://github.com/AndrewKeepCoding/WinUI3LocalizerCalendarDatePickerSampleApp). You can see how to localize the days of the week there. Each month comes with...

Sorry for taking too much time. I found some weird behavior trying to localize the YearViewPanel (the panel where you select months). Besides the YearViewPanel the sample app should work.