Converter
Last updated
Last updated
While a user has an article open for editing in the Writer, it is represented in the Browser as a collection of nodes with text content and attributes. Everytime the article is to be sent or read from the article repository, it needs to be translated to an XML representation. The XML document structure for an article is well defined by the newsitem-text.xml format specification.
The process of converting to/from nodes and XML is done by Writer, but it takes help from one or many converters. Example of plugins that provide converters are plugins that contribute content to the article text, or add metadata information about the article.
Conversion process from XML document to nodes in Browser
The way to tell Writer that there's a converter to be used for a plugin, is to register it in the package file
for the plugin. Read more about the Package file. In the example below, a plugin with the name plugin
is registering a converter that is defined in the MyPluginConverter.js
file
The converter should contain a function for converting data from XML to Substance Nodes, called import
, and one function for converting from Substance Nodes to XML, called export
. Here's an example where the plugin called myplugin
is adding content to the article, through the object
extension in the writer format. In this example, the plugin implements an object where it is possible to define a question and provide an answer.
The converter can also contain a function matchElement
, to let it know if it's responsible for the current node.
An article example with the plugin1 active could look like: