[
https://issues.apache.org/jira/browse/COCOON3-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587150#comment-13587150
]
Hudson commented on COCOON3-99:
-------------------------------
Integrated in Cocoon 3.0 #247 (See
[https://builds.apache.org/job/Cocoon%203.0/247/])
[COCOON3-99] Applying provided patch with some minor rework (Revision
1450159)
Result = SUCCESS
ilgrosso : http://svn.apache.org/viewvc/?view=rev&rev=1450159
Files :
*
/cocoon/cocoon3/trunk/cocoon-optional/src/main/java/org/apache/cocoon/optional/pipeline/components/sax/fop/FopSerializer.java
> Provide FopSerializer with an embedded user configuration present in the
> cocoon block
> -------------------------------------------------------------------------------------
>
> Key: COCOON3-99
> URL: https://issues.apache.org/jira/browse/COCOON3-99
> Project: Cocoon 3
> Issue Type: Improvement
> Components: cocoon-optional
> Affects Versions: 3.0.0-beta-1
> Reporter: Jos Snellings
> Assignee: Francesco Chicchiriccò
> Priority: Minor
> Fix For: 3.0.0-beta-1
>
> Attachments: patch-fopserializer.txt
>
>
> The current FopSerializer creates an instance of FopFactory. Only the
> defaults are used. This is a problem if you want to generate PDFs
> from Unicode data. The Cyrillic and Greek characters have no glyphs in these
> fonts, causing those strings to be displayed as "#" sequences.
> This patch adds an override for the method "setConfiguration" to add a user
> configuration location via a sitemap parameter.
> In sitemap.xmap of the block, add the parameter "userConfigurationPath"
> indicating the location of the user configuration file.
> Example:
> <map:match pattern="editor/publish/thesaurus.pdf">
> <map:generate type="publish"/>
> <map:transform src="presentation/xslt/thesaurusfo.xslt"/>
> <map:serialize type="flo2pdf">
> <map:parameter name="userConfigurationPath"
> value="fopconf/fop.xconf"/>
> </map:serialize>
> </map:match>
--
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
