Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - XSLT and well-formed XHTML >Thread Next - Re: XSLT and well-formed XHTML Re: XSLT and well-formed XHTMLTo: NULL Date: 5/10/2008 8:22:00 PM * Vic wrote in microsoft.public.xsl: >1. The character encoding specified in the HTTP header (utf-8) is >different from the value in the <meta> element (utf-16). I will use >the value from the HTTP header (utf-8) for this validation. This >problem is created by this line: <META http-equiv="Content-Type" >content="text/html; charset=utf-16">, which is automatically generated >by the transformation???? I'm not sure why. What are you using to transform and validate the document? This should not happen since you specify xsl:output encoding='utf-8', so this might rather be a problem with your method of submission or transformation. >2. The meta tags are not well formed. They show up without the closing >"/>." I tried to resolve this by changing my XSLT output from "html" >to "xml" but that results in no page at all. What do you mean by that? Clearly if you specify method='html' the re- sult is very unlikely to be proper XHTML. >3. I get blank namespace attributes, such as: <body xmlns="">. I have >absolutely no idea why this is happening, but it's invalid. That is because you put those elements in no namespace, instead of using <html xmlns="http://www.w3.org/1999/xhtml"> put the xmlns declaration on the xsl:stylesheet element. Then all unprefixed literal result elements will be in that namespace. This might also resolve your second issue. -- Björn Höhrmann · mailto:bjoern@h... · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
