buildbot exception in ASF Buildbot on fop-trunk

[buildbot]

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

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

[jira] [Created] (FOP-2491) FOP 2.0 cannot support open-type font

[Leo Yang (JIRA)]

Leo Yang created FOP-2491:
-

 Summary: FOP 2.0 cannot support open-type font
 Key: FOP-2491
 URL: https://issues.apache.org/jira/browse/FOP-2491
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: FOP: 2.0
Open Font: Noto-Sans Cjk 
(https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip)
Reporter: Leo Yang


Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF 
document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk 
font cannot be embedded into PDF document.

How to repeat:
 1. Get FOP 2.0 library.
 2. Get Google-Noto-Sans from 
https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
 3. Set the fop.xconf as following:
 
 
 
 4. Set the FOP as following:
 
 http://www.w3.org/1999/XSL/Format";>
 
 
 
 
 
 
 
 Hello Noto-OTF!
 
 
 
 5. Generate the PDF, there is no error reported.
 6. Open the PDF file in Acro-Reader, it will report the "cannot extract the 
embedded font" error.




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