Re: Question for FOP

2002-04-05 Thread Rick Tessner

On Thu, 2002-04-04 at 14:31, Cai, Jenny (US - Dallas) wrote:
 Hi,

Hi Jenny,
 
 I just successfully run the examples (simple.fo) provided in
 'fop-0.20.3-bin.tar.gz' file under fop-0.20.3\docs\examples\fo subdirectory
 in the command prompt and I got a pdf file successfully . I still have the
 following question:
 
 1. How can I view the source code for this example?

I think, based on your third question below, that you're looking for an
XML file that is then converted to PDF.  The simple.fo is the source,
written in XSL:FO, which is XML.  But, probably not what you were
expecting.

I personally don't write my documentation directly in XSL:FO but instead
write them in some other XML format (such as DocBook,
http://docbook.org/ ) and then write stylesheets (or using existing
stylesheets) to convert the XML format to XSL:FO.  I then use FOP to
render the XSL:FO as PDF.

I think that's the kind of thing that you would be looking for as well.

 2. I also looked over all the rest of the folders included in 'fop-0.20.3'
 and there are a lot other folders like design, html-docs(some .html files in
 it), xml-docs(some xml files in it), etc.  What are all those files used
 for?  

These would just be the documentation for  FOP.  The html-docs folder
contains the FOP documentation in HTML format, generated from the
xml-docs/fop folder.  I noticed that under the xml-docs folder, there is
the skins folder which contains stylesheets (used in converting the XML
documents to HTML, PDF, etc).

Think of the xml-docs folder as the source and the the html-docs folder
as the output (programatically speaking).
 
 3. Actually what I want to do is:  convert a XML file to PDF file and
 display this PDF file on the web page. How to do this?

There would be a couple of ways of doing this.  The first would be to
generate the PDF in a batch mode and create a static web site containing
web pages that reference the static PDF documents.

The second would be to dynamically create the PDF documents.  This would
be done with a servlet using a servlet engine such as Apache Tomcat. 
There is an example of doing this on the Apache FOP website (
http://xml.apache.org/fop/embedding.html ).  Another method would be to
use Apache Cocoon (which can also be found on http://xml.apache.org/ )

 I am new to this and really like to have your advices and help.  So if you
 could provide further information, I would appreciate it very much.

Hope this helps.

-- 
Rick Tessner
[EMAIL PROTECTED]

There are no bad days.  Only good days and great days.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: CVS problems

2001-07-16 Thread Rick Tessner

On Mon, 16 Jul 2001 22:30:59 +0200, Karen Lease wrote:

Hi all,

cvs [login aborted]: connect to xml.apache.org:2401 failed: Connection
refused

Sounds like overload on the host, but I've never seen that before.
Apache wouldn't by any chance experiencing some kind of DOS attacks
recently?

Any suggestions?

It looks like the CVS repository has moved to cvs.apache.org.  This
is true for xml-fop and xml-cocoon2 at least.  I just use the anoncvs,
so I don't know about actually committer userids, but I'd assume that
all that has been moved over as well.

If you're a UNIX user and you just wanna change the CVS admin files
in your checked-out copy of xml-fop, use the following to replace
all refs to xml.apache.org to cvs.apache.org in the CVS/Root files.

[ This is sh/ksh/bash compatible ... something similar would need to
  be used for csh/tcsh ]

  cd xml-fop
  for i in `find . -name Root -print | grep CVS/Root` ; do
j=${i}.new
cat $i | sed -e 's/xml.apache/cvs.apache/'  $j
mv $i ${i}.orig
mv $j $i
  done

And change the entry in the ~/.cvspass file from xml.apache.org to
cvs.apache.org.

-- 
Rick Tessner[EMAIL PROTECTED]
MYRA Systems Corp. Fone: (250) 381 1335 x125  Phax: (250) 381 1304
   Cell: (250) 885 9452

Forget your troubles and blow some bubbles.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]