I would like to provide my own resource string localization for languages not included in the ACT. I have put in a pull request that allows developers to insert their own translations. Can someone please provide feedback?
Comments: Thanks for the update, and again, thank you for taking the time to support this feature. My scenario relies on the built-ins to be served and then the external localization override the built-ins on the client side. Like in my scenario above, I only localize Today but use the built-in localizations for the rest of the resource strings. I'm relying on the built-in resources to be served followed by the external/custom localizations. I realize that may not be the most optimal solutions as I am adding one more resource request. But, I figured, it's just one more small request. The other thing I had in my pull request was the ability to allow external localization for any culture. I did that so I didn't have to specify the cultures I want to provide localizations for since my application supports a lot.
Comments: Thanks for the update, and again, thank you for taking the time to support this feature. My scenario relies on the built-ins to be served and then the external localization override the built-ins on the client side. Like in my scenario above, I only localize Today but use the built-in localizations for the rest of the resource strings. I'm relying on the built-in resources to be served followed by the external/custom localizations. I realize that may not be the most optimal solutions as I am adding one more resource request. But, I figured, it's just one more small request. The other thing I had in my pull request was the ability to allow external localization for any culture. I did that so I didn't have to specify the cultures I want to provide localizations for since my application supports a lot.