Our journey began 18 years ago.

Since then, we have actively maintained and developed this product, listened to customer feedback, and improved it with every release.

518 bugs solved
165 features implemented
30 interfaces improved
136 product releases since 2008
Explore Our Journey Download NuGet Purchase Compare
Latest release

Version 10.3.0

Added a Custom editor language with dedicated translations, English fallback for missing strings, and no changes to existing language or spelling settings.

1 interface change

Interfaces 1

  1. Add EditorLanguage.Custom after the fourteen existing enum values, preserving their numeric identities. Selecting Custom resolves EditorStrings.custom.json from the folder loaded with LocalizationManager.SetJsonOverrideDirectory or AutoDiscoverJsonOverrides. Custom strings are separate from all built-in culture overrides; missing keys fall back to neutral English resources and then the key. SetOverride("custom", key, value) is supported. Custom uses invariant formatting and does not add a spelling dictionary; existing explicit spelling settings remain independent. Existing applications require no migration. New custom translations should select Custom and use the dedicated custom file instead of replacing an English JSON translation. Verified with shared regression tests and actual visible WinForms selection, tooltip, dialog and built-in language switching.