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
Re: FOP Release
-1 On Tue, Apr 21, 2015 at 9:21 AM, Simon Steiner wrote: > 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 >
Re: FOP Release
One of the changes for PDFBox 2.0.0 (from what I gather from the PDFBox ‘Ideas’ page), is a switch to Java 1.6. We discussed a switch for FOP that required a higher version of Java (I believe it was 1.6, but don’t recall). But I can’t find anywhere on our site that indicates what the minimum Java requirement actually is. I’d like to update the site to include the minimum requirements if someone can let me know what those are… ;-) Clay > On Apr 21, 2015, at 8:21 AM, Simon Steiner wrote: > > 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
RE: FOP Release
Hi, Its listed here https://xmlgraphics.apache.org/fop/trunk/running.html Thanks From: Clay Leeds [mailto:the.webmaes...@gmail.com] Sent: 21 April 2015 21:23 To: Apache FOP Subject: Re: FOP Release One of the changes for PDFBox 2.0.0 (from what I gather from the PDFBox ‘Ideas’ page), is a switch to Java 1.6. We discussed a switch for FOP that required a higher version of Java (I believe it was 1.6, but don’t recall). But I can’t find anywhere on our site that indicates what the minimum Java requirement actually is. I’d like to update the site to include the minimum requirements if someone can let me know what those are… ;-) Clay On Apr 21, 2015, at 8:21 AM, Simon Steiner mailto:simonsteiner1...@gmail.com> > wrote: 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
[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)
