Re: Free 3 of 9

[TvT]

2013/4/18 nels 

> barcode Free 3 of 9 fonts



Hi,

are you using barcode4j?
The examples are here: http://barcode4j.sourceforge.net/examples.html

If you then open the exampe you will find:

  
  

  none
  8mm
  

  



Depending on the type of barcode (for you code 39) you can use different
options:

http://barcode4j.sourceforge.net/2.1/barcode-xml.html

http://barcode4j.sourceforge.net/2.1/barcode-xml.html#string>">
  http://barcode4j.sourceforge.net/2.1/symbol-code39.html>>
15mm

0.19mm

2.5

1mw

http://barcode4j.sourceforge.net/2.1/barcode-xml.html#boolean>">10mw

auto


  bottom

  Helvetica

  8pt

  {string}


  false

  false


  http://barcode4j.sourceforge.net/2.1/symbol-code39.html>>


Regards,
ToM

Adding image to PDF File : Error

[javakthar]

HI

I get the following error when processing my agent to convert xml to PDF.
THe PDF document gets created but the image does not get created. 

pr 18, 2013 3:51:04 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: The file format is not supported. No
ImagePreloader found for
data:image/jpeg;base64,R0lGODlhDwAPAKECzMzM/wAAACwADwAPAAACIISPeQHsrZ5ModrLlN48CXF8m2iQ3YmmKqVlRtW4MLwWACH+H09wdGltaXplZCBieSBVbGVhZCBTbWFydFNhdmVyIQAAOw==
Apr 18, 2013 3:51:04 PM org.apache.fop.layoutmgr.table.TableLayoutManager
getNextKnuthElements
INFO: table-layout="fixed" and width="auto", but auto-layout not supported
=> assuming width="100%"
Apr 18, 2013 3:51:04 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'verdanna,normal,400' not found. Substituting with
'any,normal,400'.


Following is the content of my xsl-fo 






Kindly let me know how this could be resolved.

Regards
Javed Khan



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/Adding-image-to-PDF-File-Error-tp38354.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

FOP memory growing with a lot of

[aemitic]

Hi,

I noticed that FOP (any version) uses a constantly growing amount of memory
when creating PDFs. Even if using very small  blocks and no
forward references.

Please refer to this stackoverflow question which contains a small java
program that replicates the issue.

How can I limit the amount of used memory when transforming to PDF an FO
file with a huge number of  blocks? (> 25)

Thanks for any help



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequences-tp38355.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: FOP memory growing with a lot of blocks (>250000)

[Bonekrusher]

Hi,

I've created some pretty large PDFs (e.g 500+ pages) with a lot of graphics.
IMO, although memory usage increases, eventually Java's Garbage Collection
will free up your memory. 




--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38356.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: Free 3 of 9

[nels]

To be honest I don't know. What I attached before is the only part of the XSL
that looks barcode-related. I have inherited this code to maintain (which is
my excuse).



-
just starting out with FOP - don't hurt me!
--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/Free-3-of-9-tp38348p38357.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: FOP memory growing with a lot of

[Glenn Adams]

Put each page-sequence in a separate XSL-FO file.


On Thu, Apr 18, 2013 at 5:09 AM, aemitic  wrote:

> Hi,
>
> I noticed that FOP (any version) uses a constantly growing amount of memory
> when creating PDFs. Even if using very small  blocks and no
> forward references.
>
> Please refer to this stackoverflow question which contains a small java
> program that replicates the issue.
>
> How can I limit the amount of used memory when transforming to PDF an FO
> file with a huge number of  blocks? (> 25)
>
> Thanks for any help
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequences-tp38355.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: FOP memory growing with a lot of blocks (>250000)

[aemitic]

@Bonekrusher

The test application I created and put in the StackOverflow question (linked
in the post above) clearly shows how the Java's Garbage Collection *can't
and does not* free up the memory.




--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38359.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: FOP memory growing with a lot of

[aemitic]

@Glenn Adams-2
Could you please elaborate more?

Transforming multiple XSL-FO files with FOP would mean to produce multiple
XSL-FO files, wouldn't it?
I need to produce a single PDF.



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38360.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: FOP memory growing with a lot of

[Glenn Adams]

use a separate tool to combine the PDFs


On Thu, Apr 18, 2013 at 8:31 AM, aemitic  wrote:

> @Glenn Adams-2
> Could you please elaborate more?
>
> Transforming multiple XSL-FO files with FOP would mean to produce multiple
> XSL-FO files, wouldn't it?
> I need to produce a single PDF.
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38360.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: FOP memory growing with a lot of

[aemitic]

Thanks for the suggestion.

This /workaround/ (it's not a solution) cannot be applied. Why:
 - internal pdf links would not work
 - pdf bookmarks would not work
 - page numbering would not be correct
 - creating over 15 PDFs and then merging them with an external tool is
unacceptable from a performance point of view




--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38362.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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

Re: FOP memory growing with a lot of

[Glenn Adams]

It depends on what tool you use to combine them. In any case, I don't think
you will find an alternative any time soon. Just a heads up. If you care to
create a patch that solves this problem, then please post it and I'll make
sure it is applied ASAP.


On Thu, Apr 18, 2013 at 9:01 AM, aemitic  wrote:

> Thanks for the suggestion.
>
> This /workaround/ (it's not a solution) cannot be applied. Why:
>  - internal pdf links would not work
>  - pdf bookmarks would not work
>  - page numbering would not be correct
>  - creating over 15 PDFs and then merging them with an external tool is
> unacceptable from a performance point of view
>
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38362.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

[no subject]

[bob swanson]

>> I've created some pretty large PDFs (e.g 500+ pages) with a lot of
graphics.

>> IMO, although memory usage increases, eventually Java's Garbage
Collection

>> will free up your memory.


I am creating a 500-600 page document with over 1,000
high-quality images and just have to set a good-sized
memory limit in order for the script to work.

I'm using:

FOP_OPTS="-Xms400m -Xmx400m"

with the script on a Mac.

Certainly there may be issues with usage of particular
constructs or features, but I have not run into
those with my projects.

Keep up the good work!

Re: FOP memory growing with a lot of

[Maruan Sahyoun]

I'm not a fop expert but

o could you render individual page-sequences to the intermediate format
o stitch the intermediate results together
o do the final rendering based on the intermediate format

Just an idea. Don't know if that would work. I also think that merging 15 
PDF's is not ideal (although I have done that for a banking customer)

Maruan Sahyoun

Am 18.04.2013 um 17:01 schrieb aemitic :

> Thanks for the suggestion.
> 
> This /workaround/ (it's not a solution) cannot be applied. Why:
> - internal pdf links would not work
> - pdf bookmarks would not work
> - page numbering would not be correct
> - creating over 15 PDFs and then merging them with an external tool is
> unacceptable from a performance point of view
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38362.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
> 

Re: FOP memory growing with a lot of

[Luis Bernardo]

You can't. Although it is true that memory is regained when a page is 
output, there is information that needs to be kept till the end, and 
that information keeps growing as you add pages. For instance, byte 
offsets for the objects need to be stored till the end to build the xref 
table, and right now all that is kept in memory.


You can get somewhat better results if you allow your page sequences to 
have more than one page (say, 100 or 1000). Putting all the pages in one 
page-sequence will not work either because you will run out of memory 
during the initial phase of building the FO tree.


On the other hand you can always increase the memory your jvm uses.

On 4/18/13 12:09 PM, aemitic wrote:

Hi,

I noticed that FOP (any version) uses a constantly growing amount of memory
when creating PDFs. Even if using very small  blocks and no
forward references.

Please refer to this stackoverflow question which contains a small java
program that replicates the issue.

How can I limit the amount of used memory when transforming to PDF an FO
file with a huge number of  blocks? (> 25)

Thanks for any help



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequences-tp38355.html
Sent from the FOP - Users mailing list archive at Nabble.com.

-
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: FOP memory growing with a lot of

[aemitic]

Thanks Luis Bernardo, your explanation is really helpful.

So, it is a Fop limitation. 
I shall find the good balance between  blocks number and
the number of pages contained in them.

I guess this info might save a lot of time to someone else in the future.
Especially to business users who are elaborating big big data. Maybe it
should be added to the Fop website under the memory consumption notes? Just
a suggestion.

Thanks again to everyone!



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38368.html
Sent from the FOP - Users mailing list archive at Nabble.com.

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