Exposes the richtext schema indirectly to the filters. It will be accessed via the data processor property of the editor.
Prepares toData transformation.
view fragment to transform
richTextDocument the (empty) document, which shall receive the transformed data;
domFragment the view DOM-structure to transform;
fragmentAsStringForDebugging some representation of domFragment to be used for debugging — it will only
be initialized, if debug logging is turned on.
Registers a module:engine/view/matcher~MatcherPattern for view elements whose content should be treated as raw data
and its content should be converted to a
module:engine/view/element~ViewElement#getCustomProperty custom property of a view element called "$rawContent" while
converting #toView to view.
Pattern matching all view elements whose content should be treated as plain text.
Transforms CKEditor HTML to CoreMedia RichText 1.0. Note, that
to trigger data processor for empty text as well, you have to set the
option trim: 'none' on CKEditor.getData().
fragment from view model to process
CoreMedia RichText 1.0 XML as string
Internal toData transformation, especially meant for testing purpose.
the fragment created from view
OptionaltargetDocument: Documentthe target document, which will get the elements added and will be transformed according to the rules
the transformed CoreMedia RichText XML
Converts the data to a module:engine/view/documentfragment~ViewDocumentFragment document fragment.
The data to be processed.
If the processor is set to use marked fillers, it will insert fillers wrapped in <span> elements
(<span data-cke-filler="true"> </span>) instead of regular characters.
This mode allows for more precise handling of block fillers (so they do not leak into the editor content) but bloats the editor data with additional markup.
This mode may be required by some features and will be turned on by them automatically.
Whether to use the default or marked block fillers.
Data-Processor for CoreMedia RichText 1.0.