True, sometimes this is a bug. But usually not. In fact, it is impossible to write an XSD schema that says: Inside element <DESCRIPTION> allow any XHTML Basic tags. Instead, you end of w/ "any" content model. The problem is the same whether you use XSD or DTDs.

Thus, the typical solution is to use the editor of choice with the typical word processing features (tables, embed a picture, bullet/numbered lists, set font/size, bold, italic, did I miss anything?) and post process and validate the document into XML at the app level. This works fine, btw. No need to fix it.

take it easy,
Charles Reitzel

At 04:00 PM 12/20/2002 +0000, Michael Kowalski wrote:
A bug, not a feature! What if you want to constrain markup of this kind to enforce design standards and preserve the look-and-feel of the site? Many content authors have limited design skills.
michael

On Friday, December 20, 2002, at 03:39 pm, Eoin Campbell wrote:
- No format restrictions. You can mix text, tables and images
  any way you want without being limited by the interface.
--
http://cms-list.org/
trim your replies for good karma.


Reply via email to