forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: xml.apache.org forrest-0.6
Date Mon, 18 Oct 2004 15:19:16 GMT
On Oct 17, 2004, at 9:00 PM, David Crossley wrote:
> Clay Leeds wrote:
>> As you know. I am the "Web Maestro" for the Apache FOP web site. I
>> intend to update the http://xml.apache.org/fop/ web site soon after
>> xml.apache.org's forrestbot is updated to Apache Forrest 0.6.
>
> This bit confuses me. I did not realise that any "forrestbot"
> new or old is assisting yet with the xml.apache.org site.
> We do want it to.

Actually, I really just want to make certain that when I commit files 
for 'xml-fop' via cvs.apache.org, Forrest-0.6 is used to process my 
xml-fop/src/documentation/content/xdocs/*.xml

>> So my question is when will I be able to update xml-fop so that it 
>> will
>> build the new, improved FOP web site using Apache Forrest 0.6 instead
>> of Apache Forrest 0.5.1 (with which I couldn't get BUILD SUCCESSFUL to
>> save my life...)?
>
> The build of the website for "FOP" has nothing to do
> with the build of the top-level xml.apache.org website.
> FOP is separate and you 'cvs checkin' the generated result
> to the xml-site CVS in the /targets/ directory.

You're right. I am not concerned about the top-level of 
<http://xml.apache.org/>. My goal is to finally update 
<http://xml.apache.org/fop/>, so I can make other, needed updates.

>> Or has http://xml.apache.org/ already been updated to Apache Forrest
>> 0.6?
>
> No, the top-level xml site has not, but i am working on it.
>
> By the way, you can now tell which sites are generated by Forrest
> by doing "view-source" and see the Generator meta tag.

Correction:

'...you *will* now be able to tell (after the system which generates 
<http://xml.apache.org/fop/> is updated to Forrest-0.6)...' Currently 
the FOP web site shows this:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>FOP</title>
<link type="text/css" href="skin/page.css" rel="stylesheet">
</head>

The <http://forrest.apache.org/> site shows this:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.7-dev">
<meta name="Forrest-skin-name" content="pelt">
<title>Welcome to Apache Forrest</title>
<link type="text/css" href="skin/basic.css" rel="stylesheet">
<link media="screen" type="text/css" href="skin/screen.css" 
rel="stylesheet">
<link media="print" type="text/css" href="skin/print.css" 
rel="stylesheet">
<link type="text/css" href="skin/profile.css" rel="stylesheet">
<script src="skin/getBlank.js" language="javascript" 
type="text/javascript"></script><script src="skin/getMenu.js" 
language="javascript" type="text/javascript"></script><script 
src="skin/fontsize.js" language="javascript" 
type="text/javascript"></script>
<link rel="shortcut icon" href="favicon.ico">
</head>

Also, is there a reason why the first meta tag in all caps? Wouldn't 
that violate xhtml rules, which, I believe specify all tags should be 
lowercase (I realize it says HTML 4.01 Transitional... or are we 
fishing for a PATCH? ;-))?

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message