- From: Chris Chiasson <chris@chiasson.name>
- Date: Tue, 29 May 2007 20:45:53 -0500
- To: "Jacques Distler" <distler@golem.ph.utexas.edu>
- Cc: "Waters, Michael, Springer US" <Mike.Waters@springer.com>, "Robert Miner" <robertm@dessci.com>, R.W.Kaye@bham.ac.uk, www-math@w3.org, "William F. Hammond" <hammond@math.albany.edu>
It seems like we are just treating symptoms of a larger problem, which is: How should content negotiation be handled when some of the XML dialects available (MathML, SVG, etc) are not supported by the client? Is there a working group solving this problem? On 5/29/07, Jacques Distler <distler@golem.ph.utexas.edu> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On May 29, 2007, at 1:59 PM, Waters, Michael, Springer US wrote: > > > Just now I confirmed that observation by alternately adding and > > removing a "AddCharset UTF-8" directive to Apache's httpd.conf > > file. By adding that 1 directive, stopping/starting the server, > > >>AND<< removing the local browser cache, not just refreshing the > > page, I was able to prevent the triggering of MathPlayer on the > > simplest MathML demo page, thereby showing the XML tree. To re- > > enable the correct MathPlayer behavior, I removed the directive, > > stoppped/started the server, >>AND<< removed the local browser > > cache, going back to the default application/xhtml+xml MIME type > > for .xhtml and .xht files. > > OK. I give up, then. > > IE+MathPlayer gets > > Content-Type: application/xhtml+xml > > All XHTML-UA's get > > Content-Type: application/xhtml+xml; charset=UTF-8 > > HTML-UA's (including IE without MathPlayer) get > > Content-Type: text/html; charset=UTF-8 > > Instiki pages are served with a > > <meta http-equiv="Content-Type" content="text/html; > charset=UTF-8" /> > > This is ignored by XHTML-UA's. They get the encoding from the HTTP > headers. (For present purposes, I am avoiding an <?xml?> declaration, > so as not to have to deal with IE in quirks mode.) > > IE+MathPlayer is an HTML-UA masquerading as an XHTML-UA. So it will, > presumably, get the encoding from the <meta> element. > > Hopefully, that will suffice. > > Jacques > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (Darwin) > Comment: PGP Key - http://golem.ph.utexas.edu/~distler/distler.asc > > iD8DBQFGXKQinyqPIXpYcjcRAomyAKCqFjungiG0NcFH2XW1Uu2UCY60LACfSH2x > VS8L2+pb8e0wgN5lbxUrU38= > =c5t9 > -----END PGP SIGNATURE----- > > -- http://chris.chiasson.name/
Received on Wednesday, 30 May 2007 01:46:14 UTC