RE: FOP 0.9.5 and Too many Files Open...image Files in my case...

2010-12-07 Thread Nuvvula, Durga
Hi Peter,

Sorry for late reply, Thanks for your email!!!

I have tried the first option of setting the system property in the start up 
and it was not solving my problem with the number of open files.

I have tried updating the FOP 0.9.5 to FOP 1.0 and the number of open file 
descriptors problem seems to be solved. I have tested and it works for me.

Best Regards,
Durga

-Original Message-
From: Peter Hancock [mailto:peter.hanc...@gmail.com]
Sent: Thursday, November 18, 2010 3:31 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: FOP 0.9.5 and Too many Files Open...image Files in my case...

Hi Durga,

Before trying to resolve this particular issue, are you able to
upgrade to 1.0?  It is possible that your particular issue has been
resolved after 0.95.
There are threads on the mailing list that report similiar problems, e.g.
http://old.nabble.com/Too-many-open-images--td25664263.html#a25664263
http://old.nabble.com/Keeping-memory-usage-low-when-FOP-is-not-running-and-avoid-open-file-handles-after-FOP-is-run-td29202650.html#a29205862

Let me know if you want further help

Pete

On Wed, Nov 17, 2010 at 3:49 PM, Nuvvula, Durga  wrote:
> Hi,
>
>
>
> I am using the FOP 0.9.5 for my pdf generation. I have made sure that I have
> closed all the input streams that I have opened for pdf generation.
>
>
>
> I am not opening the image files(.tiff,.gif,.png etc) directly but I am
> using them in my XSL. I have made sure that my xsl stream is closed properly
> in the finally block.
>
>
>
> When I track the number of open files through lsof, I am observing the image
> files(.tiff,.gif,.png etc) not closed because of this it is reaching the
> limit of number of open files and have to restart the server. Our server has
> the configuration of open files to 1024.
>
>
>
> Do I need to do anything extra for closing the image files that have opened
> by the FOP internally?
>
>
>
> Any help or suggestions towards the resolution of the problem is
> appreciated.
>
>
>
> Thanks In Advance.
>
>
>
> Best Regards,
>
> Durga Prasad
>
> 46943895956
>
>

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: AW: ValidationException: Document is empty

2010-12-07 Thread J.Pietschmann

On 07.12.2010 16:39, Georg Datterl wrote:


http://www.w3.org/1999/XSL/Transform";>
 
 
 http://www.w3.org/1999/XSL/Format";>
 
 



 
 ">


That's not how XSLT is supposed to work.
If you want to use a variable for page-height, use an attribute value
template:
 

Google for further details, or buy Michael Kay's book.

J.Pietschmann

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



RE: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
Did you read the links I included?  Xslt does not contain fo.  Xslt can include 
fo tags which would make it xslfo which can be transformed with an xml to 
generate fo.  Xslt can be used without any fo tags to generate web content.  
FOP requires either xslfo + xml or fo which is that intermediate result of 
xslfo + xml you're seeing in the 2 step transformation.  The difference between 
the xslt and xslfo is the fo tags which tell it how to generate a document, 
which provides information such as page breaks which you wouldn't have on the 
web.  While your xslt file with the < tags in it did pass an xsl validation 
with one free program I found to verify syntax, it's not standard code to start 
a tag with < and end with >.

If you can break the code with variables I'd like to see a sample.  I use 
plenty of variables in my xsl.
If you cannot transform your xml+xslt->pdf with fop 1.0 with the < 
references converted to < please send what error message you're seeing.  That 
works fine here.

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, December 07, 2010 11:44 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

> I think you're a bit confused.

Oh yes.

> 1) FOP doesn't complain about anything.  My response included the corrected 
> xslt along with a PDF I got from FOP with it.

I'm not quite sure WHO exactly complains. The original xslt (with <) works 
fine if I use it to transform the xml file. It generates a fo-file which I can 
then transform into a pdf. The corrected xslt works fine, if I don't use more 
complex transformations. It stops working when I use variables.

> 2) I'm not sure what you mean by "valid xml".  Your xml file is a 
> valid xml.  Your xslt file is not xslt if it contains any fo.  If you fix the 
> tags it's valid xslfo.

My xslt should not contain valid fo, it should create valid fo. If I fix the 
tags, it's (IMHO) no longer a valid xslt-file.

> 3) Converting < to < wouldn't make it work any better as anything 
> else since you didn't convert > to >

Converting < to < would make it a valid xslt-file, IMHO, since the fo-tags 
are no longer found. The transformation originally worked fine with fop 0.20, 
so it is possible that something changed, but that would still not explain why 
I can transform xml+xslt->fo and fo->pdf, but not xml+xslt->pdf directly.

Regards

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 17:25
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

I think you're a bit confused.
1) FOP doesn't complain about anything.  My response included the corrected 
xslt along with a PDF I got from FOP with it.
2) I'm not sure what you mean by "valid xml".  Your xml file is a valid xml.  
Your xslt file is not xslt if it contains any fo.  If you fix the tags it's 
valid xslfo.
3) Converting < to < wouldn't make it work any better as anything else since 
you didn't convert > to >

Xslt: http://www.w3schools.com/xsl/default.asp
Xslfo: http://www.w3schools.com/xslfo/default.asp

Xslt was designed to format xml data for a web page.  Xslfo expands on xslt to 
add the pageable tags required for a PDF which a web page wouldn't understand.

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 10:40 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

You are right. But. Of course there's a but...
Let me expand my transformation a little bit:


http://www.w3.org/1999/XSL/Transform";>


http://www.w3.org/1999/XSL/Format";>


"   >



  
  





Now fop (actually: the sax parser) complains about the < in page-height. Quite 
understandable, I think. And the whole transformation is no longer valid xml, 
since the fo tags are mixed into the xsl tags.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated

RE: AW: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
If you can write your own code you could do the 2 step transformation to avoid 
the issue without writing the FO file to disk.
FOP allows you to receive the results as streaming bytes which you can send 
right back in as an FO SAXSource. 

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, December 07, 2010 12:17 PM
To: fop-users@xmlgraphics.apache.org
Subject: AW: AW: ValidationException: Document is empty

Hi Chris,

I think that's the important point. I'll rewrite my transformation tomorrow and 
have a look. Thanks a lot. Oh, and 20 points for the plausible explanation.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Christopher R. Maden [mailto:cr...@maden.org]
Gesendet: Dienstag, 7. Dezember 2010 17:48
An: fop-users@xmlgraphics.apache.org
Betreff: Re: AW: ValidationException: Document is empty

On 12/07/2010 11:43 AM, Georg Datterl wrote:
> I'm not quite sure WHO exactly complains. The original xslt (with
> <) works fine if I use it to transform the xml file. It generates a 
> fo-file which I can then transform into a pdf. The corrected xslt 
> works fine, if I don't use more complex transformations. It stops 
> working when I use variables.

Ah... I've got it now.

This is why use of disable-output-escaping is so strongly discouraged...

When you use XSLT to transform your XML and serialize it to disk, the d-o-e is 
applied and you get a valid FO.

However, when you feed XML and XSLT to FOP, your transformation result is never 
serialized.  The d-o-e directive is never applied, and a poorly-formed XML data 
structure is passed to FOP, resulting in your error.

You will need to rewrite your transformation to avoid use of d-o-e.  It is an 
unfortunate hack that really shouldn't have been included in XSLT; it is never 
necessary, and while it enables some quick hacks that would be more complicated 
otherwise, it also is prone to mysterious breakage like your case.

~Chris
--
Chris Maden, text nerd  http://crism.maden.org/ >
 MISSING: land of free, home of brave.
 Last seen 10 September 2001.  Reward offered.
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



AW: AW: ValidationException: Document is empty

2010-12-07 Thread Georg Datterl
Hi Chris,

I think that's the important point. I'll rewrite my transformation tomorrow and 
have a look. Thanks a lot. Oh, and 20 points for the plausible explanation.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Christopher R. Maden [mailto:cr...@maden.org]
Gesendet: Dienstag, 7. Dezember 2010 17:48
An: fop-users@xmlgraphics.apache.org
Betreff: Re: AW: ValidationException: Document is empty

On 12/07/2010 11:43 AM, Georg Datterl wrote:
> I'm not quite sure WHO exactly complains. The original xslt (with
> <) works fine if I use it to transform the xml file. It generates
> a fo-file which I can then transform into a pdf. The corrected xslt
> works fine, if I don't use more complex transformations. It stops
> working when I use variables.

Ah... I’ve got it now.

This is why use of disable-output-escaping is so strongly discouraged...

When you use XSLT to transform your XML and serialize it to disk, the
d-o-e is applied and you get a valid FO.

However, when you feed XML and XSLT to FOP, your transformation result
is never serialized.  The d-o-e directive is never applied, and a
poorly-formed XML data structure is passed to FOP, resulting in your error.

You will need to rewrite your transformation to avoid use of d-o-e.  It
is an unfortunate hack that really shouldn’t have been included in XSLT;
it is never necessary, and while it enables some quick hacks that would
be more complicated otherwise, it also is prone to mysterious breakage
like your case.

~Chris
--
Chris Maden, text nerd  http://crism.maden.org/ >
 MISSING: land of free, home of brave.
 Last seen 10 September 2001.  Reward offered.
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: AW: ValidationException: Document is empty

2010-12-07 Thread Christopher R. Maden
On 12/07/2010 11:43 AM, Georg Datterl wrote:
> I'm not quite sure WHO exactly complains. The original xslt (with
> <) works fine if I use it to transform the xml file. It generates
> a fo-file which I can then transform into a pdf. The corrected xslt
> works fine, if I don't use more complex transformations. It stops
> working when I use variables.

Ah... I’ve got it now.

This is why use of disable-output-escaping is so strongly discouraged...

When you use XSLT to transform your XML and serialize it to disk, the
d-o-e is applied and you get a valid FO.

However, when you feed XML and XSLT to FOP, your transformation result
is never serialized.  The d-o-e directive is never applied, and a
poorly-formed XML data structure is passed to FOP, resulting in your error.

You will need to rewrite your transformation to avoid use of d-o-e.  It
is an unfortunate hack that really shouldn’t have been included in XSLT;
it is never necessary, and while it enables some quick hacks that would
be more complicated otherwise, it also is prone to mysterious breakage
like your case.

~Chris
-- 
Chris Maden, text nerd  http://crism.maden.org/ >
 MISSING: land of free, home of brave.
 Last seen 10 September 2001.  Reward offered.
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



AW: ValidationException: Document is empty

2010-12-07 Thread Georg Datterl
Hi Eric,

> I think you're a bit confused.

Oh yes.

> 1) FOP doesn't complain about anything.  My response included the corrected 
> xslt along with a PDF I got from FOP with it.

I'm not quite sure WHO exactly complains. The original xslt (with <) works 
fine if I use it to transform the xml file. It generates a fo-file which I can 
then transform into a pdf. The corrected xslt works fine, if I don't use more 
complex transformations. It stops working when I use variables.

> 2) I'm not sure what you mean by "valid xml".  Your xml file is a valid xml.  
> Your xslt file is not xslt if it contains any
> fo.  If you fix the tags it's valid xslfo.

My xslt should not contain valid fo, it should create valid fo. If I fix the 
tags, it's (IMHO) no longer a valid xslt-file.

> 3) Converting < to < wouldn't make it work any better as anything else 
> since you didn't convert > to >

Converting < to < would make it a valid xslt-file, IMHO, since the fo-tags 
are no longer found. The transformation originally worked fine with fop 0.20, 
so it is possible that something changed, but that would still not explain why 
I can transform xml+xslt->fo and fo->pdf, but not xml+xslt->pdf directly.

Regards

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 17:25
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

I think you're a bit confused.
1) FOP doesn't complain about anything.  My response included the corrected 
xslt along with a PDF I got from FOP with it.
2) I'm not sure what you mean by "valid xml".  Your xml file is a valid xml.  
Your xslt file is not xslt if it contains any fo.  If you fix the tags it's 
valid xslfo.
3) Converting < to < wouldn't make it work any better as anything else since 
you didn't convert > to >

Xslt: http://www.w3schools.com/xsl/default.asp
Xslfo: http://www.w3schools.com/xslfo/default.asp

Xslt was designed to format xml data for a web page.  Xslfo expands on xslt to 
add the pageable tags required for a PDF which a web page wouldn't understand.

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 10:40 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

You are right. But. Of course there's a but...
Let me expand my transformation a little bit:


http://www.w3.org/1999/XSL/Transform";>


http://www.w3.org/1999/XSL/Format";>


"   >



  
  





Now fop (actually: the sax parser) complains about the < in page-height. Quite 
understandable, I think. And the whole transformation is no longer valid xml, 
since the fo tags are mixed into the xsl tags.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:21
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That seems a strange thing to do but yes that works fine.  FOP just doesn't 
like html in the xslt.
Replace all < with < and you get an empty document.


-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 10:08 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

Indeed, the xml is nearly empty, but I'd expect a one-page document with one 
flow and one block inside.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.

RE: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
I think you're a bit confused.
1) FOP doesn't complain about anything.  My response included the corrected 
xslt along with a PDF I got from FOP with it.
2) I'm not sure what you mean by "valid xml".  Your xml file is a valid xml.  
Your xslt file is not xslt if it contains any fo.  If you fix the tags it's 
valid xslfo.
3) Converting < to < wouldn't make it work any better as anything else since 
you didn't convert > to >

Xslt: http://www.w3schools.com/xsl/default.asp
Xslfo: http://www.w3schools.com/xslfo/default.asp

Xslt was designed to format xml data for a web page.  Xslfo expands on xslt to 
add the pageable tags required for a PDF which a web page wouldn't understand.

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, December 07, 2010 10:40 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

You are right. But. Of course there's a but...
Let me expand my transformation a little bit:


http://www.w3.org/1999/XSL/Transform";>


http://www.w3.org/1999/XSL/Format";>


"   >



  
  





Now fop (actually: the sax parser) complains about the < in page-height. Quite 
understandable, I think. And the whole transformation is no longer valid xml, 
since the fo tags are mixed into the xsl tags.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:21
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That seems a strange thing to do but yes that works fine.  FOP just doesn't 
like html in the xslt.
Replace all < with < and you get an empty document.


-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 10:08 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

Indeed, the xml is nearly empty, but I'd expect a one-page document with one 
flow and one block inside.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:05
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That would be because your document is empty.  Am I missing something here?  
This is the entire text of the xml you attached:



-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 9:30 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgrap

RE: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
Yes, that is the point of the < code, to be able to print the < symbol in 
your output without confusing it with a tag.
As such, codes should never be used in the HTML which tells the processor how 
to interpret the data. 

-Original Message-
From: Amick, Eric [mailto:eric.am...@mail.house.gov] 
Sent: Tuesday, December 07, 2010 10:37 AM
To: 'fop-users@xmlgraphics.apache.org'
Subject: RE: ValidationException: Document is empty

If I may jump in here, I think it's more fundamental. I don't believe the XML 
standard allows using entities as a part of start and end tags like that.

Eric Amick   Systems Engineer II
Legislative Computer Systems

> -Original Message-
> From: Eric Douglas [mailto:edoug...@blockhouse.com]
> Sent: Tuesday, December 7, 2010 10:21
> To: fop-users@xmlgraphics.apache.org
> Subject: RE: ValidationException: Document is empty
> 
> That seems a strange thing to do but yes that works fine.  FOP just 
> doesn't like html in the xslt.
> Replace all < with < and you get an empty document.
> 
> 
> -Original Message-
> From: Georg Datterl [mailto:georg.datt...@geneon.de]
> Sent: Tuesday, December 07, 2010 10:08 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: AW: ValidationException: Document is empty
> 
> Hi Eric,
> 
> Indeed, the xml is nearly empty, but I'd expect a one-page document 
> with one flow and one block inside.
> 
> Regards,
> 
> Georg Datterl
> 
> -- Kontakt --
> 
> Georg Datterl
> 
> Geneon media solutions gmbh
> Gutenstetter Straße 8a
> 90449 Nürnberg
> 
> HRB Nürnberg: 17193
> Geschäftsführer: Yong-Harry Steiert
> 
> Tel.: 0911/36 78 88 - 26
> Fax: 0911/36 78 88 - 20
> 
> www.geneon.de
> 
> Weitere Mitglieder der Willmy MediaGroup:
> 
> IRS Integrated Realization Services GmbH:www.irs-nbg.de
> Willmy PrintMedia GmbH:www.willmy.de
> Willmy Consult & Content GmbH: www.willmycc.de
> 
> 
> -Ursprüngliche Nachricht-
> Von: Eric Douglas [mailto:edoug...@blockhouse.com]
> Gesendet: Dienstag, 7. Dezember 2010 16:05
> An: fop-users@xmlgraphics.apache.org
> Betreff: RE: ValidationException: Document is empty
> 
> That would be because your document is empty.  Am I missing something 
> here?  This is the entire text of the xml you attached:
> 
> 
> 
> -Original Message-
> From: Georg Datterl [mailto:georg.datt...@geneon.de]
> Sent: Tuesday, December 07, 2010 9:30 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: AW: ValidationException: Document is empty
> 
> Hi everybody,
> 
> Since nobody yet provided an answer,  let's make it easier to debug.
> Here are a really short xml and a really short and simple 
> transformation. The call to fop is
> 
> org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl 
> test/xsl/billing.xslt -pdf c:\temp\test2.pdf
> 
> Fop version is the latest trunk.
> Error message is: org.apache.fop.fo.ValidationException: Document is 
> empty (something might be wrong with your XSLT stylesheet).
> Confused is: me. What could be wrong with my stylesheet?
> 
> (Yes, I know we don't like xml and xslts here, but obviously I can't 
> provide anything else)
> 
> Regards,
> 
> Georg Datterl
> 
> -- Kontakt --
> 
> Georg Datterl
> 
> Geneon media solutions gmbh
> Gutenstetter Straße 8a
> 90449 Nürnberg
> 
> HRB Nürnberg: 17193
> Geschäftsführer: Yong-Harry Steiert
> 
> Tel.: 0911/36 78 88 - 26
> Fax: 0911/36 78 88 - 20
> 
> www.geneon.de
> 
> Weitere Mitglieder der Willmy MediaGroup:
> 
> IRS Integrated Realization Services GmbH:www.irs-nbg.de
> Willmy PrintMedia GmbH:www.willmy.de
> Willmy Consult & Content GmbH: www.willmycc.de
> 
> 
> -Ursprüngliche Nachricht-
> Von: Georg Datterl
> Gesendet: Freitag, 3. Dezember 2010 18:22
> An: 'fop-users@xmlgraphics.apache.org'
> Betreff: ValidationException: Document is empty
> 
> Hi folks,
> 
> Another funny question from yours truly. It's been some time since our 
> last quiz show and maybe this time we get a new winner. Anyway, here's 
> todays problem:
> 
> Given:
> * FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 
> 2.6.2, through maven, but I get the same results with a 
> shortly-before- 1.0-release version of trunk and XmlSpy
> * * A simple xml file
> * An equally simple transformation file, one page layout, a few 
> blocks, two tables with blocks, two borders.
> Wanted:
> * A simple PDF, one page, no images.
> 
> Problem:
> * When applying the transformation, I get a fo file which I can 
> transform into a pdf. Everything works fine.
> * When running the xml and the xslt through fop (following 
> ExampleXML2FO), I get the fo file which I can transform into PDF. 
> Looks ok.
> * When running the xml and the xslt through fop (following
> ExampleXML2PDF) with MimeConstants.MIME_FOP_AREA_TREE, I get the area 
> tree. Looks ok.
> * When running the xml and the xslt through fop (following
> ExampleXML2PDF) with MimeConstants.MIME_PDF, I get
> 
>  [

AW: ValidationException: Document is empty

2010-12-07 Thread Georg Datterl
Hi Eric,

You are right. But. Of course there's a but...
Let me expand my transformation a little bit:


http://www.w3.org/1999/XSL/Transform";>


http://www.w3.org/1999/XSL/Format";>


"   >



  
  





Now fop (actually: the sax parser) complains about the < in page-height. Quite 
understandable, I think. And the whole transformation is no longer valid xml, 
since the fo tags are mixed into the xsl tags.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:21
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That seems a strange thing to do but yes that works fine.  FOP just doesn't 
like html in the xslt.
Replace all < with < and you get an empty document.


-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 10:08 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

Indeed, the xml is nearly empty, but I'd expect a one-page document with one 
flow and one block inside.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:05
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That would be because your document is empty.  Am I missing something here?  
This is the entire text of the xml you attached:



-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 9:30 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgraphics.apache.org'
Betreff: ValidationException: Document is empty

Hi folks,

Another funny question from yours truly. It's been some time since our last 
quiz show and maybe this time we get a new winner. Anyway, here's todays 
problem:

Given:
* FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 2.6.2, 
through maven, but I get the same results with a shortly-before-1.0-release 
version of trunk and XmlSpy
* * A simple xml file
* An equally simple transformation file, one page layout, a few blocks, two 
tables with blocks, two borders.
Wanted:
* A simple PDF, one page, no images.

Problem:
* When applying the transformation, I get a fo file which I can transform into 
a pdf. Everything works fine.
* When running the xml and the xslt through fop (following ExampleXML2FO), I 
get the fo file which I can transform into PDF. Looks ok.
* When running the xml and the xslt throu

RE: ValidationException: Document is empty

2010-12-07 Thread Amick, Eric
If I may jump in here, I think it's more fundamental. I don't believe the XML 
standard allows using entities as a part of start and end tags like that.

Eric Amick   Systems Engineer II
Legislative Computer Systems

> -Original Message-
> From: Eric Douglas [mailto:edoug...@blockhouse.com]
> Sent: Tuesday, December 7, 2010 10:21
> To: fop-users@xmlgraphics.apache.org
> Subject: RE: ValidationException: Document is empty
> 
> That seems a strange thing to do but yes that works fine.  FOP just
> doesn't like html in the xslt.
> Replace all < with < and you get an empty document.
> 
> 
> -Original Message-
> From: Georg Datterl [mailto:georg.datt...@geneon.de]
> Sent: Tuesday, December 07, 2010 10:08 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: AW: ValidationException: Document is empty
> 
> Hi Eric,
> 
> Indeed, the xml is nearly empty, but I'd expect a one-page document
> with one flow and one block inside.
> 
> Regards,
> 
> Georg Datterl
> 
> -- Kontakt --
> 
> Georg Datterl
> 
> Geneon media solutions gmbh
> Gutenstetter Straße 8a
> 90449 Nürnberg
> 
> HRB Nürnberg: 17193
> Geschäftsführer: Yong-Harry Steiert
> 
> Tel.: 0911/36 78 88 - 26
> Fax: 0911/36 78 88 - 20
> 
> www.geneon.de
> 
> Weitere Mitglieder der Willmy MediaGroup:
> 
> IRS Integrated Realization Services GmbH:www.irs-nbg.de
> Willmy PrintMedia GmbH:www.willmy.de
> Willmy Consult & Content GmbH: www.willmycc.de
> 
> 
> -Ursprüngliche Nachricht-
> Von: Eric Douglas [mailto:edoug...@blockhouse.com]
> Gesendet: Dienstag, 7. Dezember 2010 16:05
> An: fop-users@xmlgraphics.apache.org
> Betreff: RE: ValidationException: Document is empty
> 
> That would be because your document is empty.  Am I missing something
> here?  This is the entire text of the xml you attached:
> 
> 
> 
> -Original Message-
> From: Georg Datterl [mailto:georg.datt...@geneon.de]
> Sent: Tuesday, December 07, 2010 9:30 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: AW: ValidationException: Document is empty
> 
> Hi everybody,
> 
> Since nobody yet provided an answer,  let's make it easier to debug.
> Here are a really short xml and a really short and simple
> transformation. The call to fop is
> 
> org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl
> test/xsl/billing.xslt -pdf c:\temp\test2.pdf
> 
> Fop version is the latest trunk.
> Error message is: org.apache.fop.fo.ValidationException: Document is
> empty (something might be wrong with your XSLT stylesheet).
> Confused is: me. What could be wrong with my stylesheet?
> 
> (Yes, I know we don't like xml and xslts here, but obviously I can't
> provide anything else)
> 
> Regards,
> 
> Georg Datterl
> 
> -- Kontakt --
> 
> Georg Datterl
> 
> Geneon media solutions gmbh
> Gutenstetter Straße 8a
> 90449 Nürnberg
> 
> HRB Nürnberg: 17193
> Geschäftsführer: Yong-Harry Steiert
> 
> Tel.: 0911/36 78 88 - 26
> Fax: 0911/36 78 88 - 20
> 
> www.geneon.de
> 
> Weitere Mitglieder der Willmy MediaGroup:
> 
> IRS Integrated Realization Services GmbH:www.irs-nbg.de
> Willmy PrintMedia GmbH:www.willmy.de
> Willmy Consult & Content GmbH: www.willmycc.de
> 
> 
> -Ursprüngliche Nachricht-
> Von: Georg Datterl
> Gesendet: Freitag, 3. Dezember 2010 18:22
> An: 'fop-users@xmlgraphics.apache.org'
> Betreff: ValidationException: Document is empty
> 
> Hi folks,
> 
> Another funny question from yours truly. It's been some time since our
> last quiz show and maybe this time we get a new winner. Anyway, here's
> todays problem:
> 
> Given:
> * FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes
> 2.6.2, through maven, but I get the same results with a shortly-before-
> 1.0-release version of trunk and XmlSpy
> * * A simple xml file
> * An equally simple transformation file, one page layout, a few blocks,
> two tables with blocks, two borders.
> Wanted:
> * A simple PDF, one page, no images.
> 
> Problem:
> * When applying the transformation, I get a fo file which I can
> transform into a pdf. Everything works fine.
> * When running the xml and the xslt through fop (following
> ExampleXML2FO), I get the fo file which I can transform into PDF. Looks
> ok.
> * When running the xml and the xslt through fop (following
> ExampleXML2PDF) with MimeConstants.MIME_FOP_AREA_TREE, I get the area
> tree. Looks ok.
> * When running the xml and the xslt through fop (following
> ExampleXML2PDF) with MimeConstants.MIME_PDF, I get
> 
>  [org.apache.fop.fo.FOTreeBuilder] ->
> org.apache.fop.fo.ValidationException: Document is empty (something
> might be wrong with your XSLT stylesheet).
> 
> * When combining ExampleXML2FO and ExampleXML2PDF and using two
> transformations (XML->FO, FO->Area tree), I get a correct Area tree.
> * When combining ExampleXML2FO and ExampleXML2PDF and using two
> transformations (XML->FO, FO->PDF), I get a pdf, which should have one
> PageSequence with one p

RE: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
That seems a strange thing to do but yes that works fine.  FOP just doesn't 
like html in the xslt.
Replace all < with < and you get an empty document.
 

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, December 07, 2010 10:08 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi Eric,

Indeed, the xml is nearly empty, but I'd expect a one-page document with one 
flow and one block inside.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:05
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That would be because your document is empty.  Am I missing something here?  
This is the entire text of the xml you attached:



-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 9:30 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgraphics.apache.org'
Betreff: ValidationException: Document is empty

Hi folks,

Another funny question from yours truly. It's been some time since our last 
quiz show and maybe this time we get a new winner. Anyway, here's todays 
problem:

Given:
* FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 2.6.2, 
through maven, but I get the same results with a shortly-before-1.0-release 
version of trunk and XmlSpy
* * A simple xml file
* An equally simple transformation file, one page layout, a few blocks, two 
tables with blocks, two borders.
Wanted:
* A simple PDF, one page, no images.

Problem:
* When applying the transformation, I get a fo file which I can transform into 
a pdf. Everything works fine.
* When running the xml and the xslt through fop (following ExampleXML2FO), I 
get the fo file which I can transform into PDF. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_FOP_AREA_TREE, I get the area tree. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_PDF, I get

 [org.apache.fop.fo.FOTreeBuilder] -> org.apache.fop.fo.ValidationException: 
Document is empty (something might be wrong with your XSLT stylesheet).

* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->Area tree), I get a correct Area tree.
* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->PDF), I get a pdf, which should have one PageSequence with one 
page, according to fop.getResults(). I can't open the PDF in Acrobat (pdf 
corrupt and can't be repaired)

That's it. No error messages, no hints. Area tree works, generating a pdf does 
not. Generating a fo and then a pdf works in XmlSpy. Does anybody see any 
reasoning behind that?

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Wil

AW: ValidationException: Document is empty

2010-12-07 Thread Georg Datterl
Hi Eric,

Indeed, the xml is nearly empty, but I'd expect a one-page document with one 
flow and one block inside.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Eric Douglas [mailto:edoug...@blockhouse.com]
Gesendet: Dienstag, 7. Dezember 2010 16:05
An: fop-users@xmlgraphics.apache.org
Betreff: RE: ValidationException: Document is empty

That would be because your document is empty.  Am I missing something here?  
This is the entire text of the xml you attached:



-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Tuesday, December 07, 2010 9:30 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgraphics.apache.org'
Betreff: ValidationException: Document is empty

Hi folks,

Another funny question from yours truly. It's been some time since our last 
quiz show and maybe this time we get a new winner. Anyway, here's todays 
problem:

Given:
* FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 2.6.2, 
through maven, but I get the same results with a shortly-before-1.0-release 
version of trunk and XmlSpy
* * A simple xml file
* An equally simple transformation file, one page layout, a few blocks, two 
tables with blocks, two borders.
Wanted:
* A simple PDF, one page, no images.

Problem:
* When applying the transformation, I get a fo file which I can transform into 
a pdf. Everything works fine.
* When running the xml and the xslt through fop (following ExampleXML2FO), I 
get the fo file which I can transform into PDF. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_FOP_AREA_TREE, I get the area tree. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_PDF, I get

 [org.apache.fop.fo.FOTreeBuilder] -> org.apache.fop.fo.ValidationException: 
Document is empty (something might be wrong with your XSLT stylesheet).

* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->Area tree), I get a correct Area tree.
* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->PDF), I get a pdf, which should have one PageSequence with one 
page, according to fop.getResults(). I can't open the PDF in Acrobat (pdf 
corrupt and can't be repaired)

That's it. No error messages, no hints. Area tree works, generating a pdf does 
not. Generating a fo and then a pdf works in XmlSpy. Does anybody see any 
reasoning behind that?

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de



-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail:

RE: ValidationException: Document is empty

2010-12-07 Thread Eric Douglas
That would be because your document is empty.  Am I missing something here?  
This is the entire text of the xml you attached:

 

-Original Message-
From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, December 07, 2010 9:30 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: ValidationException: Document is empty

Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgraphics.apache.org'
Betreff: ValidationException: Document is empty

Hi folks,

Another funny question from yours truly. It's been some time since our last 
quiz show and maybe this time we get a new winner. Anyway, here's todays 
problem:

Given:
* FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 2.6.2, 
through maven, but I get the same results with a shortly-before-1.0-release 
version of trunk and XmlSpy
* * A simple xml file
* An equally simple transformation file, one page layout, a few blocks, two 
tables with blocks, two borders.
Wanted:
* A simple PDF, one page, no images.

Problem:
* When applying the transformation, I get a fo file which I can transform into 
a pdf. Everything works fine.
* When running the xml and the xslt through fop (following ExampleXML2FO), I 
get the fo file which I can transform into PDF. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_FOP_AREA_TREE, I get the area tree. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_PDF, I get

 [org.apache.fop.fo.FOTreeBuilder] -> org.apache.fop.fo.ValidationException: 
Document is empty (something might be wrong with your XSLT stylesheet).

* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->Area tree), I get a correct Area tree.
* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->PDF), I get a pdf, which should have one PageSequence with one 
page, according to fop.getResults(). I can't open the PDF in Acrobat (pdf 
corrupt and can't be repaired)

That's it. No error messages, no hints. Area tree works, generating a pdf does 
not. Generating a fo and then a pdf works in XmlSpy. Does anybody see any 
reasoning behind that?

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de



-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



AW: ValidationException: Document is empty

2010-12-07 Thread Georg Datterl
Hi everybody,

Since nobody yet provided an answer,  let's make it easier to debug. Here are a 
really short xml and a really short and simple transformation. The call to fop 
is

org.apache.fop.cli.Main -d -xml test/xml/billing.xml -xsl test/xsl/billing.xslt 
-pdf c:\temp\test2.pdf

Fop version is the latest trunk.
Error message is: org.apache.fop.fo.ValidationException: Document is empty 
(something might be wrong with your XSLT stylesheet).
Confused is: me. What could be wrong with my stylesheet?

(Yes, I know we don't like xml and xslts here, but obviously I can't provide 
anything else)

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de


-Ursprüngliche Nachricht-
Von: Georg Datterl
Gesendet: Freitag, 3. Dezember 2010 18:22
An: 'fop-users@xmlgraphics.apache.org'
Betreff: ValidationException: Document is empty

Hi folks,

Another funny question from yours truly. It's been some time since our last 
quiz show and maybe this time we get a new winner. Anyway, here's todays 
problem:

Given:
* FOP 1.0, Batik 1.7, xmlgraphics-commons 1.4, xalan 2.7.1, xerxes 2.6.2, 
through maven, but I get the same results with a shortly-before-1.0-release 
version of trunk and XmlSpy
* * A simple xml file
* An equally simple transformation file, one page layout, a few blocks, two 
tables with blocks, two borders.
Wanted:
* A simple PDF, one page, no images.

Problem:
* When applying the transformation, I get a fo file which I can transform into 
a pdf. Everything works fine.
* When running the xml and the xslt through fop (following ExampleXML2FO), I 
get the fo file which I can transform into PDF. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_FOP_AREA_TREE, I get the area tree. Looks ok.
* When running the xml and the xslt through fop (following ExampleXML2PDF) with 
MimeConstants.MIME_PDF, I get

 [org.apache.fop.fo.FOTreeBuilder] -> org.apache.fop.fo.ValidationException: 
Document is empty (something might be wrong with your XSLT stylesheet).

* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->Area tree), I get a correct Area tree.
* When combining ExampleXML2FO and ExampleXML2PDF and using two transformations 
(XML->FO, FO->PDF), I get a pdf, which should have one PageSequence with one 
page, according to fop.getResults(). I can't open the PDF in Acrobat (pdf 
corrupt and can't be repaired)

That's it. No error messages, no hints. Area tree works, generating a pdf does 
not. Generating a fo and then a pdf works in XmlSpy. Does anybody see any 
reasoning behind that?

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult & Content GmbH: www.willmycc.de



http://www.w3.org/1999/XSL/Transform";>

		
			

	

			
      
  

		



-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: exact dimensions in apache fop

2010-12-07 Thread Pascal Sancho
Hi,

You should check your printer settings:
did you uncheck the [scale to print] option?

Le 06/12/2010 22:13, joe armstrong a écrit :
> I'm trying to understand page layouts in apache fop. I have set a page width
> of 21 cm and margin-left + margin-right to 5 cm, so I should get 16 cm of
> content. When I process and print on my laser printer and *measure* I get
> only 15 cm for the content.

--
Pascal


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Add-ons for Apache FOP

2010-12-07 Thread Jeremias Maerki
If you don't know the sizes of the images at design time, you'd probably
have to write an XSLT plug-in that would pre-load the image using the
image loading framework from Apache XML Graphics Commons. This should be
quite fast at runtime but possibly not so quick to implement.


On 03.12.2010 00:21:53 Lucian Opris wrote:
> Thank you again for the answer. Considering I'll use fo:external-graphic, is
> there easy way to determine page size in style? For large attachments (100
> pages) having many fo:page-sequence will not slow down the rendering
> process?
> Thanks,
> 
> Lucian Opris
> 
> -Original Message-
> From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] 
> Sent: Thursday, December 02, 2010 2:07 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: Re: Add-ons for Apache FOP
> 
> fox:external-document doesn't allow any additional content besides the
> full-page images. You'll have to determine the page sizes yourself and
> use normal fo:page-sequence elements to set up the image for full-page
> display.
> 
> The PDF size increases that much because there is currently no easy way
> to cache the already transferred PDF objects so they are not transferred
> again for each page. I've experimented with that some time ago but had
> to disable that feature because of massive problems. I may revisit this
> at some point (no current plans). If you have to add larger PDFs to a
> document I suggest you do that as a post-processing step using Apache
> PDFBox.
> 
> On 01.12.2010 21:45:05 Lucian Opris wrote:
> > Also, I've noticed that without using fox:external-document the pdf size
> is
> > about 17K  then using fox:external-document to call a 608K PDF I've got a
> > resulting 2.104K PDF. Do you know what could cause such a dramatic file
> > increase?
> > 
> > Lucian Opris
> > 
> > -Original Message-
> > From: Lucian Opris [mailto:lucian.op...@bluematrix.com] 
> > Sent: Wednesday, December 01, 2010 3:12 PM
> > To: fop-users@xmlgraphics.apache.org
> > Subject: RE: Add-ons for Apache FOP
> > 
> > Thank you Jeremias,
> > I've added the  > src="C:/FOP1/fop-1.0/attachments/my.pdf"/> to work in conjunction with new
> > namespace
> > xmlns:fox="http://xmlgraphics.apache.org/fop/extensions"; and it worked
> fine.
> > Now the question is can we stamp header and footers on external pdf called
> > with fox since fox:external-document is peer with fo:page-sequence?
> > 
> > 
> > Lucian Opris
> > 
> > -Original Message-
> > From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] 
> > Sent: Wednesday, December 01, 2010 2:13 AM
> > To: fop-users@xmlgraphics.apache.org
> > Subject: Re: Add-ons for Apache FOP
> > 
> > Hi Lucian
> > 
> > On 30.11.2010 20:35:48 Lucian Opris wrote:
> > > Hi Jeremias,
> > > I'm using your FOP add-ons to call PDF attachments as images using
> > > .
> > > Is there a way to preserve pdf page size for landscape pages or should I
> > use
> > > ?
> > 
> > Support for landscape pages is available in the latest release (2.0.0)
> > of the plug-in.
> > 
> > > Are PDFs with mixed pagesizes work with  > the
> > > footer stamping start at the same point from left?
> > 
> > Not sure what you mean by that. With fox:external-document the target
> > page will have the exact size of the respective input page. This should
> > work for each page independently.
> 
> 
> 
> Jeremias Maerki
> 
> 
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org




Jeremias Maerki


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: [Barcode4j-users] barcode4j question

2010-12-07 Thread Jeremias Maerki
John,
I still think this is a class loading problem. You didn't say what kind
of server you're using. If, for some reasons, that server unpacks all
application JARs into a commons local directory and loads the classes
from there, it could possibily be so that Barcode4J's
META-INF/services/org.apache.fop.fo.ElementMapping file overwrote the
FOP one. That way, FOP doesn't find its own fo:* classes and that
UnknownXMLObj might be explained. You could try to temporarily remove
the Barcode4J FOP extension from the classpath and check if that changes
anything.

At any rate, you have to make sure the individual JARs are not merged
without special handling for the META-INF/services files and that all of
the JARs are associated with the same classloader(-hierarchy).

On 06.12.2010 20:26:05 John Brady wrote:
> Hi,
> 
> I have taken a clean version of fop.jar (FOP 0.95) from here:
> http://archive.apache.org/dist/xmlgraphics/fop/binaries/
> 
> I am still getting the same issue (error attached). It is throwing the error 
> at the following call (method attached):
> 
> transformer.transform(src, res);
> 
> I am able to get it to work in eclipse under test conditions but when I 
> deploy it to my UAT server it fail at the line above. I am thinking that I am 
> missing a jar on UAT that eclipse may have included. Do you know what else 
> could cause this issue? 
> 
> Best Regards,
> John Brady
> 
> IT Specialist 
> Aerlingus.com  
> 
>  
> 
> -Original Message-
> From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch] 
> Sent: 29 November 2010 21:09
> To: John Brady
> Subject: Re: [Barcode4j-users] barcode4j question
> 
> Hi John
> 
> This smells like a class loading problem. I'd say that FOP
> hasn't found the file META-INF/services/org.apache.fop.fo.ElementMapping
> in the classpath. That usually doesn't happen. I can only imagine that
> you've unpacked fop.jar and repacked it in a different way so the
> plug-ins are not found. After all, the main ElementMapping services file
> is normally (!) in the same JAR as the ElementMappingRegistry.
> 
> On 29.11.2010 20:27:23 John Brady wrote:
> > Hi Jeremias,
> > 
> > I am at the stage now where I am integrating the code into the booking 
> > engine. I am looking to pipe the document through into the 
> > HttpServletResponse directly by returning a byte array. My previous tests 
> > were successful when writing the contents directly to a pdf file including 
> > the barcode. Now when I try to use ByteArrayOutputStream I get the error 
> > attached (line 222 = transformer.transform(src, res);). I am using Fop 
> > 0.95. The function I am using to create the byte array is also attached in 
> > the code.txt document. Is there something obvious I am missing?
> > 
> > Kind Regards,
> > John
> 
> 
> 
> Best regards,
> Jeremias Märki
> _
> Jeremias Märki, Software-Development and Consulting
> Contact Information: http://www.jeremias-maerki.ch/contact.html
> Blog: http://www.jeremias-maerki.ch/blog/
> 
> 
> ..For low fares and great deals on hotels, car hire and travel insurance 
> visit http://www.aerlingus.com
> ***
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed.  Any review, dissemination or other use of, or taking
> of any action in reliance upon, this information by persons or entities
> other than the intended recipient is prohibited.If you have received
> this email in error please notify the sender immediately and delete
> the material. 
> ***
> Aer Lingus Limited
> Registered in Ireland
> Company Number 9215
> Registered Office at Dublin Airport, Dublin,Ireland.
> ***




Jeremias Maerki


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: exact dimensions in apache fop

2010-12-07 Thread Jeremias Maerki
Are you printing PDF from Acrobat Reader? If yes, please see:
http://xmlgraphics.apache.org/fop/faq.html#pdf-print-contortion

On 06.12.2010 22:13:13 joe armstrong wrote:
> Hello,
> 
> I'm trying to understand page layouts in apache fop. I have set a page width
> of 21 cm and margin-left + margin-right to 5 cm, so I should get 16 cm of
> content. When I process and print on my laser printer and *measure* I get
> only 15 cm for the content.
> 
> I set the extent of region-start to 3.0cm but when I measure I get 2.8cm
> 
> I have printed this on a macbook, using the print menu in the
> preview program I have set scale to 100% and disable "scale to fit"
> 
> Is this a common problem? Can I expect precise dimensions in the
> printed output?
> 
> I'm using apache fop version 1.0
> 
> My test program is appended.
> 
> If you process and print this on your local printer and them take a ruler
> and measure do you get a region-start of exactly 3.0cm?
> 
> Or is my program wrong?
> 
> Cheers
> 
> /Joe Armstrong
> 
> http://www.w3.org/1999/XSL/Format";>
> 
>   master-name="odd"
>  page-height="29.7cm"
>  page-width="21cm"
>  margin-top="2.5cm"
>  margin-bottom="2.5cm"
>  margin-left="3.0cm"
>  margin-right="2.0cm">
> 
>background-color="#ee"   
>  region-name="xsl-region-body"
>  margin-top="0.6in"
>  margin-bottom="5.0cm"
>  margin-left="3.5cm"
>  margin-right="2.5cm"/>
> 
>  background-color="yellow"  
>precedence="true"
>region-name="xsl-region-before"
>extent="1.0cm"/>
> 
>  background-color="orange"
>region-name="xsl-region-after"
>extent="1.5cm"
>precedence="true"/>
> 
>  background-color="pink"
>region-name="xsl-region-start"
>extent="3.0cm"/>
> 
>  background-color="#efefef"
>region-name="xsl-region-end"
>extent="2.0cm"/>
> 
> 
> 
> 
> 
>   
>  
> flow-name="xsl-region-start">
> 
>Page: 
>This is region Start, extent=3.0cm
>
>  
>  
>  flow-name="xsl-region-end">
>region end. extent = "2.0cm"
> 
>
>  
> 
>  
>Region before extent=1.0cm
> 
>
>  
> 
>  flow-name="xsl-region-after"
>display-align="after">
> 
> text-align="center">Page 
>region-after extent=1.5cm
>
>
>  
> 
>  
>  white-space-collapse="false" 
>  white-space-treatment="preserve" 
>  >
>These are the simple-page-master values
>  master-name="odd"
>  page-height="29.7cm"
>  page-width="21cm"
>  margin-top="2.5cm"
>  margin-bottom="2.5cm"
>  margin-left="3.0cm"
>  margin-right="2.0cm">
>
>
>This is xsl-region-body. margin-left="3.5cm" this is 0.5 cm larger than
>the extent of region-start.
>margin-right= 2.5 cm, ie 0.5 cm larger than the extent of the 
>thing to the right. Margin-bottom is 5.0cm
>   
> 
>   provisional-label-separation="0.1in" 
>space-before.optimum="6pt"
>start-indent="0.5in">
>   
>  start-indent="1.0cm"
> end-indent="6.0cm">
>   
> The Extensible Markup Language (XML) is a subset of SGML.
> start-indent = 1.0 cm end - indent = 6.0 cm
>   
> 
> 
>   
> start-indent = 5 cm end-ident=1.0 cm
> The Extensible Markup Language (XML) is a subset of SGML that
> is completely described in this document. Its goal is to enable
> generic SGML to be served, received, and processed on the Web
> in the way that is now possible with HTML.
> The Extensible Markup Language (XML) is a subset of SGML that
> is completely described in this document.
>   
> 
>   
>   
>  
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org




Jeremias Maerki


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Extracting text of created pdfs with fonts

2010-12-07 Thread Jeremias Maerki
You didn't say what FOP version you're using. Have you tried the latest
FOP release?

On 06.12.2010 11:05:27 alexander.reel...@lusini.com wrote:
> Hi all,
> 
> I have a problem extracting the text content of a pdf created with fop using 
> custom fonts.
> 
> The fonts have been added to the fop.xconf and are rendered correctly.
> However, when I try to open the file (regardless whether this is done with 
> itext, pdfbox or pdfclown libraries), I cannot extract any text - only binary 
> gibberish is returned.
> 
> As soon as I disable the custom font rendering, every lib can extract the 
> content.
> 
> Any pointers on what I am doing wrong? Wrong font configuration? Is it 
> possible at all to extract content when custom fonts are used?
> 
> 
> Regards, Alexander




Jeremias Maerki


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org