Widows and Orphans Setting

2002-03-25 Thread S. Jayaraman
Hi folks

I have a problem. I am trying to use the attributes widows and orphans
to control the page break. I wish to avoid the situation that a title dos
not come at the end of a page alone. It should come in the next page, if
there is no space for 3-4 lines following it.

Please refer to the fop extract below.

I still end up with the situation that the title appears in one page and the
text appears in the next page.

Where am I going wrong ?

Thanx a million in advance

Rgds
Jay



* FOP EXTRACT  

fo:block text-align=start orphans=3 widows=3
Here is a title
fo:block space-after=0.0cm
This is the text that should come under the title.. There are 
many lines.
This is cut off
in this mail..
/fo:block
/fo:block

 END OF FOP EXTRACT *



AW: Reporting Engine !!

2002-03-25 Thread S. Jayaraman
To remove your address from the list, send a message to:
   [EMAIL PROTECTED]

-Ursprüngliche Nachricht-
Von: Woods, John T. [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 25. März 2002 19:21
An: '[EMAIL PROTECTED]'
Betreff: RE: Reporting Engine !!


how do I unsubscribe from this mailing list?

-Original Message-
From: Buonincontri, Steve (CAP, MMF, ITSS)
[mailto:[EMAIL PROTECTED]
Sent: Monday, March 25, 2002 10:17 AM
To: [EMAIL PROTECTED]
Subject: RE: Reporting Engine !!




Look up JReport at www.jinfonet.net

see whether they have FO support yet.

I have been using RTF2FO and XEP (or FOP).

- sb

-



AW: FOP API

2002-03-19 Thread S. Jayaraman
Hi Sumanta

Sorry. You find javadocs in the Fop-0.20.1-bin.tar.gz. I can see it in my
version.

Cheers
Jay



-Ursprüngliche Nachricht-
Von: Dutta, Sumanta [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 19. März 2002 17:19
An: '[EMAIL PROTECTED]'; Swaminathan Jayaraman
Betreff: RE: FOP API


Hi Jay,

I downloaded Fop-0.20.1-bin.tar.gz, and you are right, it has a docs
directory. But I don't see any javadoc anywhere under it. It has html-docs,
which is same as the website.

Thanks,
Sumanta.

-Original Message-
From: S. Jayaraman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 19, 2002 10:59 AM
To: [EMAIL PROTECTED]
Subject: AW: FOP API


Hi

You must have got it when you downloaded the FOP package. There is a Doc
directory.

Cheers
Jay


-Ursprüngliche Nachricht-
Von: Dutta, Sumanta [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 19. März 2002 17:06
An: '[EMAIL PROTECTED]'
Betreff: FOP API


Hi,

Is there any javadoc for the FOP classes (like Driver, etc.)? I could not
find anything on http://xml.apache.org/fop/index.html.

Thanks,
Sumanta.



--
This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient
of this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.





--
This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient
of this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.




AW: SV: SV: external-graphic src syntax

2002-03-13 Thread S. Jayaraman
Hi

I think if you are running under tomcat, the current directory is tomcat/bin
If you are running from command line, Java_home is the current dir
Rgds
Jay


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Magnus
Sjöberg
Gesendet: Mittwoch, 13. März 2002 15:59
An: [EMAIL PROTECTED]
Betreff: Re: SV: SV: external-graphic src syntax


That's bizarre, I 'assumed' FOP used the current directory
as its base dir...
I ran the following command with test.xml, test.xsl and
image.jpg in the current directory:

current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl
test.xsl -pdf test.pdf

All images in the xml are added to the fo using
fo:external-graphic src=image.jpg/
This produces no errors.
Exactly what sequence of events are you using to create the
PDF?

///Magnus

Michael Engelhart wrote:

 Thanks Mangus,

 That's great info.  (Maybe we can get it stuck into the FAQ? )

 I know have 2 working fine.  1 and 3 I still can't get to work
 My question about #1 is, how do you know what the relative path is
 relative too?? I my mind it should be relative to the stylesheet that's
 calling it  but in my experience that doesn't work at all.

 For example if I have this setup:
 directory
 - doc.xsl (which does a dynamic transform with Xalan into an FO
 document)
 - logo.jpg

 The src=logo.jpg tag makes FOP complain about  the Invalid URL image.

 thanks
 Mike
 On Wednesday, March 13, 2002, at 08:44  AM, Magnus Sjöberg wrote:

  Ok, you got me started. I looked into this and found out the
  following ;-)
 
  In the xsl spec., the src attribute for
  fo:external-graphic is specified to contain a
  'uri-specification'
  For all I know, this is the URI definition as defined in
  RFC2396.
  Looking into this and comparing the three attribute values
  that failed I came up with this:
 
  1) src=logo.jpg
  This should work since 'logo.jpg' is a correct relative URI
  according to the BNF
 
  2) src=file:./logo.jpg
  This should also work since 'file:./logo.jpg' defines a
  correct absoluteURI.
 
  3) src=file://./logo.jpg
  This defines an absolute URI, but the file:// should be
  followed by a 'server' or a 'reg_name' according to the RFC.
  I believe that the code parsing the file://./logo.jpg treats
  the . after 'file://' as a server name, hence the URL error.
 
  Of the three I got 1 and 2 working using Fop-0.20.2,
  Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h
  o u l d work).
  Example 3 failed, complaining about Invalid Image URL -
  error on relative URL, which I believe is a correct error
  message.
  The relative URL really is incorrect.
 
  I also used a relative URI as in
  src=/root/path/to/images/image.jpg, which worked. (Note
  the missing file:)
 
  Hope this 'clears' up some of the fog.
 
  Rgds///
Magnus

--

Secode - Total Internet Security
Magnus Sjöberg
Research And Development

email: [EMAIL PROTECTED]
cell: +46 709 150 710
POTS: +46 8 564 875 05
http://www.secode.com

Internet is to be a safe area for business, transactions and
information exchange



AW: SV: SV: external-graphic src syntax

2002-03-13 Thread S. Jayaraman
Hi


Sorry I goofed the earlier mail.

I think if you are running under tomcat, the BASE directory is tomcat/bin
If you are running from command line, Java_home is the BASE dir
Rgds
Jay



-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Magnus
Sjöberg
Gesendet: Mittwoch, 13. März 2002 15:59
An: [EMAIL PROTECTED]
Betreff: Re: SV: SV: external-graphic src syntax


That's bizarre, I 'assumed' FOP used the current directory
as its base dir...
I ran the following command with test.xml, test.xsl and
image.jpg in the current directory:

current_dir java org.apache.fop.apps.Fop -xml test.xml -xsl
test.xsl -pdf test.pdf

All images in the xml are added to the fo using
fo:external-graphic src=image.jpg/
This produces no errors.
Exactly what sequence of events are you using to create the
PDF?

///Magnus

Michael Engelhart wrote:

 Thanks Mangus,

 That's great info.  (Maybe we can get it stuck into the FAQ? )

 I know have 2 working fine.  1 and 3 I still can't get to work
 My question about #1 is, how do you know what the relative path is
 relative too?? I my mind it should be relative to the stylesheet that's
 calling it  but in my experience that doesn't work at all.

 For example if I have this setup:
 directory
 - doc.xsl (which does a dynamic transform with Xalan into an FO
 document)
 - logo.jpg

 The src=logo.jpg tag makes FOP complain about  the Invalid URL image.

 thanks
 Mike
 On Wednesday, March 13, 2002, at 08:44  AM, Magnus Sjöberg wrote:

  Ok, you got me started. I looked into this and found out the
  following ;-)
 
  In the xsl spec., the src attribute for
  fo:external-graphic is specified to contain a
  'uri-specification'
  For all I know, this is the URI definition as defined in
  RFC2396.
  Looking into this and comparing the three attribute values
  that failed I came up with this:
 
  1) src=logo.jpg
  This should work since 'logo.jpg' is a correct relative URI
  according to the BNF
 
  2) src=file:./logo.jpg
  This should also work since 'file:./logo.jpg' defines a
  correct absoluteURI.
 
  3) src=file://./logo.jpg
  This defines an absolute URI, but the file:// should be
  followed by a 'server' or a 'reg_name' according to the RFC.
  I believe that the code parsing the file://./logo.jpg treats
  the . after 'file://' as a server name, hence the URL error.
 
  Of the three I got 1 and 2 working using Fop-0.20.2,
  Xalan-2.3.0 and Xerces-2.0.0 (which is good, since they s h
  o u l d work).
  Example 3 failed, complaining about Invalid Image URL -
  error on relative URL, which I believe is a correct error
  message.
  The relative URL really is incorrect.
 
  I also used a relative URI as in
  src=/root/path/to/images/image.jpg, which worked. (Note
  the missing file:)
 
  Hope this 'clears' up some of the fog.
 
  Rgds///
Magnus

--

Secode - Total Internet Security
Magnus Sjöberg
Research And Development

email: [EMAIL PROTECTED]
cell: +46 709 150 710
POTS: +46 8 564 875 05
http://www.secode.com

Internet is to be a safe area for business, transactions and
information exchange



AW: FopImageFactory caches too aggressively

2002-03-07 Thread S. Jayaraman
I think, this is a good method to be made available.
If the system is used to print manuals involving a lot of diagrams, this
call would be very useful (if different types of manuals are printed in
sequence.
But this will not solve the problem of one fo file having a number of
complex (large) diagrams, unless the renderer itself keeps flushing the
cache.. Is any such thing foreseen as an option to the renderer ?

Rgds
Jay


-Ursprüngliche Nachricht-
Von: Peter Murray [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 7. März 2002 15:57
An: [EMAIL PROTECTED]
Betreff: FopImageFactory caches too aggressively



Greetings group,

The FopImageFactory class appears to cache all references to images from
within rendered fop documents.  If you are running FOP in a server process,
(a) this might cause a memory problem and (b) if images change between
renderings (as they do in my case), I get the old copy of the image rather
than the latest.

How would people feel about adding a static method
FopImageFactory.clearCache()?  Of course, this won't really be what is
needed 'cause if you are rendering fops in multiple threads, you might want
the cache to be a little more persistent than if each thread is flushing it
after rendering a fop...

What do folks think about this?

-pete

--

Peter M. Murray
s u b x, i n c.
428 Fore Street
4th Floor
Portland, Maine 04101
v. 207.775.0808
f. 617.249.0617
[EMAIL PROTECTED]



AW: watermarking

2002-03-06 Thread S. Jayaraman
Will I be still able to put a watermark across the middle of my page ?
Rgds
Jay

***

Use the region-before.  Make it large enough to contain your image and then
include a block (and if required an absolutely positioned block-container)
with your image in the static-content for the region-before.
(BTW this is the same technique as used in MS Word).

Trev

**

hello all

Is there any way of adding some kind of watermark to a PDF document
generated with FOP ? I am using FOP in a JSP environment.

Thanks

Chris








AW: Just a quick one.

2002-03-01 Thread S. Jayaraman
OOps. Sorry .. forgot to add.
The indent=0 not put for the first column.
And lucky for me, the tables did not have borders printed. I admit that it
would have been horrible to look at.
Rgds
Jay

-Ursprüngliche Nachricht-
Von: S. Jayaraman [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 1. März 2002 09:24
An: [EMAIL PROTECTED]
Betreff: AW: Just a quick one.


I had the same problem. But since I did not use XSL, with Java I could
recognize the situation and put indent=0 for the the fo:block in the table
cell. I know this is a work around only. Let us hope for a proper solution.
Rgds
Jay


-Ursprüngliche Nachricht-
Von: Paul Campbell [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 1. März 2002 02:08
An: [EMAIL PROTECTED]
Betreff: Just a quick one.



Page numbers, and table borders.

fo:page-number/ Okay, but fo:page-count/ or fo:page-total/ or
fo:last-page/  Any Ideas?  I know it's been asked before, but I been
through
the docs twice, and have come out empty handed.

Table borders.  My documents are built on nested lists, with inherited
indents.
I placed a table in a list item and it aligns to the absolute left not the
list
start indent.  Worse than that, the text in the table cell aligns properly,
so
it looks a mess.  Anyone suggestions about how to align the table border to
the
actual table contents or force it in a bit?

Is it worth it to rewrite my XSLT to base the document on a table model
instead?  Like the usual HTML stuff?

Thanks

Paul



AW: calling fop from java

2002-02-28 Thread S. Jayaraman
Hi

This is an extract from the site:   http://xml.apache.org/fop/embedding.html

  Driver driver = new Driver();
  driver.setRenderer(Driver.RENDER_PDF);
  InputHandler inputHandler = new XSLTInputHandler(xmlFile, xslFile);
  XMLReader parser = inputHandler.getParser();
  driver.setOutputStream(new FileOutputStream(outFile));
  driver.render(parser, inputHandler.getInputSource());



The above code should do it.
Rgds
Jay


-Ursprüngliche Nachricht-
Von: Fischer Tibor [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 28. Februar 2002 15:07
An: [EMAIL PROTECTED]
Betreff: Re: calling fop from java


that's ok,
sorry but i didn't said, that i have an xml, and an xsl file, and i have
to generate the pdf from them

Fishy

Alexandre Denes dos Santos wrote:

Use:

Driver driver = new Driver(InputStream in, OutputStream out);
driver.setRenderer(Driver.RENDER_PDF);

driver.run();

where in is the inputStream to the fo file that you will render and
out is the outputstream where the pdf content will be write to.

The package is org.apache.fop.apps.

Hope that helps.

Denes



- Original Message -
From: Fischer Tibor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 10:50 AM
Subject: calling fop from java


hi

i would like to call the fop's transformation procedure from a running
java application, to create pdf  realtime

how is it possible??
what method sholud i call??

Thanks,
Fishy











Watermarks

2002-02-20 Thread S. Jayaraman
Hi

Is it possible to have pages printed out with watermarks ?

Thanx in advance
Rgds
Jay


---
S. Jayaraman
Consor AG
Ottikerstr. 14
CH-8006 Zurich 
Switzerland

email - [EMAIL PROTECTED]
phone - +41 1 368 35 36 
fax - +41 1 368 35 99
 BITTE BEACHTEN 
Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet möglicherweise
vertrauliche oder gesetzlich geschützte Daten oder Informationen. Zum
Empfang derselben ist (sind) ausschliesslich die genannte(n) Person(en)
bestimmt. Falls Sie diese Nachricht irrtümlicherweise erreicht hat, sind Sie
höflich gebeten, diese unter Ausschluss jeder Reproduktion zu zerstören und
die absendende Person umgehend zu benachrichtigen. Vielen Dank für Ihre
Hilfe.



attachment: winmail.dat

FO--PDF Renderer Driver Error

2002-02-19 Thread S. Jayaraman
Hello,

I got the following error in my Servlet.
I have attached the relevant lines from my source program.
The code works on NT but blows in the Solaris version.
Would be happy at some pointers (I could see the method, when I saw the
FOP.JAR file) (FOP Version 0.19.)


Error: 500
Location: /universal/servlet/servPrintDoc
Internal Servlet Error:

java.lang.NoSuchMethodError:org.apache.fop.apps.Driver: method
addPropertyList(Ljava/lang/String;)V not found
at consor.universal.print.buildOutput.writePDF(buildOutput.java:176)
at consor.universal.print.XMLToFO.process(XMLToFO.java:87)
at servPrintDoc.doGet(servPrintDoc.java:65)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
at org.apache.tomcat.core.Handler.service(Handler.java:286)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79
7)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection
(Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)



My SOurceCode extract

driver.setRenderer(org.apache.fop.render.pdf.PDFRenderer,
Version.getVersion());

driver.addElementMapping(org.apache.fop.fo.StandardElementMapping);

driver.addElementMapping(org.apache.fop.svg.SVGElementMapping);

driver.addPropertyList(org.apache.fop.fo.StandardPropertyListMapping);
//OFFENDING LINE (Line#176)

driver.addPropertyList(org.apache.fop.svg.SVGPropertyListMapping);


Thank YOu
Kind Rgds
Jay



---
S. Jayaraman
Consor AG
Ottikerstr. 14
CH-8006 Zurich
Switzerland

email - [EMAIL PROTECTED]
phone - +41 1 368 35 36
fax - +41 1 368 35 99
 BITTE BEACHTEN 
Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet möglicherweise
vertrauliche oder gesetzlich geschützte Daten oder Informationen. Zum
Empfang derselben ist (sind) ausschliesslich die genannte(n) Person(en)
bestimmt. Falls Sie diese Nachricht irrtümlicherweise erreicht hat, sind Sie
höflich gebeten, diese unter Ausschluss jeder Reproduktion zu zerstören und
die absendende Person umgehend zu benachrichtigen. Vielen Dank für Ihre
Hilfe.