You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Clay Leeds <cl...@medata.com> on 2004/10/16 21:04:23 UTC
xml.apache.org forrest-0.6
When will xml.apache.org be updated to forrest-0.6?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml.apache.org forrest-0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> When will xml.apache.org be updated to forrest-0.6?
Not sure what you mean. More information please.
--
David Crossley
Re: OpenOffice and Forrest
Posted by Clay Leeds <cl...@medata.com>.
On Oct 18, 2004, at 3:10 PM, Clay Leeds wrote:
> On Oct 18, 2004, at 2:39 PM, Linda Rose wrote:
>> Hi,
>>
>> Once again, excuse my ignorance .... but how exactly do you use
>> OpenOffice
>> files as source files for Forrest? Do you save it as a .sxw file? I
>> thought
>> it had to be an xml file? Can someone point me to step-by-step
>> instructions
>> for using OpenOffice files with Forrest?
>>
>> Thanks,
>>
>> Linda
>
> You are correct. Forrest takes *.sxw files and can generate a web site
> off of that with a few important caveats explained on the OpenOffice
> Writer page[1]:
> - embedded images won't work--they must be linked to:
> src/documentation/resources/images/*.jpg|*.gif|*.png
>
> I, Ross and others hope to resolve this with an improved
> OpenOffice.org
> writer XSL file, but I don't know how long that will take:
>
> src/core/context/resources/stylesheets/aggregates/openoffice-
> writer.xsl
>
> - your documents need to be built from the openoffice-writer.sxw
> file, which you 'obtain' via running 'forrest seed' on an empty
> directory from the command line. From my experience, starting
> from a 'blank' document yields unpredictable results. Here's the
> path to the file after doing a /forrest seed/:
>
> src/documentation/content/xdocs/samples/openoffice-writer.sxw
BTW, the reason why you need to start from this particular
openoffice-writer.sxw file, is that OpenOffice.org has a bug which does
not properly carry style information. In particular, if you open the
openoffice-writer.sxw file, and delete the Heading 3 Style, then save
the file, the Heading 3 style will not exist the next time you open the
file. It's frustrating and I'm not clear on a workaround. Search the
archives for more info.
> [1]
> http://forrest.apache.org/docs/oowriter.html
>
> Web Maestro Clay
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>
>
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: OpenOffice and Forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> ----- Original Message -----
> From: "Clay Leeds" <cl...@medata.com>
> To: <us...@forrest.apache.org>
> Sent: Monday, October 18, 2004 3:10 PM
> Subject: Re: OpenOffice and Forrest
>
>
>
>>>- your documents need to be built from the openoffice-writer.sxw
>>
>> file, which you 'obtain' via running 'forrest seed' on an empty
>> directory from the command line. From my experience, starting
>> from a 'blank' document yields unpredictable results. Here's the
>> path to the file after doing a /forrest seed/:
>>
>> src/documentation/content/xdocs/samples/openoffice-writer.sxw
>>
>>[1]
>>http://forrest.apache.org/docs/oowriter.html
>
>
>
> Well, I updated to version .6 (I had .5.1.1) and found the
> openoffice-writer.sxw sample. Now my question is: If I use the sample as a
> template, where do I store my .sxw files so forrest can find them? Then do I
> update the website by typing forrest? I can't find this anywhere in the
> documentation.
Documentation for forrest is at
http://forrest.apache.org/docs/your-project.html
Your specific questions are answered here
http://forrest.apache.org/docs/your-project.html#adding_content (no it
doesn't mention Open Office by name but it is an XML format and so you
can follow these instructions).
Ross
Re: OpenOffice and Forrest
Posted by Linda Rose <li...@cox.net>.
----- Original Message -----
From: "Clay Leeds" <cl...@medata.com>
To: <us...@forrest.apache.org>
Sent: Monday, October 18, 2004 3:10 PM
Subject: Re: OpenOffice and Forrest
>
> > - your documents need to be built from the openoffice-writer.sxw
> file, which you 'obtain' via running 'forrest seed' on an empty
> directory from the command line. From my experience, starting
> from a 'blank' document yields unpredictable results. Here's the
> path to the file after doing a /forrest seed/:
>
> src/documentation/content/xdocs/samples/openoffice-writer.sxw
>
> [1]
> http://forrest.apache.org/docs/oowriter.html
Well, I updated to version .6 (I had .5.1.1) and found the
openoffice-writer.sxw sample. Now my question is: If I use the sample as a
template, where do I store my .sxw files so forrest can find them? Then do I
update the website by typing forrest? I can't find this anywhere in the
documentation.
Thanks for your help.
Linda
>
> Web Maestro Clay
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>
>
Re: OpenOffice and Forrest
Posted by Clay Leeds <cl...@medata.com>.
On Oct 18, 2004, at 2:39 PM, Linda Rose wrote:
> Hi,
>
> Once again, excuse my ignorance .... but how exactly do you use
> OpenOffice
> files as source files for Forrest? Do you save it as a .sxw file? I
> thought
> it had to be an xml file? Can someone point me to step-by-step
> instructions
> for using OpenOffice files with Forrest?
>
> Thanks,
>
> Linda
You are correct. Forrest takes *.sxw files and can generate a web site
off of that with a few important caveats explained on the OpenOffice
Writer page[1]:
- embedded images won't work--they must be linked to:
src/documentation/resources/images/*.jpg|*.gif|*.png
I, Ross and others hope to resolve this with an improved
OpenOffice.org
writer XSL file, but I don't know how long that will take:
src/core/context/resources/stylesheets/aggregates/openoffice-writer.xsl
- your documents need to be built from the openoffice-writer.sxw
file, which you 'obtain' via running 'forrest seed' on an empty
directory from the command line. From my experience, starting
from a 'blank' document yields unpredictable results. Here's the
path to the file after doing a /forrest seed/:
src/documentation/content/xdocs/samples/openoffice-writer.sxw
[1]
http://forrest.apache.org/docs/oowriter.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: OpenOffice and Forrest
Posted by thorsten <th...@apache.org>.
Linda Rose wrote:
> Hi,
>
> Once again, excuse my ignorance .... but how exactly do you use OpenOffice
> files as source files for Forrest? Do you save it as a .sxw file? I thought
> it had to be an xml file? Can someone point me to step-by-step instructions
> for using OpenOffice files with Forrest?
>
Hi Linda,
you have to play a wee bit around with forrest then this questions will
be all answered.
Just install forrest then open a command line:
mkdir lindasForrest
cd lindasForrest
forrest seed
forrest
cd src/documentation/content/xdocs/samples
There you find openoffice-writer.sxw
Just open that with your open office and play around.
HTH
thorsten
> Thanks,
>
> Linda
>
>
>
OpenOffice and Forrest
Posted by Linda Rose <li...@cox.net>.
Hi,
Once again, excuse my ignorance .... but how exactly do you use OpenOffice
files as source files for Forrest? Do you save it as a .sxw file? I thought
it had to be an xml file? Can someone point me to step-by-step instructions
for using OpenOffice files with Forrest?
Thanks,
Linda
Re: xml.apache.org forrest-0.6
Posted by Clay Leeds <cl...@medata.com>.
This thread moved to xml-fop Build Failed thread[1] on
dev@forrrest.apache.org[1].
[1]
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=14528
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml.apache.org forrest-0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> 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
I am still confused. Can you tell me how you currently update
the FOP website.
For most websites it is entirely a manual operation.
For example at "XML Commons" we do this:
*) Edit the source at
cvs://xml-commons/src/documentation/content/xdocs/*.xml
*) Generate the site locally with whatever Forrest that
the project has decided to use.
*) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
*) Commit the edited source to
cvs://xml-commons/src/documentation/content/xdocs/
To publish the result, we have an automated cron job to
do 'cvs update'. Otherwise we do it manually with
ssh cvs.apache.org
cd /www/xml.apache.org/commons
cvs -q update -dP
> >> 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? ;-))?
No, i think that if we had used an XHTML serializer in the
forrest sitemap then all would be lowercase. At the moment
we are still serializing to HTML so it doesn't matter.
--
David Crossley
Re: xml.apache.org forrest-0.6
Posted by Clay Leeds <cl...@medata.com>.
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 - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml.apache.org forrest-0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> David Crossley wrote:
> > Clay Leeds wrote:
> >> When will xml.apache.org be updated to forrest-0.6?
> >
> > Not sure what you mean. More information please.
>
> Sorry to be obtuse. ;-)
:-) I was just about to reply to my own email
because i had figured out what you meant.
> 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.
> 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.
> 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.
--
David Crossley
Re: xml.apache.org forrest-0.6
Posted by Clay Leeds <cl...@medata.com>.
On Oct 16, 2004, at 3:03 PM, David Crossley wrote:
> Clay Leeds wrote:
>> When will xml.apache.org be updated to forrest-0.6?
>
> Not sure what you mean. More information please.
>
> --
> David Crossley
Sorry to be obtuse. ;-)
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.
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...)?
Or has http://xml.apache.org/ already been updated to Apache Forrest
0.6?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: xml.apache.org forrest-0.6
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> When will xml.apache.org be updated to forrest-0.6?
Not sure what you mean. More information please.
--
David Crossley