W3C home > Mailing lists > Public > spec-prod@w3.org > January to March 2001

Re: Editing tools

From: Paul Grosso <pgrosso@arbortext.com>
Date: Wed, 07 Mar 2001 14:38:28 -0600
Message-Id: <3.0.32.20010307143407.01d72b54@notesmail.arbortext.com>
To: Charles McCathieNevile <charles@w3.org>
Cc: <spec-prod@w3.org>
At 15:12 2001 03 07 -0500, Charles McCathieNevile wrote:
>On Wed, 7 Mar 2001, Paul Grosso wrote:
>
>  What does "clean roundtrip" mean?
>
>Keeping the source that is imported. For example, Amaya makes things valid,
>Netscape Composer makes things invalid, and Dreamweaver just leaves them
>alone (until you edit).

Okay, thanks.  

Epic handles well-formed XML; non-well-formed stuff isn't XML, so
no promises are made, though some minor errors may be corrected
with an error message upon input.

If the input is (supposedly) valid (as opposed to just well-formed,
that is, if there is a doctype declaration that points to a DTD),
then Epic will do a validity check and give warnings for things
that don't match the DTD.  It generally would not do fixup--certainly
not without warnings.

Epic always generates well-formed or valid XML.

Except in the case of "pre-formatted" elements, Epic wraps content,
so input file indentation and line breaks are not usually retained.
For example, if you read in a file that is the result of HTML Tidy
and then save it out and then look at the result in a text editor,
it will not look as "tidy".  But the logical content is the same,
and the result in a browser should be the same.

paul
Received on Wednesday, 7 March 2001 15:38:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:11 GMT