Serialize and Deserialize Content
The Editor component allows you to configure and apply custom definitions for serializing and deserializing its content.
Serializing
The Editor provides the following configuration options:
-
Entities()—Indicates whether the characters outside the ASCII range will be encoded as HTML entities. By default, they are encoded (true). -
Scripts()—Indicates whether inline scripts will be serialized and posted to the server. By default, scripts will be removed (false). -
Semantic()—Indicates whether the font styles will be saved as semantic tags (strong,em,span) or as presentational tags (b,i,u,font). By default, the Editor uses semantic tags (true). -
Custom()—Allows you to define custom serialization for the editable content. The JavaScript handler will receive the Editor content and will return its serialized version.
@(Html.Kendo().Editor()
.Name("editor")
.Serialization(s => s
.Entities(true)
.Scripts(true)
.Semantic(true)
.Custom("serializeHandler")
)
)
<script>
function serializeHandler(html) {
return html.replace(/(<\/?)b(\s?)/, "$1strong$2");
}
</script>
Deserializing
Deserialization is the process of parsing the HTML string input from the value() method or from the viewHtml dialog into editable content. The deserialization configuration method allows you to use a custom JavaScript handler, as demonstrated in the following example.
@(Html.Kendo().Editor()
.Name("editor")
.Deserialization(ds => ds
.Custom("deserializeHandler")
)
}
<script>
function deserializeHandler(html) {
return html.replace(/(<\/?)b(\s?)/, "$1strong$2")
}
</script>