cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Michler" <Mich...@fzi.de>
Subject AW: Problems with JTidy and cocoon
Date Wed, 18 Jan 2006 17:19:50 GMT

Hi,

I think the namespaces should match, but i've attached the nekohtml and the
tidyhtml output, or what do you mean by RAW-output?
I've created this output with this pipe
            <map:match pattern="templates/frame-common.tidyhtml">
                <map:generate src="templates/frame-common.html"
type="nekohtml"/>
                <map:serialize type="html"/>
            </map:match>
and my xslt callup is

            <map:match pattern="common/**.html">
                <map:aggregate element="data">
                    <map:part
src="cocoon:/templates/frame-common.tidyhtml"/>
                    <map:part src="cocoon:/common/{1}.tidyhtml"/>
                </map:aggregate>
                <map:transform src="trafos/frameit.xsl">
                   <map:parameter name="lang" value="de" />
                   <map:parameter name="switch"
value="/swt/eng/common/{1}.html" />
                </map:transform>
                <map:serialize type="html"/>
            </map:match>

is this correct?


Thanks

Johannes


The raw-output of tidyhtml is
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="HTML Tidy, see www.w3.org" name="generator"/>
<title>Forschungszentrum Informatik (FZI) - Forschungsbereich SWT</title>
<meta content="Homepage des Forschungszentrum Informatik in Karlsruhe."
name="description"/>
<meta content="FZI, Forschungszentrum Informatik, Informatik"
name="keywords"/>
<meta content="text/html; charset=iso-8859-15" http-equiv="Content-Type"/>
<link type="image/x-icon" href="/swt/ressources/images/swt.ico" rel="icon"/>
<link type="image/x-icon" href="/swt/ressources/images/swt.ico"
rel="shortcut icon"/>
<link href="/swt/fzi.css" type="text/css" rel="stylesheet"/>
<script type="text/javascript" src="/swt/fzi.js" language="JavaScript">
</script>
<style type="text/css">  p {text-align:justify;} </style>
</head>

and the output of nekohtml gives me

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>


<head>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

<title>Forschungszentrum Informatik (FZI) - Forschungsbereich SWT</title>

<meta name="description" content="Homepage des Forschungszentrum Informatik
in Karlsruhe.">

<meta name="keywords" content="FZI, Forschungszentrum Informatik,
Informatik">

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">

<link rel="icon" href="/swt/ressources/images/swt.ico" type="image/x-icon">

<link rel="shortcut icon" href="/swt/ressources/images/swt.ico"
type="image/x-icon">

<link rel="stylesheet" type="text/css" href="/swt/fzi.css">

<script language="JavaScript" src="/swt/fzi.js" type="text/javascript">
</script>

<style type="text/css">  p {text-align:justify;} </style> 

</head>

-----Ursprüngliche Nachricht-----
Von: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]
Gesendet: Di 1/17/2006 6:06
An: users@cocoon.apache.org
Betreff: Re: Problems with JTidy and cocoon
 
Le 17 janv. 06, à 17:27, Johannes Michler a écrit :

> Yes, i've tried this, but unfortunately this doesn't work with the
> transform-script (i get a white page)

There is a difference between JTidy and NekoHTML in the way they 
generate namespaces...I don't have the details handy, but IIRC one of 
them generates namespaced xhtml elements while the other does not.

So, if you're running an XSLT transform after one of these generators, 
you will have to adapt it (again IIRC) to run with the other.

To find out more, look at the raw output of the generators, without any 
transformation, to find out exactly which namespaces are used in their 
output.

-Bertrand


Mime
View raw message