How to localize

The modern way to localize the editor UI is the Language property. Set it once and the editor automatically translates every built-in toolbar tooltip, every dialog (Hyperlink, Image, Table, Find & Replace, Spell Check, etc.), every context-menu item, and the spell-check language hint to the chosen culture. No per-label override code is required.

Setting the Language property

The Language property is of type EditorLanguage (an enum living in SpiceLogic.HtmlEditor.Resources.Localization). Assign it from code or set it in the Visual Studio designer property browser.

using SpiceLogic.HtmlEditor.Resources.Localization;



// Switch the entire editor UI to German.

editor.Language = EditorLanguage.German;

Supported EditorLanguage values

The enum currently ships with the following members. Each maps to a .NET culture code and to a matching bundled spell-check dictionary.

Spell-check language

By default the spell checker follows the editor language — SpellCheckOptions.SpellCheckLanguage is set to SpellCheckLanguage.SameAsEditorLanguage, so changing Language automatically selects the matching bundled Hunspell dictionary. Set SpellCheckLanguage explicitly only when you want the spell checker to use a different language than the UI.

using SpiceLogic.HtmlEditor.Abstractions.Entities.SpellCheck;



// German UI, but spell-check the body text in French.

editor.Language = EditorLanguage.German;

editor.SpellCheckOptions.SpellCheckLanguage = SpellCheckLanguage.French;

Custom override (languages the enum does not cover)

If you need a culture that is not in the EditorLanguage enum, or you only want to retranslate a handful of strings, fall back to the per-element override approach the editor has always supported:

• Override individual toolbar button tooltips — see Overriding Toolbar Button Properties.
• Replace the built-in dialogs with your own translated forms — see Replacing the default Dialogs.
• Supply a localized context menu — see Using your own Context Menu.

These hooks remain fully supported and can be combined with the Language property — the per-element override always wins over the bundled translation, so you can ship in (say) German and patch a few specific tooltips with your own wording.