Picon

[jira] [Commented] (FOP-2462) Fop PDF Image Plugin broken since rev 1590626


    [
https://issues.apache.org/jira/browse/FOP-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513979#comment-14513979
] 

Matthias Reischenbacher commented on FOP-2462:
----------------------------------------------

Thanks Simon. What I could see so far is that the page content stream (32 0 obj in your case) is different.
Could you please also attach a file without compression (null filter in fop config). Thanks.

> Fop PDF Image Plugin broken since rev 1590626
> ---------------------------------------------
>
>                 Key: FOP-2462
>                 URL: https://issues.apache.org/jira/browse/FOP-2462
>             Project: Fop
>          Issue Type: Bug
>          Components: image/unqualified
>    Affects Versions: trunk
>            Reporter: Matthias Reischenbacher
>         Attachments: fop-2462-acrobat-error-message.png, fop-2462-external-pdf.pdf,
fop-2462-test-case-null-filter.pdf, fop-2462-test-case.pdf, fop-2462-test-case.xml, out.pdf
>
>
> Rendering the attached sample fo and pdf file with FOP and the PDF Image Plugin creates a corrupted PDF file
since revision 1590626. The generated PDF file can be opened with Adobe Acrobat but when opening the page
with the external PDF file an error message is displayed and no content is visible.

--
(Continue reading)

buildbot | 27 Apr 10:00 2015
Picon

buildbot exception in ASF Buildbot on fop-trunk

The Buildbot has detected a build exception on builder fop-trunk while building ASF Buildbot. Full
details are available at:
    http://ci.apache.org/builders/fop-trunk/builds/290

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The Nightly scheduler named 'fopNightly' triggered this build
Build Source Stamp: [branch xmlgraphics/fop/trunk] HEAD
Blamelist: 

BUILD FAILED: exception svn

Sincerely,
 -The Buildbot

simon steiner (JIRA | 27 Apr 09:47 2015
Picon

[jira] [Updated] (FOP-2462) Fop PDF Image Plugin broken since rev 1590626


     [
https://issues.apache.org/jira/browse/FOP-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

simon steiner updated FOP-2462:
-------------------------------
    Attachment: out.pdf

My output

> Fop PDF Image Plugin broken since rev 1590626
> ---------------------------------------------
>
>                 Key: FOP-2462
>                 URL: https://issues.apache.org/jira/browse/FOP-2462
>             Project: Fop
>          Issue Type: Bug
>          Components: image/unqualified
>    Affects Versions: trunk
>            Reporter: Matthias Reischenbacher
>         Attachments: fop-2462-acrobat-error-message.png, fop-2462-external-pdf.pdf,
fop-2462-test-case-null-filter.pdf, fop-2462-test-case.pdf, fop-2462-test-case.xml, out.pdf
>
>
> Rendering the attached sample fo and pdf file with FOP and the PDF Image Plugin creates a corrupted PDF file
since revision 1590626. The generated PDF file can be opened with Adobe Acrobat but when opening the page
with the external PDF file an error message is displayed and no content is visible.

--
This message was sent by Atlassian JIRA
(Continue reading)

Picon

[jira] [Commented] (FOP-2462) Fop PDF Image Plugin broken since rev 1590626


    [
https://issues.apache.org/jira/browse/FOP-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513053#comment-14513053
] 

Matthias Reischenbacher commented on FOP-2462:
----------------------------------------------

Simon, could you please attach your generated PDF, that doesn't exhibit the error, so that we can compare
what's different between mine and your PDF?

> Fop PDF Image Plugin broken since rev 1590626
> ---------------------------------------------
>
>                 Key: FOP-2462
>                 URL: https://issues.apache.org/jira/browse/FOP-2462
>             Project: Fop
>          Issue Type: Bug
>          Components: image/unqualified
>    Affects Versions: trunk
>            Reporter: Matthias Reischenbacher
>         Attachments: fop-2462-acrobat-error-message.png, fop-2462-external-pdf.pdf,
fop-2462-test-case-null-filter.pdf, fop-2462-test-case.pdf, fop-2462-test-case.xml
>
>
> Rendering the attached sample fo and pdf file with FOP and the PDF Image Plugin creates a corrupted PDF file
since revision 1590626. The generated PDF file can be opened with Adobe Acrobat but when opening the page
with the external PDF file an error message is displayed and no content is visible.

--
(Continue reading)

Picon

[jira] [Updated] (FOP-2465) [PATCH] Links to 'last' page aren't working


     [
https://issues.apache.org/jira/browse/FOP-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Reischenbacher updated FOP-2465:
-----------------------------------------
    Attachment: fop-2465-link-to-last-page.patch

Patch

> [PATCH] Links to 'last' page aren't working
> -------------------------------------------
>
>                 Key: FOP-2465
>                 URL: https://issues.apache.org/jira/browse/FOP-2465
>             Project: Fop
>          Issue Type: Bug
>          Components: layout/page
>            Reporter: Matthias Reischenbacher
>         Attachments: fop-2465-link-to-last-page.patch, fop-2465-link-to-last-page.xml
>
>
> If there is a separate page master for the 'last' page and the layout is redone (see
PageBreaker.redoLayout) links to content inside the last page don't work.
> My test case fo file contains a bookmark to a block on the last page. The following warning is displayed when
generating PDF output:
> WARNING: 1 link target could not be fully resolved and now point to the top of the page or is dysfunctional.
> My Patch tries to fix the ID handling and replaces the old PageViewport instances inside the IDTracker
with the one. Please let me know if there is a better way to fix this issue.

(Continue reading)

Picon

[jira] [Updated] (FOP-2465) [PATCH] Links to 'last' page aren't working


     [
https://issues.apache.org/jira/browse/FOP-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Reischenbacher updated FOP-2465:
-----------------------------------------
    Attachment: fop-2465-link-to-last-page.xml

Test case

> [PATCH] Links to 'last' page aren't working
> -------------------------------------------
>
>                 Key: FOP-2465
>                 URL: https://issues.apache.org/jira/browse/FOP-2465
>             Project: Fop
>          Issue Type: Bug
>          Components: layout/page
>            Reporter: Matthias Reischenbacher
>         Attachments: fop-2465-link-to-last-page.xml
>
>
> If there is a separate page master for the 'last' page and the layout is redone (see
PageBreaker.redoLayout) links to content inside the last page don't work.
> My test case fo file contains a bookmark to a block on the last page. The following warning is displayed when
generating PDF output:
> WARNING: 1 link target could not be fully resolved and now point to the top of the page or is dysfunctional.
> My Patch tries to fix the ID handling and replaces the old PageViewport instances inside the IDTracker
with the one. Please let me know if there is a better way to fix this issue.

(Continue reading)

Picon

[jira] [Created] (FOP-2465) [PATCH] Links to 'last' page aren't working

Matthias Reischenbacher created FOP-2465:
--------------------------------------------

             Summary: [PATCH] Links to 'last' page aren't working
                 Key: FOP-2465
                 URL: https://issues.apache.org/jira/browse/FOP-2465
             Project: Fop
          Issue Type: Bug
          Components: layout/page
            Reporter: Matthias Reischenbacher

If there is a separate page master for the 'last' page and the layout is redone (see
PageBreaker.redoLayout) links to content inside the last page don't work.

My test case fo file contains a bookmark to a block on the last page. The following warning is displayed when
generating PDF output:
WARNING: 1 link target could not be fully resolved and now point to the top of the page or is dysfunctional.

My Patch tries to fix the ID handling and replaces the old PageViewport instances inside the IDTracker with
the one. Please let me know if there is a better way to fix this issue.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Glenn Adams | 22 Apr 18:35 2015

Maven



On Wed, Apr 22, 2015 at 10:31 AM, Luis Bernardo <lmpmbernardo <at> gmail.com> wrote:

I think that maven will be embraced as soon as there is a volunteer to do the transition.

A few years ago I went through the process of creating a full maven configuration for FOP; however, the group was not ready to make the transition at that time.

I have recently converted another multiple-module internal project to maven from ant, and would be able to repeat the process on fop. However, I don't want to do it unless there is support to switch over.
 


On 4/22/15 6:13 PM, Glenn Adams wrote:
on another point, when can we transition to maven? our ant configurations are difficult to maintain and understand; we should modernize


John Cumming (JIRA | 22 Apr 08:43 2015
Picon

[jira] [Commented] (FOP-2460) Subsetting OTF font leads to PDF errors when viewing / incorrect characters


    [
https://issues.apache.org/jira/browse/FOP-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506533#comment-14506533
] 

John Cumming commented on FOP-2460:
-----------------------------------

We have also had problems with several other OTF fonts, including Adobe Caslon Pro Regular. We get a series
of filled circles and no valid rendered glyphs in the output. Other applications, such as MS Word,
FrameMaker and InDesign all handle the font OK.

This may well be a different problem but could be related ?

I have always assumed that the bug is somewhere in the OTF handling, although haven't had a look myself yet.

> Subsetting OTF font leads to PDF errors when viewing / incorrect characters
> ---------------------------------------------------------------------------
>
>                 Key: FOP-2460
>                 URL: https://issues.apache.org/jira/browse/FOP-2460
>             Project: Fop
>          Issue Type: Bug
>          Components: font/opentype
>    Affects Versions: trunk
>            Reporter: Robert Meyer
>
> When attempting to generate a document whilst subsetting the VilleroyBoch-Regular.otf font,
different viewers will either show errors, no text or lead to incorrect or corrupt characters being drawn.
> I currentlty believe this is down to either a subroutine not being copied from the original font leading to
a invalid reference, or the subroutine does not contain valid data. When looking at this font in
FontForge, 3 characters in a "hello world" example I used were missing which backs up this hypothesis.
> [EDIT] I've removed the font as I did not check if there were copyright issues by making it public domain. I
will work when I am able to do so but keep the font privately unless I hear otherwise from the user who
originally posted the problem

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Simon Steiner | 21 Apr 17:21 2015
Picon

FOP Release

Hi,

 

Since Batik and XGC have been released, are we ready to release FOP?

 

It has been said we can’t release PDF plugin using a snapshot release of PDFBox 2.0. PDFBox 1.8 is missing font parsing libraries we need for font merging.

We could make release a PDF plugin beta release using snapshot of PDFBox or ask user to use PDF plugin snapshot version with FOP 2.0.

 

Thanks

buildbot | 18 Apr 10:42 2015
Picon

buildbot success in ASF Buildbot on fop-trunk

The Buildbot has detected a restored build on builder fop-trunk while building ASF Buildbot. Full details
are available at:
    http://ci.apache.org/builders/fop-trunk/builds/281

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The Nightly scheduler named 'fopNightly' triggered this build
Build Source Stamp: [branch xmlgraphics/fop/trunk] HEAD
Blamelist: 

Build succeeded!

Sincerely,
 -The Buildbot


Gmane