[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: Broken link problems anyone?
Subject: Re: Broken link problems anyone? From: Mike Brown <mike@xxxxxxxx> Date: Wed, 26 Apr 2000 18:01:35 -0600 (MDT) |
> There is no difference in the > XSL, and I have looked at the HTML and there > is no difference when you look at the > graphic that was displayed, and the one that was not. The best way to tell is to view the server logs and see what the browser is asking for, and when. I used this method and found that in IE, having autodetect encoding set and viewing an HTML document that is served without charset info in the HTTP headers or META elements, and that contains +foo-, where foo is a sequence of characters in the Base64 alphabet, causes the document to be (rightly) interpreted as UTF-7 encoded. This ended up munging a lot of image references and, if you looked closely, some of the text in the document as well. When the browser tried to fetch the images, it was asking for them by the wrong name. The solution was to make sure the HTML document contained <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> This may of course not be the solution, but I would start by looking at the HTTP server logs. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: Broken link problems anyone?, Chris Beck | Thread | RE: Broken link problems anyone?, Medina, Edward |
RE: including the HTML <BR> in XSL , Toivo Lainevool | Date | Re: Displaying every 2 element valu, Mike Brown |
Month |
Keywords