Karl,
At 04:09 PM 5/20/2010, you wrote:
Got it, thanks Wendell. My output method is "xml", my doctype is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
Net result, valid xhtml content and no auto-generated bad meta
content-type tag.
Nice.
Note, as Liam did in response to this thread, that XSLT 2.0
processors respect an honest "xhtml" serialization method.
To be safe, should I add:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
To my <head> tag?
Hm, that's an interesting question.
If so, is there such thing as an "xhtml" content type?
I'm afraid you'll need more of an expert to comment on the vagaries
of content="application/xhtml+xml", etc. etc. (back to Liam). It's
one of those things where there appears to be a "correct" way, and a
way that works, or doesn't, and these are not, or are only sometimes, the same.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--