- From: Irene Vatton <Irene.Vatton@inrialpes.fr>
- Date: Tue, 04 Jun 2002 17:33:10 +0200
- To: Masayasu Ishikawa <mimasa@w3.org>
- Cc: Irene.Vatton@inrialpes.fr, steven.pemberton@cwi.nl, www-amaya@w3.org, Irene.Vatton@inrialpes.fr
> Irene Vatton <Irene.Vatton@inrialpes.fr> wrote: > > > > I was creating an XHTML 1.1 document. I saved it, and Amaya added the > > > following element to the document: > > > > > > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > > > > > > In other words: wrong. > > > > If Amaya generated that encoding it effectively saved the document with this > > encoding. That generates of course an error if the server doesn't take care > > of the information given when the document was saved and decides to serve it > > with another encoding. > > 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". > > Regards, > -- > Masayasu Ishikawa / mimasa@w3.org > W3C - World Wide Web Consortium >
Received on Tuesday, 4 June 2002 11:35:32 UTC