We came up with our own localization framework back in the .NET 2.0 days and we're still using it. Version-numbered translations in an XML file with a simple GU

We came up with our own localization framework back in the .NET 2.0 days and we're still using it. Version-numbered translations in an XML file with a simple GUI to show missing translations, flag out-dated translations, etc. The framework and UI: https://github.com/neosmart/Localization https://github.com/neosmart/Localization Sample translations: https://github.com/neosmart/easybcd-localization https://github.com/neosmart/easybcd-localization Guide and screenshots (that should have probably be also folded into the non-existent readme for the localization toolkit repo): https://neosmart.net/forums/threads/translations-to-other-languages.696/ https://neosmart.net/forums/threads/translations-to-other-la... XML is a drag, but JSON isn't supported without a dependency under .NET Framework and the single-binary NLTUI app masks that from most users. XML also gives nice schema validation, for example look at how simple the validation is in the github action ci for the real-world app example from above: https://github.com/neosmart/EasyBCD-Localization/blob/master/validate.sh https://github.com/neosmart/EasyBCD-Localization/blob/master...