Re: [VOTE] Merge Temp_FopFontsForSVG into trunk

2013-08-21 Thread Luis Bernardo


+1

Since currently fop depends on a batik milestone release, not on trunk 
(except for the gump build), I see no problem replacing the current 
batik jar in the lib directory by a patched one. Note that the gump 
descriptor will need to be updated if the batik jar in fop is updated 
before the patch is applied to batik trunk.


On 8/21/13 11:08 AM, Vincent Hennebert wrote:

This work allows to directly use FOP-configured fonts for SVG images,
instead of trying to find, via AWT, equivalent fonts installed on the
system, and then mapping them to FOP fonts when generating the output.

Please note that this introduces a dependency on the trunk version of
Batik, with the patch from BATIK-1041 applied. That means that before
releasing the next version of FOP, a new version of Batik will have to
be released first.

This vote will run until Monday, 26 August 11:00 UTC.

+1 from me.

Thanks,
Vincent




Re: [VOTE] Merge Temp_FopFontsForSVG into trunk

2013-08-21 Thread Clay Leeds
This looks like a great and important step. Nice work Vincent!

I have similar concerns as Pancho, so when the BATIK patch is applied I'll vote 
+1.


Regards,

Clay

Clay Leeds  #  949-510-8993  @  the.webmaes...@gmail.com

On Aug 21, 2013, at 4:30 AM, Pascal Sancho  wrote:

> Hi,
> 
> from [1], I understand that the BATIK patch is not yet applied on BATIK 
> trunk, so introducing a such dependency is not a good idea for the moment.
> 
> I will vote +1 when the patch will be applied.
> 
> For now, we depend on Batik team
> 
> [1] 
> https://issues.apache.org/jira/browse/BATIK-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> 
> 
> 2013/8/21 Vincent Hennebert 
> This work allows to directly use FOP-configured fonts for SVG images,
> instead of trying to find, via AWT, equivalent fonts installed on the
> system, and then mapping them to FOP fonts when generating the output.
> 
> Please note that this introduces a dependency on the trunk version of
> Batik, with the patch from BATIK-1041 applied. That means that before
> releasing the next version of FOP, a new version of Batik will have to
> be released first.
> 
> This vote will run until Monday, 26 August 11:00 UTC.
> 
> +1 from me.
> 
> Thanks,
> Vincent
> 
> 
> 
> -- 
> pascal



[jira] [Commented] (FOP-2291) break-after="page" produces blank page but doesn't use blank page master

2013-08-21 Thread Clay Helberg (JIRA)

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

Clay Helberg commented on FOP-2291:
---

Thanks, Vincent. I had (apparently incorrectly) assumed that the second page, 
not having any content, would not generate any areas and thus would satisfy the 
blank-or-not-blank criterion.

It seems that there ought to be an easier way to generate a blank page within a 
flow without having to resort to a separate page sequence for the purpose. But 
I guess the shortcoming is in the spec rather than the software. Alas, I don't 
think force-page-count will work for me, because I can't tell ahead of time 
whether the blank will be a recto or verso page.

> break-after="page" produces blank page but doesn't use blank page master
> 
>
> Key: FOP-2291
> URL: https://issues.apache.org/jira/browse/FOP-2291
> Project: Fop
>  Issue Type: Bug
>  Components: page-master/layout
>Affects Versions: 1.1
> Environment: Window 7, Java 1.7.0_03
>Reporter: Clay Helberg
> Attachments: blanktest.fo, blanktest.pdf
>
>
> I'm trying to produce a blank page corresponding to some content, using an 
> empty fo:block with break-after="page". It does produce a blank page, but it 
> uses the standard odd or even not-blank page master instead of using the 
> blank page master.
> I've verified that the blank page master triggers for auto-generated blank 
> pages, but not for the manually generated ones.

--
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


Re: [VOTE] Merge Temp_FopFontsForSVG into trunk

2013-08-21 Thread Pascal Sancho
Hi,

from [1], I understand that the BATIK patch is not yet applied on BATIK
trunk, so introducing a such dependency is not a good idea for the moment.

I will vote +1 when the patch will be applied.

For now, we depend on Batik team

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


2013/8/21 Vincent Hennebert 

> This work allows to directly use FOP-configured fonts for SVG images,
> instead of trying to find, via AWT, equivalent fonts installed on the
> system, and then mapping them to FOP fonts when generating the output.
>
> Please note that this introduces a dependency on the trunk version of
> Batik, with the patch from BATIK-1041 applied. That means that before
> releasing the next version of FOP, a new version of Batik will have to
> be released first.
>
> This vote will run until Monday, 26 August 11:00 UTC.
>
> +1 from me.
>
> Thanks,
> Vincent
>



-- 
pascal


[GUMP@vmgump]: Project xml-fop-test (in module xml-fop) failed

2013-08-21 Thread FOP Gump Nightly Build
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project xml-fop-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop-test :  XSL-FO (Formatting Objects) processor


Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/srv/gump/public/workspace/xml-fop/build/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/gump_work/build_xml-fop_xml-fop-test.html
Work Name: build_xml-fop_xml-fop-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 24 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only -Dant.build.clonevm=true 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
gump-test 
[Working Directory: /srv/gump/public/workspace/xml-fop]
CLASSPATH: 
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/xml-fop/build/classes:/srv/gump/public/workspace/xml-fop/build/codegen-classes:/srv/gump/public/workspace/xml-fop/build/test-classes:/srv/gump/public/workspace/xml-fop/lib/build/asm-3.1.jar:/srv/gump/public/workspace/xml-fop/lib/build/mockito-core-1.8.5.jar:/srv/gump/public/workspace/xml-fop/lib/build/qdox-1.12.jar:/srv/gump/public/workspace/xml-fop/build/fop.jar:/srv/gump/public/workspace/xml-fop/build/fop-sandbox.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/jav
 
a/build/resolver.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/avalon-framework-impl-4.3.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.5-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20130821.jar:/srv/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/batik-slideshow.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/batik-svgpp.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-anim.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-awt-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-bridge.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-codec.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-css.jar:/srv/gump/public/workspace/xml-bati
 
k/batik-20130821/lib/batik-dom.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-ext.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-extension.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-gui-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-gvt.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-parser.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-script.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-svg-dom.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-svggen.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-swing.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-transcoder.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130821/lib/batik-xml.jar:/srv/gump/public/workspace/xmlgraphics-commons/build/xmlgraphics-commons-2013082
 
1.jar:/srv/gump/packages/fop-hyph/fop-hyph.jar:/srv/gump/public/workspace/junit/dist/junit-20130821.jar:/srv/gump/public/workspace/junit/dist/junit-dep-20130821.jar:/srv/gump/public/workspace/xmlunit/build/java/lib/xmlunit-sumo-20130821.jar

[jira] [Resolved] (FOP-2291) break-after="page" produces blank page but doesn't use blank page master

2013-08-21 Thread Vincent Hennebert (JIRA)

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

Vincent Hennebert resolved FOP-2291.


Resolution: Invalid

Indeed the output is correct WRT the spec. See section 7.27.2, 
"blank-or-not-blank", of the XSL-FO 1.1 Recommendation. The master is eligible 
if there are no areas to be put on that page. However, on page 2 of your 
example, there is an (empty) area generated by the third fo:block.

If you want a real blank page, you have to play with multiple page-sequences 
and the force-page-count property.

HTH,
Vincent

> break-after="page" produces blank page but doesn't use blank page master
> 
>
> Key: FOP-2291
> URL: https://issues.apache.org/jira/browse/FOP-2291
> Project: Fop
>  Issue Type: Bug
>  Components: page-master/layout
>Affects Versions: 1.1
> Environment: Window 7, Java 1.7.0_03
>Reporter: Clay Helberg
> Attachments: blanktest.fo, blanktest.pdf
>
>
> I'm trying to produce a blank page corresponding to some content, using an 
> empty fo:block with break-after="page". It does produce a blank page, but it 
> uses the standard odd or even not-blank page master instead of using the 
> blank page master.
> I've verified that the blank page master triggers for auto-generated blank 
> pages, but not for the manually generated ones.

--
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


[VOTE] Merge Temp_FopFontsForSVG into trunk

2013-08-21 Thread Vincent Hennebert
This work allows to directly use FOP-configured fonts for SVG images,
instead of trying to find, via AWT, equivalent fonts installed on the
system, and then mapping them to FOP fonts when generating the output.

Please note that this introduces a dependency on the trunk version of
Batik, with the patch from BATIK-1041 applied. That means that before
releasing the next version of FOP, a new version of Batik will have to
be released first.

This vote will run until Monday, 26 August 11:00 UTC.

+1 from me.

Thanks,
Vincent


Re: [GUMP@vmgump]: Project xml-fop (in module xml-fop) failed

2013-08-21 Thread Luis Bernardo
FYI, this has been fixed with some help from Stefan from Gump. The fix is
here: http://svn.apache.org/viewvc?view=revision&revision=1515745 (we can
commit to the Gump descriptor for fop).

I also noticed that the Gump build is using snapshots from many of the
projects fop depends on (batik, xerces, xalan, xml-apis and so on), not the
corresponding jars in the lib directory. So I would like to suggest that,
if applicable, we upgrade these jars to the most recent release.


On Mon, Aug 19, 2013 at 12:51 AM, Luis Bernardo wrote:

>
> This is certainly caused by a missing fontbox jar. Does anyone know where
> the gump config file for fop (I assume there must be one) resides?
>
>
> On 8/18/13 12:40 AM, Jeremias Maerki wrote:
>
>> To whom it may engage...
>>  This is an automated request, but not an unsolicited one. For
>> more information please visit 
>> http://gump.apache.org/nagged.**html
>> ,
>> and/or contact the folk at gene...@gump.apache.org.
>>
>> Project xml-fop has an issue affecting its community integration.
>> This issue affects 2 projects,
>>   and has been outstanding for 12 runs.
>> The current state of this project is 'Failed', with reason 'Build Failed'.
>> For reference only, the following projects are affected by this:
>>  - xml-fop :  XSL-FO (Formatting Objects) processor
>>  - xml-fop-test :  XSL-FO (Formatting Objects) processor
>>
>>
>> Full details are available at:
>>  
>> http://vmgump.apache.org/gump/**public/xml-fop/xml-fop/index.**html
>>
>> That said, some information snippets are provided here.
>>
>> The following annotations (debug/informational/warning/**error messages)
>> were provided:
>>   -INFO- Made directory [/srv/gump/public/workspace/**
>> xml-fop/build/classes]
>>   -INFO- Made directory [/srv/gump/public/workspace/**
>> xml-fop/build/codegen-classes]
>>   -INFO- Failed with reason build failed
>>   -DEBUG- Extracted fallback artifacts from Gump Repository
>>
>>
>>
>> The following work was performed:
>> http://vmgump.apache.org/gump/**public/xml-fop/xml-fop/gump_**
>> work/build_xml-fop_xml-fop.**html
>> Work Name: build_xml-fop_xml-fop (Type: Build)
>> Work ended in a state of : Failed
>> Elapsed: 32 secs
>> Command Line: /usr/lib/jvm/java-7-oracle/**bin/java
>> -Djava.awt.headless=true -Dbuild.sysclasspath=only
>> -Xbootclasspath/p:/srv/gump/**public/workspace/xml-xalan/**
>> build/xalan-unbundled.jar:/**srv/gump/public/workspace/xml-**
>> xalan/build/serializer.jar:/**srv/gump/public/workspace/xml-**
>> commons/java/external/build/**xml-apis.jar:/srv/gump/public/**
>> workspace/xml-xerces2/build/**xercesImpl.jar org.apache.tools.ant.Main
>> -Dgump.merge=/srv/gump/public/**gump/work/merge.xml gump
>> [Working Directory: /srv/gump/public/workspace/**xml-fop]
>> CLASSPATH: /usr/lib/jvm/java-7-oracle/**lib/tools.jar:/srv/gump/**
>> public/workspace/xml-fop/**build/classes:/srv/gump/**
>> public/workspace/xml-fop/**build/codegen-classes:/srv/**
>> gump/public/workspace/xml-fop/**build/sandbox-classes:/srv/**
>> gump/public/workspace/xml-fop/**lib/build/asm-3.1.jar:/srv/**
>> gump/public/workspace/xml-fop/**lib/build/qdox-1.12.jar:/srv/**
>> gump/public/workspace/ant/**dist/lib/ant.jar:/srv/gump/**
>> public/workspace/ant/dist/lib/**ant-launcher.jar:/srv/gump/**
>> public/workspace/ant/dist/lib/**ant-jmf.jar:/srv/gump/public/**
>> workspace/ant/dist/lib/ant-**junit.jar:/srv/gump/public/**
>> workspace/ant/dist/lib/ant-**junit4.jar:/srv/gump/public/**
>> workspace/ant/dist/lib/ant-**swing.jar:/srv/gump/public/**
>> workspace/ant/dist/lib/ant-**apache-resolver.jar:/srv/gump/**
>> public/workspace/ant/dist/lib/**ant-apache-xalan2.jar:/srv/**
>> gump/public/workspace/xml-**commons/java/build/resolver.**
>> jar:/srv/gump/packages/apache-**attic/avalon-framework-api-4.**
>> 3.jar:/srv/gump/packages/**apache-attic/avalon-framework-**
>> impl-4.3.jar:/srv/gump/public/**workspace/
>>   apache-commons/io/target/**commons-io-2.5-SNAPSHOT.jar:/**
>> srv/gump/public/workspace/**apache-commons/logging/target/**
>> commons-logging-20130818.jar:/**srv/gump/public/workspace/**
>> pdfbox/fontbox/target/fontbox-**2.0.0-SNAPSHOT.jar:/srv/gump/**
>> public/workspace/jakarta-**servletapi/dist/lib/servlet.**
>> jar:/srv/gump/public/**workspace/xml-commons/java/**
>> external/build/xml-apis-ext.**jar:/srv/gump/public/**
>> workspace/xml-batik/batik-**20130818/batik-slideshow.jar:/**
>> srv/gump/public/workspace/xml-**batik/batik-20130818/batik-**
>> svgpp.jar:/srv/gump/public/**workspace/xml-batik/batik-**
>> 20130818/lib/batik-anim.jar:/**srv/gump/public/workspace/xml-**
>> batik/batik-20130818/lib/**batik-awt-util.jar:/srv/gump/**
>> public/workspace/xml-batik/**batik-20130818/lib/batik-**
>> bridge.jar:/srv/gump/public/**workspace/xml-batik/batik-**
>> 20130818/lib/batik-codec.jar:/