Re: Probs using XSLT in browsers
Ok, i think i understood. But that means that FF correctly guessed i was using latin 1 or it simply ignores the illegal characters, cause the problem only ocurred in IE. Thanks again. On Tue, 8 Mar 2005 15:31:40 GMT, David Carlisle <davidc@xxxxxxxxx> wrote: > > > but isn't that strange that it occurs even in comments? > > No. > > XML is defined to be a series of (unicode characters) whereas your file > consists of a series of bytes. So the first thing (conceptually) that > has to happen is that a) the system figures out what encoding you are > usinmg and then (b) translates the sequence of bytes into a sequence of > characters and then (c) parses that sequence of characters looking for > XML markup. > > A real XML parser most likely interleaves these into a single pass, but > logically they are distinct and if you have an encoding error (such as > an illegal utf8 byte when the system thought it was reading utf8 (but > you intended latin 1) then logically you get a fatal error after stage > (b) and before the file can be parsed looking for comments (or any other > markup). > > > David > > ________________________________________________________________________ > This e-mail has been scanned for all viruses by Star. The > service is powered by MessageLabs. For more information on a proactive > anti-virus service working around the clock, around the globe, visit: > http://www.star.net.uk > ________________________________________________________________________
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format