Just tried it with JSPs in the Trinidad demo bundle, and at least
there it worked fine.  Adding:

  <jsp:directive.page contentType="application/xhtml+xml;charset=utf-8"/>

resulted in:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; dir="ltr" xml:lang="en">
    <title>Apache Trinidad Demo Index</title>
    <meta name="generator" content="Apache Trinidad"></meta>
    <link rel="stylesheet" charset="UTF-8" type="text/css"
href="/tri/adf/styles/cache/minimal-desktop-496553747-en-gecko-cmp.css"></link>

etc...  Might be something Facelets specific, but it does seem as
though the core Trinidad code is doing the right thing.

-- Adam


On 8/8/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> I am trying to use the following DOCTYPE for my pages with Trinidad
> 1.0.2-SNAPSHOT and facelets 1.1.11:
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
>
> So I added:
>
> <f:view contentType="application/xhtml+xml" />
>
> To my page. The problem is that Trinidad is producing invalid XML in the head:
>
> <link rel="stylesheet" charset="UTF-8" type="text/css"
> href="/test/adf/styles/cache/minimal-desktop-496553747-en-gecko-cmp.css">
> ...
>
> The <link> tag is never closed. Is there a way to get xhtml standard
> compliant xhtml rendered using trinidad?
>
> A4J used a hack of using Tidy to ensure the output was valid XML, is
> there something similar with trinidad?
>
> In the meantime it looks like I will have to use HTML as my content-type.
>
> Thanks,
> Andrew
>

Reply via email to