[jira] [Commented] (FOP-2190) decrease PDF file size when CS are enabled

2013-01-21 Thread Glenn Adams (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559323#comment-13559323 ] Glenn Adams commented on FOP-2190: -- i've implemented a portion of this patch already in FOP

[jira] [Resolved] (FOP-2196) remove release candidate binaries and source artifacts from svnpubsub repository

2013-01-21 Thread Glenn Adams (JIRA)
[ https://issues.apache.org/jira/browse/FOP-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glenn Adams resolved FOP-2196. -- Resolution: Fixed Fix Version/s: 1.1 https://dist.apache.org/repos/dist/release/xmlgraphics/?p=127

[jira] [Created] (FOP-2196) remove release candidate binaries and source artifacts from svnpubsub repository

2013-01-21 Thread Glenn Adams (JIRA)
Glenn Adams created FOP-2196: Summary: remove release candidate binaries and source artifacts from svnpubsub repository Key: FOP-2196 URL: https://issues.apache.org/jira/browse/FOP-2196 Project: Fop

Re: svn commit: r1435344 - in /xmlgraphics/fop/trunk: src/java/org/apache/fop/fonts/LazyFont.java status.xml

2013-01-21 Thread Glenn Adams
One more point, which is "probably inlined" is not a very good guarantee, since that is strictly an implementation option. Better to error on the side of assuming it won't inline, and at least optimize the hot spots that would be affect if inlining doesn't occur. On Mon, Jan 21, 2013 at 12:12 PM,

Re: svn commit: r1435344 - in /xmlgraphics/fop/trunk: src/java/org/apache/fop/fonts/LazyFont.java status.xml

2013-01-21 Thread Glenn Adams
I agree that when JIT inlines this it will not have much affect. However, when profiling, this was identified as a hot spot. On Mon, Jan 21, 2013 at 11:52 AM, Vincent Hennebert wrote: > Hi Glenn, > > does that significantly improve performance? I would be really surprised > if it would, given tha

Re: svn commit: r1435344 - in /xmlgraphics/fop/trunk: src/java/org/apache/fop/fonts/LazyFont.java status.xml

2013-01-21 Thread Vincent Hennebert
Hi Glenn, does that significantly improve performance? I would be really surprised if it would, given that the method call is probably inlined by the JIT compiler anyway. Do you have figures to share? Thanks, Vincent On 18/01/13 22:13, gadams wrote: > Author: gadams > Date: Fri Jan 18 21:13:42

Re: remove fop1.1rc1 binaries?

2013-01-21 Thread Glenn Adams
thanks, i will remove from the release dir; the archives automatically copy everything that went into the release dirs, and can't be removed, so that is why 1.1 already appears there On Mon, Jan 21, 2013 at 3:13 AM, Vincent Hennebert wrote: > Hi Glenn, > > I think they can definitely be removed f

Re: remove fop1.1rc1 binaries?

2013-01-21 Thread Vincent Hennebert
Hi Glenn, I think they can definitely be removed from the mirrors (the source as well for that matter). But I think that, rather than removing them altogether, they should be moved to the archives: http://archive.apache.org/dist/xmlgraphics/fop/binaries/ where actually they already appear. Not to

Re: remove fop1.1rc1 binaries?

2013-01-21 Thread Chris Bowditch
Hi Glenn, I don't have a strong preference either way, but I think it probably makes sense to encourage people to use the actual released version by removing it. Thanks, Chris On 20/01/2013 21:41, Glenn Adams wrote: What is the practice regarding retention of RC binaries? Should we remove