On Aug 6, 2008, at 00:06, lmhelp wrote:
Hi,
Thank you for your answer.
That's a very --original way to specify a pathname containing a
space.
I don't think I've ever seen that before. Does Windows even accept
it?
I do not know if you are joking or not...
I was --and then I wasn't. I must admit, the feeling was mutual.
but Windows unfortunately does.
Nice to know. Awfully weird, though.
If you remove the quotes, it should work fine.
It doesn't.
I have even tried with:
<value>file:///C:\Progra~1\fop\fonts_lea</value>
this is not better.
There really is no reason to work around the space. When the URL is
parsed from the string, it will normally be escaped to '%20' anyway
(as will the double quotes be escaped to '%22', so the original 'URI'
would come to look like: file:///c:\%22Program%20Files%22\fop\fop_lea')
Any other ideas?
Can you try running FOP with the '-d' command-line option, and see if
any more clues appear? IIC, it should then also tell you more about /
why/ the font cannot be found...
Maybe it's the missing trailing backslash, which, strictly speaking,
makes your fontBaseDir 'c:\program files\fop'. I know that the more
recent versions of FOP compensate for this, but I don't remember if
0.20.5 already did.
HTH!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
