OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: XML Editor recommendation?

[ Lists Home | Date Index | Thread Index ]
  • From: Michael Champion <mchamp@mediaone.net>
  • To: xml-dev <xml-dev@lists.xml.org>
  • Date: Thu, 23 Nov 2000 10:34:16 -0500

----- Original Message -----
From: "Pollington, Lee (ELSLON)" <lee.pollington@biomednet.com>
To: <xml-dev@lists.xml.org>
Sent: Thursday, November 23, 2000 7:09 AM
Subject: RE: XML Editor recommendation?

> I would still like to know XMetal's level of compliance with W3C CSS
> standards,

FWIW, XMetal 2.0's help file says "The XMetaL cascading style sheet editor
provides extensive support for CSS1; CSS2 constructs can be entered in text


> I'd just like to add that I have other reasons for choosing Epic LE (as a
> first stage in XML authoring tools role out) for editorial staff:

Does Epic support CSS? It didn't in the past ...and a quick Search of their
website only finds a claiim to support it in "output to the Web."
And if Epic doesn't, why ask about XMetaL's level of compliance?

Also, since it's clear that XMetaL and Epic are the only products that can
seriously claim to edit XML with a wordprocessor-like UI, it would be nice
to hear more about how they compare.  Traditionally Epic was 3 times as
expensive as XMetaL, but  it sounds as though this LE version is actually
cheaper.  I can't get much info from the blurb on the website ... what can't
you do in Epic LE that you can in Epic that an end-user would care about?
What features does XMetaL have the Epic LE doesn't, and vice versa?


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS