Features
XStandard: Powerful features. Steered by standards.
This table lists the principal features of XStandard Lite and XStandard Pro, with explanatory screen shots. Hyperlinks lead to additional information, with convenient jumps back to the table. Please contact us if you have any questions.
XStandard Features| Feature | Lite | Pro | See It | Notes |
|---|
| Runs in browser-based content management solutions |  | |  | Internet Explorer, Firefox, Safari and Opera. |
| Runs in desktop-based content management solutions | | | | Use XStandard wherever ActiveX controls are supported (Visual Basic, Visual C++, Access, Visual Studio.NET, Delphi, FoxPro, etc.). See App Integration in this documentation for more details. |
| Generates clean XHTML (Strict or 1.1) with no deprecated markup. | | | | Why XHTML 1.1 is important. |
| Supports most CSS 2.1 selectors | | | | Supported CSS 2.1 selectors |
| A genuine XHTML editor, not an HTML 4 editor with code clean-up routines. | | | | Most WYSIWYG editors are just JavaScript wrappers around the editing control built into many browsers such as the MSHTML control found in Internet Explorer. These types of editor (which generate HTML 4 and then run code clean-up routines against it) have significant limitations. By contrast, XStandard is built from the ground up to be a true XHTML editor in its own right. |
| XHTML generated by XStandard can be parsed by XML parsers. | | | | Use off-the-self XML technologies like DOM, SAX and XSLT to further process markp generated by the editor. You CMS can do this before content is saved to the database or in a batch process. |
| Uses Cascading Style Sheets (CSS) for formatting. | | | | XStandard uses external or embedded CSS to ensure data is never fused with formatting. |
| Makes applying CSS quick and easy | | | | Applying the correct formatting is fast and accurate using XStandard's drop-down "Styles" menu that generates the markup that references CSS. User-friendly style names speed the authoring process. |
| Uses Web Services not FTP for file uploading |  | | | Web Services are superior to FTP because they handle metadata and offer tighter integration with content management systems. |
| Easy-to-use interface | | | | XStandard's streamlined interface speeds the authoring process and makes applying complex formatting easy. |
| Configurable toolbar | | | | Show / hide / move the buttons on XStandard's toolbar. |
| Customizable toolbar | | | | Change icons to match the look-and-feel of your own applications. Move frequently used styles to the toolbar. Program buttons to insert code snippets, or use your own buttons to extend XStandard's functionality. |
| Available in 21 languages | | | | Language versions include: English, French, German, Spanish, Chinese, Dutch, Italian, Russian and Czech. |
| Creates new language versions easily. | | | | Easily modify or create new localizations (language versions) of XStandard's interface. |
| Manages content in any language | | | | Author content in multiple languages (including Chinese, Russian, Greek, etc.). |
| Imports third-party data | | | | XStandard's "Directory" feature communicates with third-party applications (such as your CMS) and allows users to insert data from external sources directly into the editor. |
| Cleans Microsoft Word | | | | XStandard retains structural elements when pasting from Word (lists, tables, hyperlinks, images, headings, etc.), but strips out proprietary Microsoft Office tags and inline formatting. |
| Has a multi-lingual spell checker and custom dictionary | | | | Spell check in English (US, Canadian, British), German, Danish, Spanish, French, Italian, Dutch, Norwegian, Portuguese and Swedish. Add unusual spellings or frequently used abbreviations to a custom dictionary. |
| Enables locking of content (read-only) | | | | |
| Ability to add markers to content | | | | Markers are text labels that can apply short, informative messages to elements of content. For example, they can be used to flag areas of editable or read-only content. |
| Supports subdocuments | | | | Subdocuments are chunks of reusable content that authors insert into documents as required. Subdocuments are essentially custom elements that act as placeholders for content stored outside the document, within the CMS. |
| Supports popular table editing options. | | | | Editing options include splitting / merging cells, aligning cell contents (right / left / center / top / middle / bottom), inserting / deleting rows, columns and tables, etc. |
| Ability to draw tables by dragging | | | | |
| Supports bullets and numbered lists | | | | |
| Supports authoring definition lists | | | | XStandard is one of the few editors that supports authoring definition lists. XStandard also has unique features that make authoring defintion lists easier, including the ability to sort items in the list. |
| Supports the correct use of block quotes | | | | Most editors use <blockquote> for indenting which is wrong. XStandard encourages the correct use of <blockquote> for quotations only, and uses CSS for indenting. |
| Supports inline quotes | | | | XStandard is one of the few editors that support the <q> element. |
| Wraps text around images and other objects | | | | Uses the standards-compliant CSS float property to wrap text neatly around images and objects. |
| Inserts images using direct URLs | | | | Use absolute or relative URLs for image paths. |
| Cursor stays in sync when switching between Edit and View Source modes | | | | |
| Ability to save an image from the editor to the desktop | | | | |
| Supports drag & drop of image files directly into the editor, as well as file browsing | | | | Drag images from the desktop into the editor. Images will be uploaded to the server. Browse image files on the local computer or in remote libraries. Set limits on file size and type. |
| Permits entire folders to be dragged directly into the editor | | | | Uploaded folders are automatically zipped and a hyperlink created to the zipped file. |
| Inserts custom tags | | | | XStandard makes it easy for business users to add semantic meaning to text and objects by inserting custom tags. |
| Automatically inserts image metadata | | | | Metadata attached to image files in libraries browsed by XStandard is automatically captured when images are selected. This includes alt text, long descriptions and titles. |
Supports semantic markup tags like <abbr>, <acronym>, <dfn>, <kbd>, <samp>, <code>, <cite>, etc. | | | | Inserts semantic tags that render markup meaningful to visual and non-visual browsers. |
| Meets or exceeds regional accessibility standards for code output | | | | The editor's standards-compliant markup meets or exceeds accessibility requirements: Section 508 (USA), CLF (Canada), etc. |
| Distinguishes between data and layout tables | | | | Maintains the important distinction between data and layout tables, which are processed differently by assistive technologies such as screen readers. |
| Distinguishes between decorative and informative images | | | | XStandard makes it easy to ensure that informative images are used in a semantically meaningful way. |
| Offers a rich API for extending the editor's functionality | | | | Extend the functionality of XStandard through custom programming to meet the unique needs of your content management system. |
| Includes a unique "Screen Reader Preview" | | | | The accessibility button on XStandard's toolbar opens the Screen Reader Preview that helps authors further optimize content for accessibility. |
| Collapsible/expandable editor window via toolbar button | | | | Collapsing the editor permits a more economic use of screen real estate, while permitting authors to expand the editor when in use. The editor can be expanded to a full-screen view, or customized to snap open to any size. |
Notes
Why XHTML Strict / 1.1 is important
XStandard's prime role is to ensure that non-technical authors using free-form (WYSIWYG) editing areas always generate clean XHTML Strict or 1.1. This is because only XHTML Strict and 1.1 guarantee the clean separation of data from formatting, making them the clear choice whenever availability of data is an important factor. The separation of data from formatting is achieved in XStandard by using Cascading Style Sheets (CSS) for styling content. The screen shot in this section of the Features table shows clean XHTML 1.1 generated by XStandard. Purged of "noise" elements such as deprecated tags, font sizes, colors and unfinished markup, data is preserved in a "raw" state that makes it suitable for parsing and re-purposing by any XML-enabled device or application.
Supports most CSS 2.1 selectors
- Universal selector
- Matches the name of any element. For example:
* {margin:0;padding:0} - Type selector
- Matches the name of a given element. For example:
h1 {color:red} - Descendant selector
- Matches an element that is the descendant of another element. For example:
h1 em {color:red} - Child selector
- Matches an element that is the direct child of another element. For example:
p > q > strong {color:red} - Adjacent sibling selector
- Matches an element, given an element that immediately precedes it. For example:
h1 + p {margin-left:40px} - Attribute selector
- Matches elements that have certain attributes. For example:
a[title] {color:red} - Class selector
- Matches elements given a class value. For example:
em.important {color:red} - ID selector
- Matches an element with a given ID. For example:
#chapter1 {color:red}
Limitations of HTML 4 editors running code clean-up routines
While XStandard is designed to directly produce clean, accessible XHTML Strict or 1.1, without the use of code clean-up routines, most other WYSIWYG editors are in fact the MSHTML control found in Internet Explorer with some type of wrapper built around it. These editors generate HTML 4 and then run clean-up routines to "sanitize" the "dirty" code that the MSHTML control created. At best, the outcome is XHTML 1.0 Transitional (not Strict). Unfortunately, XHTML 1.0 Transitional includes significant negative characteristics inherited from HTML 4. For developers, one of the most significant disadvantages of XHTML 1.0 Transitional is that it permits the fusing together of data and formatting that makes parsing and re-purposing content so difficult.
Uses External or Embedded CSS for formatting
Unlike the <font> tag or inline CSS used in the (now deprecated) style attribute, external or embedded CSS cleanly separate data from formatting. This creates format-neutral data that is ideal for content sharing. It also makes changing the look and feel of Web sites easy, requiring only a few simple modifications to the appropriate CSS.
XStandard makes applying the correct CSS quick and easy
Authors apply CSS by choosing formatting options from the editor's drop-down Styles menu. Each style in the menu generates markup that references an appropriate CSS. Since developers can attribute friendly, meaningful names to each style (for examle, "Chapter Heading" or "Sale Price"), authors find it easy to recognize and apply the right formatting to the right content. Styles in the menu can also be grouped together for greater convenience, and the choice of styles will typically reflect the type of document being edited. For authors, these features make applying CSS an intuitive and comfortable experience that results in high levels of compliance with presentation standards.
The advantages of using Web Services
- Web Services can be easily customized to meet the unique needs of different content management systems, whereas FTP lacks the programmatic hooks necessary for processes that require tighter integration. For example, requiring uploaded files to be stored directory in a database, pushed through a workflow process, or modified in some way before being saved to the server.
- Today's applications also require more metadata that FTP is able to provide. For example, when uploading a file, Web Services can also supply the CMS with information such as the name of the document the file is associated with, the Session ID, which user uploaded the file, etc.
- Some corporate networks also do not permit FTP, so Web Services that run over HTTP are an ideal solution.
XStandard's easy-to-use interface speeds the authoring process
XStandard's streamlined toolbar is a refreshing alternative to the dizzy array of toolbar buttons seen in most WYSIWYG editors. Toolbar clutter is caused by requiring authors to build formatting piecemeal, using tools such as color, font and style pickers. Building formatting piecemeal is time-consuming and prone to error. Tools such as font and color pickers also lack any semantic capability. They can stipulate how content should appear, but offer no way of attaching any additional meaning to content. By contrast, XStandard's intuitive Styles menu makes it easy to choose the correct formatting option, and can apply sophisticated formatting combinations in a single style. The use of CSS (each style in the menu generates markup that references an appropriate CSS) also permits unlimited semantic meaning to be attached to any piece of content.
A configurable and customizable toolbar
Both versions of XStandard permit toolbar icons to be hidden, displayed or moved to different positions on the editor's toolbar. XStandard Pro also has a customizable toolbar that allows developers to change the appearance of toolbar icons to match the look-and-feel of applications XStandard runs in, or to move frequently used styles off the drop-down Styles menu and onto the toolbar. Buttons can also be programmed to insert code snippets into the editor, or to extend the editor's functionality in other ways.
Easily create new language versions of XStandard's interface (localization)
Since XStandard stores its localization data in an independent XML file, XStandard's (21) standard interface languages can be easily modified (reworded), or entirely new language versions of XStandard can be created.
Imports third-party data
XStandard's "Directory" service is a timesaving feature that communicates with third-party applications, such as CMS. It allows users to import external data from those applications directly into the editor. Content imported in this way might include staff listings, product numbers and descriptions, or indeed any type of centrally stored information in any structure (tables, email addresses, etc.)
Cleans MS Word
When content from Word is pasted into XStandard, the editor retains essential structural elements such as paragraphs, tables, bullet points, headings, hyperlinks, images, etc. However, proprietary, non-compliant markup used by Word to apply formatting is suppressed. Users replace formatting quickly and easily using XStandard's intuitive "Styles" menu. Styles create markup that references CSS, replacing the non-compliant markup found in Word with clean, standards-based code.
Supports drag & drop of images directly into the editor, and file browsing
Images can be dragged directly into XStandard from the desktop. Restrictions can be set on file size or type, and the dimensions of uploaded images are automatically calculated. XStandard ensures that images are used correctly by requiring images to be identified as "decorative" or "informative", and requiring alt text for the latter.
Inserts custom tags that add semantic meaning to text and objects
Custom tags allow business users to attach semantic meaning to elements of content during the authoring process. Custom tags can subsequently be used for indexing data, or for optimizing search results in enterprise-level search engines. They can also serve as placeholders for dynamic content. In the example below, a custom tag acts as a placeholder for the latest stock price:
- The current stock price is $<stock exchange="NASDAQ">INTL</stock>.
At run time this gives the result:
- The current stock price is $31.49.
Automatically inserts image metadata
When users select images from libraries browsed through XStandard, if an image is pre-populated with metadata (such as alt, title, longdesc), then the <img> tag in XStandard automatically captures that metadata. This saves time and ensures that metadata for images remains consistent.
Supports semantic markup used by visual and non-visual browsers
Semantic tags ensure that non-visual browsers correctly pronounce abbreviations, code snippets, quotations, etc. When combined with CSS, semantic tags also create visually appealing Web effects such as the highlighting of computer code samples, dotted underlines, or tool tips for abbreviations and definitions.
Supports the distinction between data and layout tables
Data tables such as the one below contain data that can only understood in relation to cell and column headers. If the association between the table cells and the headers is not made clear, non-visual browsers will read the data in linear fashion. The result will be meaningless and sound like this. By contrast, XStandard makes it easy to create tables that use <th> to identify the column and row headers that cell contents refer to. XStandard also requires authors to submit summaries for data tables, allowing non-visual browsers to describe tables fully. Listen to how a screen reader might process the same data table properly marked up using XStandard.
Cups of coffee consumed by each person| Name | Cups | Type | Sugar |
|---|
| Wendy | 10 | Regular | yes |
| Jim | 15 | Decaf | no |
Distinguishes between decorative and informative images
XStandard ensures that images are used correctly by prompting authors to identify images as decorative or informative, when images are uploaded through the editor or referenced in a remote library.
Decorative images are used for visual effect or as design elements (spacers or graphical bullets). Since they are not used to convey meaningful information, XStandard makes decorative images invisible to non-visual browsers by giving them an empty alt text, and by not requiring a title or longdesc.
By contrast, informative images such as photographs, diagrams and navigational aids do convey important meaning. XStandard therefore requires alt text for informative images and encourages users to also contribute both a title and longdesc. In addition, XStandard reinforces the distinction between alt text and title by asking for both. (title is properly used for tool tips, not alt)
Offers a rich API for extending the editor's functionality
XStandard has a rich API (methods, properties and events) that facilitates extending the functionality of the editor using custom programming. Hook into XStandard events to launch your own dialog boxes and to programmatically insert markup into the editor.
Includes a unique "Screen Reader Preview"
Code generated by XStandard is guaranteed to be accessibility-ready, but XStandard's Screen Reader Preview offers authors an additional opportunity to optimize content for accessibility. It does this by displaying content managed through XStandard as it is "read" by screen readers. This means content is laid out in linear fashion, together with information that the author would normally not see (alt text, table summaries, tool tips, etc.). Previewing content in this fashion prompts authors to make necessary changes prior to publishing.
For example, authors might forget to identify which cells in a data table act as row or column headers. Without this information, screen readers have no references for data in the table. Alternatively, captions and summaries submitted for tables might need to be modified, or alt texts edited to be more meaningful. XStandard also alerts authors to inappropriate text used for hyperlinks. The expression "Click here" for example, is meaningless when processed by a screen reader, and XStandard is easily customized to warn against the use of other expressions of a similar type.
The Screen Reader Preview also issues alert messages when code entered manually through View Source contains semantically questionable markup. For example it discourages the use of the <b> tag, which has visual significance for sighted readers but carries no semantic significance for users of assistive technologies such as screen readers. In this case users would be encouraged to use <strong> which does have semantic meaning for screen readers. Other alert messages include warnings that alt text or table summaries are missing. This information must be submitted before content can be saved.