findbugs warnings
I see someone hasn't been running findbugs: Dodgy Warnings CodeWarningBC Unchecked/unconfirmed cast from org.apache.fop.accessibility.StructureTreeElement to org.apache.fop.pdf.PDFStructElem in org.apache.fop.render.pdf.PDFStructureTreeBuilder.startNode(String, Attributes, StructureTreeElement) DLSDead store to logFactory in new org.apache.fop.cli.CommandLineOptions() DLSDead store to logFactory in org.apache.fop.fonts.apps.PFMReader.main(String[]) DLSDead store to logFactory in org.apache.fop.fonts.apps.TTFReader.main(String[]) Could the responsible party please fix? Thanks.
[jira] [Created] (FOP-2298) Enable support for PDF page transitions.
Glenn Adams created FOP-2298: Summary: Enable support for PDF page transitions. Key: FOP-2298 URL: https://issues.apache.org/jira/browse/FOP-2298 Project: Fop Issue Type: New Feature Affects Versions: trunk Reporter: Glenn Adams Assignee: Glenn Adams See http://marc.info/?l=fop-user&m=130017885816296&w=2. -- 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
[jira] [Updated] (FOP-2071) Documents need update: reference to area tree as 'intermediate format'
[ https://issues.apache.org/jira/browse/FOP-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2071: - Priority: Blocker Summary: Documents need update: reference to area tree as 'intermediate format' (was: docs need update: reference to area tree as 'intermediate format') > Documents need update: reference to area tree as 'intermediate format' > -- > > Key: FOP-2071 > URL: https://issues.apache.org/jira/browse/FOP-2071 > Project: Fop > Issue Type: Bug > Components: documentation >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Glenn Adams >Priority: Blocker > > in [1], the area tree (AT) format is referred to as 'intermediate format'; > this material needs to be updated to refer to the new IF format if the > suggested workaround works with IF; if the suggested workaround does not work > with IF, then the phrase 'intermediate format' should be changed to 'area > tree' > [1] http://xmlgraphics.apache.org/fop/trunk/output.html#general-fonts -- 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
[jira] [Updated] (FOP-2209) Move new CMS documentation back into FOP repository or ...
[ https://issues.apache.org/jira/browse/FOP-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2209: - Summary: Move new CMS documentation back into FOP repository or ... (was: move new CMS documentation back into FOP repository or ...) > Move new CMS documentation back into FOP repository or ... > -- > > Key: FOP-2209 > URL: https://issues.apache.org/jira/browse/FOP-2209 > Project: Fop > Issue Type: Task > Components: documentation >Affects Versions: trunk >Reporter: Glenn Adams >Assignee: Clay Leeds >Priority: Minor > > The new markdown documentation files need to be moved back into the FOP > repository. The CMS repository should be considered as a deployment rather > than source repository, in the same fashion that the former publish.xml > process copied docs out of the FOP repository into the former site > documentation repository. -- 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
[jira] [Updated] (FOP-2054) Non-embedded fonts are incorrectly assumed to be single byte, even when they are multi byte
[
https://issues.apache.org/jira/browse/FOP-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2054:
-
Priority: Blocker
Summary: Non-embedded fonts are incorrectly assumed to be single byte,
even when they are multi byte (was: non-embedded fonts are incorrectly assumed
to be single byte, even when they are multi byte)
> Non-embedded fonts are incorrectly assumed to be single byte, even when they
> are multi byte
> ---
>
> Key: FOP-2054
> URL: https://issues.apache.org/jira/browse/FOP-2054
> Project: Fop
> Issue Type: Bug
> Components: fonts
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: Glenn Adams
>Priority: Blocker
> Attachments: console.log, fop.xconf, test.fo.xml, test.pdf
>
>
> the following code in o.a.f.fonts.truetype.TTFFontLoader incorrectly assumes
> that a non-embedded font is a single byte font:
> boolean isCid = this.embedded;
> if (this.encodingMode == EncodingMode.SINGLE_BYTE) {
> isCid = false;
> }
> if (isCid) {
> multiFont = new MultiByteFont();
> returnFont = multiFont;
> multiFont.setTTCName(ttcFontName);
> } else {
> singleFont = new SingleByteFont();
> returnFont = singleFont;
> }
> this prevents the use of non-embedded (referenced only) multibyte fonts
> the attached input FO file and corresponding FOP configuration make use of
> the simsun.ttf font (a multibyte font) which can be downloaded from [1]
> [1] http://jumal.is.free.fr/SimSun.ttf
--
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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760590#comment-13760590 ] Glenn Adams commented on FOP-2293: -- I've added a question at [1] as follows: "Instead of creating new extension element types, why not use fo:multi-switch and fo:multi-case (instead of the proposed fox:best-fit and fox:best-fit-alternative), along with a new extension property, fox:best-fit on fo:multi-switch, which triggers an implicit process for setting the currently-visible-multi-case trait on the fo:multi-switch to select none or one of the alternative fo:multi-case sub-trees to contribute generated areas? The structure and function of these existing FO element types exactly match the proposed new element types. [GA]" [1] https://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement > Whitespace management extension > --- > > Key: FOP-2293 > URL: https://issues.apache.org/jira/browse/FOP-2293 > Project: Fop > Issue Type: New Feature > Components: general >Affects Versions: trunk >Reporter: Seifeddine Dridi >Priority: Minor > Labels: XSL-FO > Fix For: trunk > > Attachments: bestfit.fo, doc.pdf, multiple-feasible-nodes.fo, > patch.patch, patch-rev1.1.patch, patch-rev1.patch > > > I have been working on an extension for whitespace management, similar to > what's described here: > http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement > The logic of the extension is very simple: the user defines a set of > alternatives that he wishes to insert at the end of a page, then if there is > enough space left, FOP will pick the alternative that best matches the user's > selection criteria (first fit, smallest fit, biggest fit). > This is my first work on FOP and it took me almost 2 months to reach this > stage in development. But it's not the end of course, so I'm relying on your > feedback to improve it. > Thank you -- 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
Degraded SVG Output on JDK 1.7 update.
Has anyone run into problems with output quality of SVG external graphics on the recent updates to Java 7? One of my clients has run into a problem described in https://issues.apache.org/jira/browse/FOP-2297. I'm not well versed on this part of the code base, so any ideas would be appreciated. G.
[jira] [Created] (FOP-2297) Degraded output from SVG external graphic on upgrade from JDK 1.7.0_21 to 1.7.0_25
Glenn Adams created FOP-2297: Summary: Degraded output from SVG external graphic on upgrade from JDK 1.7.0_21 to 1.7.0_25 Key: FOP-2297 URL: https://issues.apache.org/jira/browse/FOP-2297 Project: Fop Issue Type: Bug Components: svg Affects Versions: 1.1, trunk Environment: Verified on both MacOSX and Win32. Reporter: Glenn Adams Attachments: Google.svg, test.bad.pdf, test.fo.xml, test.good.pdf When updating from JDK 1.7.0_21 to 1.7.0_25, PDF output of SVG external graphics appears to switch to low resolution, poor rendering quality. -- 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
[jira] [Updated] (FOP-2297) Degraded output from SVG external graphic on upgrade from JDK 1.7.0_21 to 1.7.0_25
[ https://issues.apache.org/jira/browse/FOP-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams updated FOP-2297: - Attachment: test.good.pdf test.fo.xml test.bad.pdf Google.svg > Degraded output from SVG external graphic on upgrade from JDK 1.7.0_21 to > 1.7.0_25 > -- > > Key: FOP-2297 > URL: https://issues.apache.org/jira/browse/FOP-2297 > Project: Fop > Issue Type: Bug > Components: svg >Affects Versions: 1.1, trunk > Environment: Verified on both MacOSX and Win32. >Reporter: Glenn Adams > Attachments: Google.svg, test.bad.pdf, test.fo.xml, test.good.pdf > > > When updating from JDK 1.7.0_21 to 1.7.0_25, PDF output of SVG external > graphics appears to switch to low resolution, poor rendering quality. -- 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
