[
https://issues.apache.org/jira/browse/FOP-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644433#comment-13644433
]
Thomas Mitterfellner commented on FOP-2242:
-------------------------------------------
Ok, I don't know why, but now generating the example pdf and also a larger one
is fast.
What I did:
I downloaded an svn snapshot, compiled it with ant.
Then I used that version of fop to generate the pdf, which was fast.
It turned out that it didn't find Open Sans (nor any other fonts), so I
generated a config file that told fop to scan my ~/.fonts directory (and used
it with the -c option).
Then I generated that pdf again, it was fast (a 10 pages pdf with about 50 svg
diagrams ~5-6 s total), plus, Open Sans was embedded.
Now, when I use fop from the openSUSE package again, pdf creation is also fast
and Open Sans is embedded. Very strange.
I guess there must have been something wrong with my default fonts setup.
But anyway - the original issue is resolved for me. Thanks for your hints!
> PDF generation is very slow when document contains svg:text
> -----------------------------------------------------------
>
> Key: FOP-2242
> URL: https://issues.apache.org/jira/browse/FOP-2242
> Project: Fop
> Issue Type: Bug
> Components: fonts, pdf, svg
> Affects Versions: 1.1
> Environment: linux x86_64 (OpenSUSE 12.2)
> Reporter: Thomas Mitterfellner
> Labels: fonts, pdf, svg, text
> Attachments: fo_style.xsl, test.xml
>
>
> PDF generation is very slow when the document contains svg:text elements.
> When I remove the svg:text elements, the pdf generation is very fast.
> I attached the xml and xsl files to test the behavior. When lines 314-343 are
> commented out (svg:text elements), pdf generation is quick.
> Note: a single svg:text element is sufficient to slow down the generation
> process.
> If there is any further information I should provide in order to tackle this
> problem, I'll try to provide it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
