- From: Lee Feigenbaum <lee@thefigtrees.net>
- Date: Tue, 29 Dec 2009 12:09:29 -0500
- To: Lee Feigenbaum <lee@thefigtrees.net>
- CC: SPARQL Working Group <public-rdf-dawg@w3.org>
OK, I fixed the IE8 problem ... by making changes to a comment in the DTD. Don't ask me why. I don't understand DTDs. But rq25.xml renders correctly via http in IE8 now. So now Firefox and IE8 are OK from the Web. Chrome still doesn't quite work for me, but I think it might be due to plugins I have installed. Can someone else please check this? I still can't get FF to render rq25.xml using the XSLT when served from a file:// URL though. Lee Lee Feigenbaum wrote: > Some of these problems have been resolved by fixing the perms on local.css. > > Some remain. > > Lee > > Lee Feigenbaum wrote: >> I haven't debugged anything yet, but here's what I currently see: >> >> Firefox: >> >> * Locally, via file:// >> => the XSLT isn't applied and I just see a jumble of text from the >> XML doc >> >> * From w3.org, via http:// >> => I see a rendered doc, but missing a bunch of styling (colors >> and table lines in examples, for instance) >> >> >> IE8: >> >> * Locally, via file:// >> => I see a rendered doc with (AFAICT) all the CSS styling >> correctly applied >> >> * From w3.org, via http:// >> => I get a strange error processing the DTD: >> >> """ >> Cannot view XML input using style sheet. Please correct the error and >> then click the Refresh button, or try again later. >> >> >> -------------------------------------------------------------------------------- >> >> >> The character '>' was expected. Error processing resource >> 'http://www.w3.org/2009/sparql/docs/shared/xmlspec.dtd'. Line 21... >> >> |%illus.class;|%ednote.class;%local.obj.mix;"atusp.class;. >> ----------------------------------------------------^ >> """ >> >> It's a strange error because as far as I can tell, that line doesn't >> exist in the DTD. >> >> >> Google Chrome: >> >> * Locally, via file:// >> => shows up rendered with styles, like in IE8 >> >> * From w3.org, via http:// >> => It seems to load a rendered doc, but there is JS (as text) at >> the top, and then I can't scroll the page at all >> >> >> >> So.... without having done any debugging, I'm wondering if there's a >> parse error somewhere that the browsers are all handling differently. >> Would be happy with other sets of eyes though! >> >> Lee >> >> >> >
Received on Tuesday, 29 December 2009 17:10:14 UTC