Bug 51060 - font configuration: embed-url tag does not support relative paths anymore
Summary: font configuration: embed-url tag does not support relative paths anymore
Status: RESOLVED WORKSFORME
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: 1.0
Hardware: PC Linux
: P3 regression
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-14 03:46 UTC by Ulrich Mayring
Modified: 2012-06-18 14:45 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Mayring 2011-04-14 03:46:42 UTC 
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.
Comment 1 Ulrich Mayring 2011-04-14 03:48:00 UTC 
See the following thread in fop-users:

http://old.nabble.com/Fop-1.0%3A-resolving-relative-Font-URLs-td31386824.html#a31394545
Comment 2 Glenn Adams 2012-04-07 01:41:55 UTC 
resetting P2 open bugs to P3 pending further review
Comment 3 Glenn Adams 2012-04-08 09:18:42 UTC 
please provide (1) a full copy of the FOP configuration producing the problem, and (2) full console output when encountering the problem;
Comment 4 Glenn Adams 2012-04-24 05:25:24 UTC 
(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
Comment 5 Ulrich Mayring 2012-06-18 12:08:28 UTC 
I don't remember how I got this error last year. At this point I cannot reproduce it anymore. Thanks for looking at it.
Comment 6 Glenn Adams 2012-06-18 14:45:28 UTC 
per comment 5, not reproducible