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

2014-05-10 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 has an issue affecting its community integration,
 and has been outstanding for 12 runs.
The current state of this project is 'Failed', with reason 'Synchronize Failed'.

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- Failed with reason synchronize failed
 -DEBUG- Extracted fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml
- Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 2014051107, vmgump.apache.org:vmgump:2014051107
Gump E-mail Identifier (unique within run) #4.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]


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

2014-05-10 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,
 and has been outstanding for 11 runs.
The current state of this project is 'Failed', with reason 'Synchronize Failed'.

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:
 -DEBUG- Dependency on checkstyle exists, no need to add for property 
checkstyle.location.
 -INFO- Failed with reason synchronize failed

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/rss.xml
- Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/atom.xml

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 2014051107, vmgump.apache.org:vmgump:2014051107
Gump E-mail Identifier (unique within run) #7.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]


[jira] [Commented] (FOP-2371) Kerning is applied only to certain combinations

2014-05-10 Thread Glenn Adams (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994425#comment-13994425
 ] 

Glenn Adams commented on FOP-2371:
--

Firstly, you need to determine if complex script features are enabled in your 
testing. If they are, then you need to look at the font's GPOS tables 
associated with the 'kern' feature to determine if the font defines contextual 
kerning. If the are not enabled, then you need to look at the font's 'kern' 
table to determine if kerning entries for the pairs you are asking about are 
present.

Basically, FOP uses what data is in the font to determine kerning. If no data 
is there, there is no kerning. You need to ascertain it is there and enabled 
before we can determine if there is a bug or not. If it is there and is 
enabled, but is not being used, then there may be a bug.

 Kerning is applied only to certain combinations
 ---

 Key: FOP-2371
 URL: https://issues.apache.org/jira/browse/FOP-2371
 Project: Fop
  Issue Type: Bug
  Components: fonts
Affects Versions: 1.1
 Environment: Win 64-bit, JRE 1.7.0_40
Reporter: Jan Tošovský
Priority: Minor
  Labels: kerning
 Attachments: kern.fo, kern.pdf


 When VLTAVA is typed with Palatino Linotype font, the kerning is applied to 
 AV combination only. The rest, i.e. LT, TA and VA, is typeset without kerning.



--
This message was sent by Atlassian JIRA
(v6.2#6252)