 DTD based filtering of imported and pasted content edit-on Pro will automatically validate any content imported, pasted or exported against the XHTML Transitional DTD. Depending on the configuration, the editor will perform a cleanup on the document and remove any attributes and elements not allowed according to the DTD. The integrator can even override the default clean-up processes with server side or client side custom clean-up processes. This feature allows a company to control the content created within its web-based application and IT systems. At no time are the users/authors able to create content which is not XHTML compliant or does not fulfill the company's content guidelines. This will secure your investment in "future-proof" content. Support of Cascading Style Sheets (CSS)
Extension of the XHTML DTD with custom XML tags edit-on Pro guarantees XHTML compliance according to W3C standards through validation against the XHMTL 1.0 Transitional DTD. However, the editor also supports custom XML tags. In order to avoid the editor's internal DTD based clean-up process to remove such custom XML tags, the tags can be declared within the Transitional DTD. It is also possible to include an own DTD, which declares the custom XML tags within the editor's Transitional DTD. Custom elements/tags can be defined as XHTML inline elements, block level elements or empty elements without any content as place holders. For more information see also the Custom DTD Sample Enhanced custom element/tag usage and rendering via CSS To ease and enforce content editing, developers can entirely control the usage and rendering of XHTML/XML custom elements/tags via CSS, including:
For more information see also Extension of the XHTML DTD with custom XML tags Template-based publishing through CSS based read-only elements and areas
Using CSS the integrator can specify certain areas/parts of a document as read-only content, which can not be modified by the editor of the document. For example, editing actions such as typing, deleting, changing the font size etc. executed on read-only content or on a selection overlapping it is ignored. Read-only elements can not be removed from a document. However, the content within a read-only element may be modified by the user. For example, when users are not allowed to remove certain parts of the document, such as news headlines, but are allowed to edit them, the integrator can utilize read-only elements. This unique feature allows the integrator to define document templates, which can be used to enforce corporate design and content guidelines while facilitating document editing. A pre-selection of templates could be offered to the users through customized toolbar buttons, dialogs, pull-down or context menus. You can check this feature online within our Custom DTD Sample Optional cleaning of Microsoft Word content When copying/pasting content from Microsoft Word or other sources, a clean-up process is invoked. Depending on the configuration, the editor will perform a clean-up on the document and remove any attributes and elements not allowed according to the XHTML Transitional DTD. The integrator can even override the default clean-up processes with server side or client side custom clean-up processes. Real-time character counting and document size limiting
|
|
This feature allows the integrator to limit the document size respectively restrict the number of characters the user can enter into a document. The limitation and the actual number of characters entered is shown through an indicator field within the editor's status bar.
|
|
|
|
||||||||||||||||||||||||
