You need to set font-base property or programmatically:
fopFactory.getFontManager().setFontBaseURL(file:///C:/Temp/fonts);
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail:
Terence M. Bandoian wrote:
Hi, Ulrich-
That matches my experience with 1.0. Setting font-base works with
metric-url but I've used absolute paths for embed-url.
So then it appears to be a bug. I'll report it.
Ulrich
--
View this message in context:
Hi Ulrich,
Sorry for the late reply, but /my/font/path isn't a reference to a
relative path. That's an absolute path. If the absolute path of your
font were /my/font/path/myfont.ttf, then your config is correct, and
you are right in issuing a bug. But if your font is located at
directory of
mehdi houshmand wrote:
Sorry for the late reply, but /my/font/path isn't a reference to a
relative path. That's an absolute path. If the absolute path of your
font were /my/font/path/myfont.ttf, then your config is correct, and
you are right in issuing a bug.
Mehdi,
I think I know the
Hi, Ulrich-
I took another look at my configuration and wanted to clarify. I ended
up using absolute paths for the embed-urls because the font files were
in a different directory than the metrics files.
However, I did have to place the font-base tag at the top level in the
configuration
Hi,
Relative font path works for me on embed-url attribute (Windows + JDK
6.0.20), whatever FOP version (0.95, 1.0, or TRUNK):
Either on my dev machine (invoking FOP via CLI):
snip
font-basefile:///D:/fonts/font-base
font kerning=yes embed-url=dejavu/DejaVuSans.ttf.../font
/snip
Or in
Hm, maybe it's not a problem with the FOP code itself, but with the new
version of xmlgraphics-commons included in FOP 1.0. At least there seems to
be a new class called CommonURIResolve involved, which wasn't used in FOP
0.95.
Ulrich
--
View this message in context:
On 14 Apr 2011, at 17:15, Ulrich Mayring wrote:
Hi Ulrich
Hm, maybe it's not a problem with the FOP code itself, but with the new
version of xmlgraphics-commons included in FOP 1.0. At least there seems to
be a new class called CommonURIResolve involved, which wasn't used in FOP
0.95.
In
On 14 Apr 2011, at 17:28, Andreas L. Delmelle wrote:
In that case, can you check what happens if you use
a trailing slash in the embed-url?
^^
Errmm... Sorry, too quick. I obviously meant 'the font-base'.
Regards
Andreas
---
I already tried the trailing slash yesterday, when you first suggested it.
However, I had to change the code of our application for that, as it doesn't
honor the setting in fop.xconf normally. The result was the same, though.
Normally our application sets the font path programmatically and it
Hi Ulrich,
Have you tried setting the font-base in your fop.xconf? I must admit I
haven't used the API much but you can set the font-base by inserting
following in the fop.xconf:
font-base ** the base directory ** /font-base
The configuration page on the fop website may help you,
mehdi houshmand wrote:
Hi Ulrich,
Have you tried setting the font-base in your fop.xconf? I must admit I
haven't used the API much but you can set the font-base by inserting
following in the fop.xconf:
font-base ** the base directory ** /font-base
Hi Mehdi,
we have set the font-base
On 04/13/2011 02:58 PM, Ulrich Mayring wrote:
mehdi houshmand wrote:
Hi Ulrich,
Have you tried setting the font-base in your fop.xconf? I must admit I
haven't used the API much but you can set the font-base by inserting
following in the fop.xconf:
font-base ** the base directory
Hi Ulrich,
Have you tried using file URIs for the font-base? This would be in the
format file:///path/to/font (for unix), for windows based ones, google
will help you, I don't use Windows regularly so I wouldn't want to
speculate
Mehdi
On 13 April 2011 13:58, Ulrich Mayring u...@denic.de
I have tried both suggestions, using a file-url and appending a slash, but to
no avail.
Please keep in mind that this is a regression, i. e. not I am doing
something wrong, but something changed from fop 0.95 to fop 1.0. Take
another look at the error message:
Failed to resolve font with
Hi Ulrich,
I have no solution, only questions:
- Are the 2 FOP versions run on the same host?
- What OS do you experiment?
- Have you tried direct access to /path/to/fonts + / + myfont.ttf
(either with ls or dir) ?
- Does FOP 1.0 load the right fop.xconf file, if any?
Le 13/04/2011 16:29,
Pascal Sancho wrote:
Hi Ulrich,
I have no solution, only questions:
- Are the 2 FOP versions run on the same host?
- What OS do you experiment?
- Have you tried direct access to /path/to/fonts + / + myfont.ttf
(either with ls or dir) ?
- Does FOP 1.0 load the right fop.xconf
On 13 Apr 2011, at 17:33, Ulrich Mayring wrote:
Hi Ulrich
All I'm doing is replace fop-0.95.jar with fop-1.0.jar and our
application ceases to work.
Just a thought: it might be that the font-cache has also changed slightly
between the two versions.
Try adding a line to your code like
On 4/13/2011 10:54 AM, Andreas L. Delmelle wrote:
On 13 Apr 2011, at 17:33, Ulrich Mayring wrote:
Hi Ulrich
All I'm doing is replace fop-0.95.jar with fop-1.0.jar and our
application ceases to work.
Just a thought: it might be that the font-cache has also changed slightly
between the two
19 matches
Mail list logo
