| Summary: | font configuration: embed-url tag does not support relative paths anymore | ||
|---|---|---|---|
| Product: | Fop - Now in Jira | Reporter: | Ulrich Mayring <ulim> |
| Component: | general | Assignee: | fop-dev |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | regression | ||
| Priority: | P3 | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
See the following thread in fop-users: http://old.nabble.com/Fop-1.0%3A-resolving-relative-Font-URLs-td31386824.html#a31394545 resetting P2 open bugs to P3 pending further review please provide (1) a full copy of the FOP configuration producing the problem, and (2) full console output when encountering the problem; (In reply to comment #3) > please provide (1) a full copy of the FOP configuration producing the problem, > and (2) full console output when encountering the problem; Ulrich, I am still awaiting your input as requested above. if I see no further input by April 30, I will close this bug due to lack of requested information. Regards, Glenn I don't remember how I got this error last year. At this point I cannot reproduce it anymore. Thanks for looking at it. |
In fop.xconf it is possible to have font configurations like this: <font-base>file:/my/font/path</font-base> <font kerning="yes" embed-url="myfont.ttf"> ... </font> This works perfectly in Fop 0.95 and earlier versions, but in Fop 1.0 it throws an exception: org.apache.fop.apps.FOPException: Failed to resolve font with embed-url 'myfont.ttf' at org.apache.fop.util.LogUtil.handleError(LogUtil.java:38) at org.apache.fop.fonts.FontInfoConfigurator.getFontInfo(FontInfoConfigurator.java:212) at org.apache.fop.fonts.FontInfoConfigurator.addFonts(FontInfoConfigurator.java:168) at org.apache.fop.fonts.FontInfoConfigurator.configure(FontInfoConfigurator.java:100) at org.apache.fop.render.PrintRendererConfigurator.buildFontList(PrintRendererConfigurator.java:106) Notes: - using absolute paths in the embed-url attribute still works. - setting the font base attribute programmatically leads to the same problem.