Bug 881859
| Summary: | Crash while generating font metrics files | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | info <info> |
| Component: | fop | Assignee: | Ruediger Landmann <rlandman> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | c.david86, rhbugs, warlord |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 12:31:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 885471 | ||
| Bug Blocks: | |||
|
Description
info@kobaltwit.be
2012-11-29 17:24:18 UTC
I don't believe TTF fonts are supported in fop 1.0. Version 1.1 says "Adds support for TTF fonts in PostScript." so I'm going to try to ship 1.1 and see if this fixes your problem. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Meanwhile I have updated to Fedora 18, fop-1.0-20.fc18.noarch The crash is still happening unfortunately, so I reopen this bug. It appears Fop 1.1 has been added to F19. Any chance of a backport to F18 ? Thanks My main system is Fedora 19 (x86_64) now and I tried this again with fop 1.1: it fails with the same error. Too bad, because this is causing me headaches for the GnuCash project... FYI, I just tried this on Fedora 20, which includes the fonts as RPM packages but I still get an error:
bash-4.2$ java -cp /usr/share/java/fop.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar \
> org.apache.fop.fonts.apps.TTFReader \
> /usr/share/fonts/ipa-ex-mincho/ipaexm.ttf /tmp/ipaexm.xml
TTF Reader for Apache FOP SVN tags/fop-1_1
Parsing font...
Reading /usr/share/fonts/ipa-ex-mincho/ipaexm.ttf...
Error while building XML font metrics file.
java.lang.ArrayIndexOutOfBoundsException: 12244
(using fop-1.1-5.fc20.noarch)
A detail that escaped me earlier: the fonts that exhibit this issue (ipa fonts) are not TrueType fonts, but OpenType fonts. It looks like fop doesn't support those. Note that gnucash has switched to other fonts now, but the issue still stands by itself. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Changing version number to keep the bug alive. Tested this again today: still an issue on Fedora 21 (fop-1.1-8.fc21.noarch). This time I tried with several different otf font files. The ipaex fonts referred to earlier still result in the same error message as above. However the lilypond-emmentaler fonts (which are shipped with Fedora) give this message when trying to extract the font metrics: TTF Reader for Apache FOP SVN tags/fop-1_1 Parsing font... Reading emmentaler-11.otf... Font Family: [Emmentaler-11] Error while building XML font metrics file. java.lang.UnsupportedOperationException: OpenType fonts with CFF data are not supported, yet Although it still fails to build the metrics file at least the message is much more userfriendly. A similar message would be much better for the ipaex fonts as well. It seems they have a different internal structure still. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Isn't this still an issue in F23? Or has it finally been solved? Nope, not fixed. I just tested and it's still happening on F23 with
fop-2.0-2.fc23.noarch:
$ java -cp /usr/share/java/fop.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar org.apache.fop.fonts.apps.TTFReader /home/janssege/Development/IPAexfont00201/ipaexm.otf /tmp/ipaexm.xml
Dec 02, 2015 6:21:58 PM org.apache.fop.fonts.apps.AbstractFontReader main
INFO: TTF Reader for Apache FOP SVN branches/fop-2_0
Dec 02, 2015 6:21:58 PM org.apache.fop.fonts.apps.AbstractFontReader main
INFO: Parsing font...
Dec 02, 2015 6:21:58 PM org.apache.fop.fonts.apps.AbstractFontReader loadTTF
INFO: Reading /home/janssege/Development/IPAexfont00201/ipaexm.otf...
Dec 02, 2015 6:21:58 PM org.apache.fop.fonts.apps.AbstractFontReader main
SEVERE: Error while building XML font metrics file.
java.lang.ArrayIndexOutOfBoundsException: 12244
at org.apache.fop.fonts.truetype.OpenFont.readPostScript(OpenFont.java:1320)
at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:736)
at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:216)
at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:166)
And for another otf font:
$ java -cp /usr/share/java/fop.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar org.apache.fop.fonts.apps.TTFReader /usr/share/fonts/abattis-cantarell/Cantarell-Regular.otf /tmp/Cantarell-Regular.xml
Dec 02, 2015 6:25:02 PM org.apache.fop.fonts.apps.AbstractFontReader main
INFO: TTF Reader for Apache FOP SVN branches/fop-2_0
Dec 02, 2015 6:25:02 PM org.apache.fop.fonts.apps.AbstractFontReader main
INFO: Parsing font...
Dec 02, 2015 6:25:02 PM org.apache.fop.fonts.apps.AbstractFontReader loadTTF
INFO: Reading /usr/share/fonts/abattis-cantarell/Cantarell-Regular.otf...
Dec 02, 2015 6:25:02 PM org.apache.fop.fonts.truetype.TTFFile seekTab
SEVERE: Dirtab loca not found.
Dec 02, 2015 6:25:02 PM org.apache.fop.fonts.apps.AbstractFontReader main
SEVERE: Error while building XML font metrics file.
java.io.IOException: 'loca' table not found, happens when the font file doesn't contain TrueType outlines (trying to read an OpenType CFF font maybe?)
at org.apache.fop.fonts.truetype.TTFFile.readIndexToLocation(TTFFile.java:180)
at org.apache.fop.fonts.truetype.TTFFile.updateBBoxAndOffset(TTFFile.java:169)
at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:750)
at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:216)
at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:166)
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |