W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 2002

Re: Amaya now saves invalid documents?

From: Keith Hopper <kh@waikato.ac.nz>
Date: Tue, 24 Sep 2002 15:36:11 +1200
To: www-amaya@w3.org
Message-ID: <4b7acc00d4kh@waikato.ac.nz>

In article <Pine.LNX.4.30.0209231751420.25011-100000@tux.w3.org>,
   Charles McCathieNevile <charles@w3.org> wrote:

> So I tried to reproduce this (Amaya 6.1). It doesn't work with XHTML, only
> with HTML, as far as I can figure.

> What happens is that it is possible to introduce strange things into the
> source of HTML, and Amaya corrects the markup when synchronising.

> Does this match what you were doing? (And do you have a sample file or more
> details?)

> cheers

> Chaals

> On Mon, 23 Sep 2002, Janet Daly wrote:

> >So here's the rub (x2)
> >
> >Did that (syncing) and still have the problem. Also, saving other docs
> >after browsing with regular view does not alert me to bad markup.
> >
> >Janet

     I don't know whether the interesting problems I have been having with
documents originated elsewhere - for revision to current standards.

The document I have  been playing with is at 


which claims to be HTML 3.2 - but isn't.  I loaded into Amaya 6.4 (linux
GTK version) and tried some simple editing - but Amaya kept indicating that
anywhere I wished to select was -


and would not let me select it.  I thought to try and save it locally which
Amaya did - but didn't raise a protest either then or on an attempt to
reload it - that is all I can do apart from viewing many red marks on the
structure view and several lines in the parsing errors.  Might this be a
related problem??

                Keith Hopper

Keith Hopper
Senior Lecturer
Department of Computer Science
University of Waikato, NZ
Received on Monday, 23 September 2002 23:36:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:26 UTC