You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Clay Leeds <cl...@medata.com> on 2003/05/15 21:08:21 UTC
minor FAQ idea
Hi Victor...
I've noticed that the TOC for the FAQ page is hard to read (perhaps
others have too?). I figure, that if you remove the hyperlink to the
numbered items (leaving the links for their sub-items), it'll probably
improve readability. In addition, is there a reason that the "ordered"
list items are preceded by an "unordered" "bullet"? (see below):
* 1. General Questions (<-- remove this hyperlink)
o What is FOP? (<-- leave these hyperlinks)
... (<-- leave these hyperlinks)
* 2. Problems running FOP (<-- remove this hyperlink)
o yata yata (<-- leave these hyperlinks)
It might also help to put a space-before="6pt" for each of those
numbered items.
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by Clay Leeds <cl...@medata.com>.
That's a good suggestion. I figured that might be the case. However, I'd
like to make certain fop-dev'rs like the idea of the change before I
browse/search the archives to see if it's been asked/suggested before,
and (since I'm not currently a member of that list) figure out how to
subscribe to that list, and finally post my question.
On 5/15/2003 1:49 PM, J.Pietschmann wrote:
> Clay Leeds wrote:
>> I figure, that if you remove the hyperlink to the numbered items
>> (leaving the links for their sub-items), it'll probably improve
>> readability.
>
> The links are automatically generated. Rais this issue on the
> forrest list.
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Clay Leeds wrote:
> I figure, that if you remove the hyperlink to the
> numbered items (leaving the links for their sub-items), it'll probably
> improve readability.
The links are automatically generated. Rais this issue on the
forrest list.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by Jeff Turner <je...@apache.org>.
On Wed, May 21, 2003 at 08:17:31AM -0600, Victor Mote wrote:
> J.Pietschmann wrote:
>
> > Glen Mazza wrote:
> > > --- Victor Mote <vi...@outfitr.com> wrote:
> > >>but am under the
> > >>impression that the pdfs that are
> > >>generated are being generated by forrest/cocoon,
> > >>which means they are using
> > >>the redesign/trunk branch.
> > >
> > > Are we certain that Forrest/Cocoon is using the trunk
> > > branch?
> > ...
> > > On the Cocoon JAR
> > > page(http://cocoon.apache.org/2.0/installing/jars.html),
> > > they say they are using the FOP 0.20.4 release,
> > > therefore the maintenance branch.
> >
> > The serializer is based on the maintenance branch, because
> > the trunk is hardly usable for production. I read Vic's comment
> > as that the PDFs and everything else on the web site is
> > generated from the xdocs from the trunk rather than from xdocs
> > from the maintenance branch.
>
> Actually, Glen correctly interpreted my comment. If you click any of the
> "print-friendly PDF" icons in the upper right corner of our web pages, you
> will get a PDF with a footer that says "Created by: FOP 1.0dev".
That comes from the src/documentation/skinconf.xml file, near the end:
<credit role="pdf">
<name>Created by: FOP 1.0dev</name>
<url>http://xml.apache.org/fop/dev</url>
<image>images/logo.jpg</image>
<width>138</width>
<height>31</height>
</credit>
</credits>
> Also, something Keiron said in our pre-Forrest days left me with the
> impression that we were trying to get the redesign branch in good
> enough shape to be used for this purpose.
>
> Since Forrest is in the picture as well as Cocoon, it seems possible that
> Forrest is overriding which version of FOP is being used. (??)
Forrest uses 0.20.4 by default, so I think the above <credit> is wrong.
My fault, as I unthinkingly cut&pasted it from an earlier FOP stylesheet.
Sorry for the confusion.
--Jeff
> Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by Jeff Turner <je...@apache.org>.
On Wed, May 21, 2003 at 09:17:52PM +0200, J.Pietschmann wrote:
...
> Well, I remember. Keiron provided a patch to the PDF serializer
> for Cocoon because of the interface change in HEAD. Perhaps the
> forrest crowd forgot of this and switched back to a FOP from
> the maintenance branch?
Keiron's patch worked fine, but CVS FOP wasn't kind to our
document2fo.xsl stylesheet, so we're currently using the maintenance
branch.
--Jeff
...
>
> J.Pietschmann
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Victor Mote wrote:
> Actually, Glen correctly interpreted my comment. If you click any of the
> "print-friendly PDF" icons in the upper right corner of our web pages, you
> will get a PDF with a footer that says "Created by: FOP 1.0dev". Also,
> something Keiron said in our pre-Forrest days left me with the impression
> that we were trying to get the redesign branch in good enough shape to be
> used for this purpose.
Well, I remember. Keiron provided a patch to the PDF serializer
for Cocoon because of the interface change in HEAD. Perhaps the
forrest crowd forgot of this and switched back to a FOP from
the maintenance branch?
> Since Forrest is in the picture as well as Cocoon, it seems possible that
> Forrest is overriding which version of FOP is being used. (??)
If they simply updated from the Cocoon repository, they will
have fallen back from using HEAD. Now that there is a Gump target
for FOP maintenance nobody will ever notice.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: minor FAQ idea
Posted by Victor Mote <vi...@outfitr.com>.
J.Pietschmann wrote:
> Glen Mazza wrote:
> > --- Victor Mote <vi...@outfitr.com> wrote:
> >>but am under the
> >>impression that the pdfs that are
> >>generated are being generated by forrest/cocoon,
> >>which means they are using
> >>the redesign/trunk branch.
> >
> > Are we certain that Forrest/Cocoon is using the trunk
> > branch?
> ...
> > On the Cocoon JAR
> > page(http://cocoon.apache.org/2.0/installing/jars.html),
> > they say they are using the FOP 0.20.4 release,
> > therefore the maintenance branch.
>
> The serializer is based on the maintenance branch, because
> the trunk is hardly usable for production. I read Vic's comment
> as that the PDFs and everything else on the web site is
> generated from the xdocs from the trunk rather than from xdocs
> from the maintenance branch.
Actually, Glen correctly interpreted my comment. If you click any of the
"print-friendly PDF" icons in the upper right corner of our web pages, you
will get a PDF with a footer that says "Created by: FOP 1.0dev". Also,
something Keiron said in our pre-Forrest days left me with the impression
that we were trying to get the redesign branch in good enough shape to be
used for this purpose.
Since Forrest is in the picture as well as Cocoon, it seems possible that
Forrest is overriding which version of FOP is being used. (??)
I just looked at the document properties for our home page index.pdf, and it
says "Producer: FOP 0.20.4". So, to answer Glen's question, I am not certain
of anything here.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Glen Mazza wrote:
> --- Victor Mote <vi...@outfitr.com> wrote:
>>but am under the
>>impression that the pdfs that are
>>generated are being generated by forrest/cocoon,
>>which means they are using
>>the redesign/trunk branch.
>
> Are we certain that Forrest/Cocoon is using the trunk
> branch?
...
> On the Cocoon JAR
> page(http://cocoon.apache.org/2.0/installing/jars.html),
> they say they are using the FOP 0.20.4 release,
> therefore the maintenance branch.
The serializer is based on the maintenance branch, because
the trunk is hardly usable for production. I read Vic's comment
as that the PDFs and everything else on the web site is
generated from the xdocs from the trunk rather than from xdocs
from the maintenance branch.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: minor FAQ idea
Posted by Glen Mazza <gl...@yahoo.com>.
--- Victor Mote <vi...@outfitr.com> wrote:
> Glen Mazza wrote:
>
> > Also, Victor--would you like help completing the
> > Examples page on the Main Tab? (tables giving
> links
> > to the fo and pdf for each of the samples)
>
> This is something that has been on my to-do list for
> a while. I haven't
> looked into it carefully, but am under the
> impression that the pdfs that are
> generated are being generated by forrest/cocoon,
> which means they are using
> the redesign/trunk branch. We probably need to
> change that.
>
Are we certain that Forrest/Cocoon is using the trunk
branch? The src\documentation\sitemap.xmap for FOP
gives this entry to generate the PDF:
<map:match pattern="fo/*.fo.pdf">
<map:generate src="content/xdocs/fo/{1}.fo"/>
<map:serialize type="fo2pdf"/>
</map:match>
And the serializer for fo2pdf is as follows:
<map:serializer name="fo2pdf"
src="org.apache.cocoon.serialization.FOPSerializer"
mime-type="application/pdf" />
On the Cocoon JAR
page(http://cocoon.apache.org/2.0/installing/jars.html),
they say they are using the FOP 0.20.4 release,
therefore the maintenance branch. (This is an
important point, as one can assume that all of the
examples will work under the 0.20.4 release but not
necessarily under the trunk release.)
Thanks,
Glen
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: minor FAQ idea
Posted by Victor Mote <vi...@outfitr.com>.
Glen Mazza wrote:
> Also, Victor--would you like help completing the
> Examples page on the Main Tab? (tables giving links
> to the fo and pdf for each of the samples) I can start
> working on this soon if you'd like.
>
> (We also have an examples page on the Development tab,
> but that looks mostly complete--probably be nice to
> merge with the one on the main page, btw.)
This is something that has been on my to-do list for a while. I haven't
looked into it carefully, but am under the impression that the pdfs that are
generated are being generated by forrest/cocoon, which means they are using
the redesign/trunk branch. We probably need to change that. I agree that it
seems like the two pages should be merged (onto the user page), but I wanted
to raise that issue on this list in case I missed something -- so here it
is. If anyone knows of a need for two pages, please speak up now.
Another idea here that I wanted to explore was how closely our test and
example files fit together. I haven't thought through all of that yet, but
it might be something to explore.
Please feel free to work on this -- it is definitely a useful path.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: minor FAQ idea
Posted by Glen Mazza <gl...@yahoo.com>.
Also, Victor--would you like help completing the
Examples page on the Main Tab? (tables giving links
to the fo and pdf for each of the samples) I can start
working on this soon if you'd like.
(We also have an examples page on the Development tab,
but that looks mostly complete--probably be nice to
merge with the one on the main page, btw.)
Glen
--- Clay Leeds <cl...@medata.com> wrote:
> Hi Victor...
>
> I've noticed that the TOC for the FAQ page is hard
> to read (perhaps
> others have too?). I figure, that if you remove the
> hyperlink to the
> numbered items (leaving the links for their
> sub-items), it'll probably
> improve readability. In addition, is there a reason
> that the "ordered"
> list items are preceded by an "unordered" "bullet"?
> (see below):
>
> * 1. General Questions (<-- remove this hyperlink)
> o What is FOP? (<-- leave these hyperlinks)
> ... (<-- leave these hyperlinks)
> * 2. Problems running FOP (<-- remove this
> hyperlink)
> o yata yata (<-- leave these hyperlinks)
>
> It might also help to put a space-before="6pt" for
> each of those
> numbered items.
> --
> Clay Leeds - cleeds@medata.com
> Web Developer - Medata, Inc. - http://www.medata.com
> PGP Public Key:
> https://mail.medata.com/pgp/cleeds.asc
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> fop-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> fop-dev-help@xml.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org