W3C home > Mailing lists > Public > www-amaya@w3.org > April to June 2002

Re: Saving an XHTML document adds wrong <meta>

From: Irene Vatton <Irene.Vatton@inrialpes.fr>
Date: Thu, 13 Jun 2002 12:27:42 +0200
To: "Steven Pemberton" <steven.pemberton@cwi.nl>
Cc: "Masayasu Ishikawa" <mimasa@w3.org>, "Irene Vatton" <Irene.Vatton@inrialpes.fr>, www-amaya@w3.org, Irene.Vatton@inrialpes.fr
Message-Id: <20020613102742.B8BCFC@maiaina.inrialpes.fr>

> > > The point is not about encoding.  If a user creates an XHTML 1.1
> document
> > > and saves it as 'application/xhtml+xml', Amaya MUST NOT say 'text/html'
> > > with the meta element.
> >
> > Well, when Amaya does that, the server refuses to save a document with the
> > MIME type
> > 'application/xhtml+xml' because it was previously saved with the MIME type
> > "text/html'.
> > As you are aware about that, you can change the configuration parameter in
> > Special/Prefenrces/Publishing to set "Use the application/xhtml+xml MIME
> type
> > for XHTML documents".
> Isn't there a way to say "Don't add a meta element that sets the mime type
> for XHTML"? I want to the server to decide what media type is used. At the
> moment the wrong thing is done. It is wrong to set the media type to
> text/html for XHTML 1.1.

We thought that the meta element was useful when documents loaded locally?
Amaya does coherent things: the mime type in the meta and the http put header
are the same.
If I understand your point of view, the author chooses to create a XHTML or 
a HTML document but Amaya should not give information about the mime type. 
The server is enough intelligent to determine it by itself.
That's easier to implement for us.

What about the encoding? Servers give self-decided encodings too and that 
errors when the document is saved in UTF-8 and served with ISO-8859-1.

> Thanks.
> Steven Pemberton
Received on Thursday, 13 June 2002 06:30:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:37 UTC