You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Jörn Kottmann <ko...@gmail.com> on 2009/06/02 11:51:34 UTC

Failed to resolve font with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'

Hi,

when I am building our docbook on linux or mac os. I get this exception:

     [java] SEVERE: Exception
     [java] org.apache.fop.apps.FOPException: Failed to resolve font 
with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'
     [java]     at org.apache.fop.util.LogUtil.handleError(LogUtil.java:38)
     [java]     at 
org.apache.fop.render.PrintRendererConfigurator.getFontInfoFromConfiguration(PrintRendererConfigurator.java:275)
     [java]     at 
org.apache.fop.render.PrintRendererConfigurator.buildFontListFromConfiguration(PrintRendererConfigurator.java:207)
     [java]     at 
org.apache.fop.render.PrintRendererConfigurator.configure(PrintRendererConfigurator.java:95)
     [java]     at 
org.apache.fop.render.pdf.PDFRendererConfigurator.configure(PDFRendererConfigurator.java:71)
     [java]     at 
org.apache.fop.render.RendererFactory.createRenderer(RendererFactory.java:187)
     [java]     at 
org.apache.fop.area.RenderPagesModel.<init>(RenderPagesModel.java:68)
     [java]     at 
org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:127)
     [java]     at 
org.apache.fop.area.AreaTreeHandler.<init>(AreaTreeHandler.java:102)
     [java]     at 
org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:224)
     [java]     at 
org.apache.fop.fo.FOTreeBuilder.<init>(FOTreeBuilder.java:100)
     [java]     at 
org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)
     [java]     at org.apache.fop.apps.Fop.<init>(Fop.java:78)
     [java]     at 
org.apache.fop.apps.FopFactory.newFop(FopFactory.java:247)
     [java]     at 
org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:104)
     [java]     at org.apache.fop.cli.Main.startFOP(Main.java:166)
     [java]     at org.apache.fop.cli.Main.main(Main.java:197)


Does it makes a difference in the result if its build on a non-windows os ?

Jörn

Re: Failed to resolve font with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'

Posted by Michael Tanenblatt <sl...@park-slope.net>.
FYI, on a Mac, most fonts live in:
	/Library/Fonts/

except certain system fonts, which live in:
	/System/Library/Fonts

Irrelevant to this discussion, but just for completeness: fonts  
installed locally for a specific user are installed in:
	~username/Library/Fonts


On Jun 18, 2009, at 11:15 AM, Thilo Goetz wrote:

> Marshall Schor wrote:
>> Looks like it does make a difference, unless we can find a way to get
>> and access the Palatino Font on Linux and/or MacOS.  One ref on the  
>> web
>> said that it was available on the Mac - but I don't have a mac, and
>> don't know how to set things up to access it.  Palatino is the font
>> being used for the main documentation.
>
> There are two files that contain the font configuration,
> fop-config.xml and fontconfig.xml.  They are almost identical.
> Do we need them both?  It should be easy to replace those
> files with versions that work on other platforms.  I have
> no idea if fonts live in a standard place in linux (probably
> not) and MacOS (probably).  We might want to at least document
> what people need to do to build the documentation on their
> own platform.  I do build on linux now and then, but I guess
> I've never built the documentation there.
>
> --Thilo
>
>>
>> -Marshall
>>
>> Jörn Kottmann wrote:
>>> Hi,
>>>
>>> when I am building our docbook on linux or mac os. I get this  
>>> exception:
>>>
>>>    [java] SEVERE: Exception
>>>    [java] org.apache.fop.apps.FOPException: Failed to resolve font
>>> with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'
>>>    [java]     at
>>> org.apache.fop.util.LogUtil.handleError(LogUtil.java:38)
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop 
>>> .render 
>>> .PrintRendererConfigurator 
>>> .getFontInfoFromConfiguration(PrintRendererConfigurator.java:275)
>>>
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop 
>>> .render 
>>> .PrintRendererConfigurator 
>>> .buildFontListFromConfiguration(PrintRendererConfigurator.java:207)
>>>
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop 
>>> .render 
>>> .PrintRendererConfigurator 
>>> .configure(PrintRendererConfigurator.java:95)
>>>
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop 
>>> .render 
>>> .pdf 
>>> .PDFRendererConfigurator.configure(PDFRendererConfigurator.java:71)
>>>
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop.render.RendererFactory.createRenderer(RendererFactory.java:187)
>>>
>>>    [java]     at
>>> org.apache.fop.area.RenderPagesModel.<init>(RenderPagesModel.java: 
>>> 68)
>>>    [java]     at
>>> org 
>>> .apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java: 
>>> 127)
>>>    [java]     at
>>> org.apache.fop.area.AreaTreeHandler.<init>(AreaTreeHandler.java:102)
>>>    [java]     at
>>> org 
>>> .apache 
>>> .fop 
>>> .render.RendererFactory.createFOEventHandler(RendererFactory.java: 
>>> 224)
>>>
>>>    [java]     at
>>> org.apache.fop.fo.FOTreeBuilder.<init>(FOTreeBuilder.java:100)
>>>    [java]     at
>>> org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)
>>>    [java]     at org.apache.fop.apps.Fop.<init>(Fop.java:78)
>>>    [java]     at
>>> org.apache.fop.apps.FopFactory.newFop(FopFactory.java:247)
>>>    [java]     at
>>> org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:104)
>>>    [java]     at org.apache.fop.cli.Main.startFOP(Main.java:166)
>>>    [java]     at org.apache.fop.cli.Main.main(Main.java:197)
>>>
>>>
>>> Does it makes a difference in the result if its build on a non- 
>>> windows
>>> os ?
>>>
>>> Jörn
>>>
>>>


Re: Failed to resolve font with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'

Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Looks like it does make a difference, unless we can find a way to get
> and access the Palatino Font on Linux and/or MacOS.  One ref on the web
> said that it was available on the Mac - but I don't have a mac, and
> don't know how to set things up to access it.  Palatino is the font
> being used for the main documentation.

There are two files that contain the font configuration,
fop-config.xml and fontconfig.xml.  They are almost identical.
Do we need them both?  It should be easy to replace those
files with versions that work on other platforms.  I have
no idea if fonts live in a standard place in linux (probably
not) and MacOS (probably).  We might want to at least document
what people need to do to build the documentation on their
own platform.  I do build on linux now and then, but I guess
I've never built the documentation there.

--Thilo

> 
> -Marshall
> 
> Jörn Kottmann wrote:
>> Hi,
>>
>> when I am building our docbook on linux or mac os. I get this exception:
>>
>>     [java] SEVERE: Exception
>>     [java] org.apache.fop.apps.FOPException: Failed to resolve font
>> with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'
>>     [java]     at
>> org.apache.fop.util.LogUtil.handleError(LogUtil.java:38)
>>     [java]     at
>> org.apache.fop.render.PrintRendererConfigurator.getFontInfoFromConfiguration(PrintRendererConfigurator.java:275)
>>
>>     [java]     at
>> org.apache.fop.render.PrintRendererConfigurator.buildFontListFromConfiguration(PrintRendererConfigurator.java:207)
>>
>>     [java]     at
>> org.apache.fop.render.PrintRendererConfigurator.configure(PrintRendererConfigurator.java:95)
>>
>>     [java]     at
>> org.apache.fop.render.pdf.PDFRendererConfigurator.configure(PDFRendererConfigurator.java:71)
>>
>>     [java]     at
>> org.apache.fop.render.RendererFactory.createRenderer(RendererFactory.java:187)
>>
>>     [java]     at
>> org.apache.fop.area.RenderPagesModel.<init>(RenderPagesModel.java:68)
>>     [java]     at
>> org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:127)
>>     [java]     at
>> org.apache.fop.area.AreaTreeHandler.<init>(AreaTreeHandler.java:102)
>>     [java]     at
>> org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:224)
>>
>>     [java]     at
>> org.apache.fop.fo.FOTreeBuilder.<init>(FOTreeBuilder.java:100)
>>     [java]     at
>> org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)
>>     [java]     at org.apache.fop.apps.Fop.<init>(Fop.java:78)
>>     [java]     at
>> org.apache.fop.apps.FopFactory.newFop(FopFactory.java:247)
>>     [java]     at
>> org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:104)
>>     [java]     at org.apache.fop.cli.Main.startFOP(Main.java:166)
>>     [java]     at org.apache.fop.cli.Main.main(Main.java:197)
>>
>>
>> Does it makes a difference in the result if its build on a non-windows
>> os ?
>>
>> Jörn
>>
>>

Re: Failed to resolve font with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'

Posted by Marshall Schor <ms...@schor.com>.
Looks like it does make a difference, unless we can find a way to get
and access the Palatino Font on Linux and/or MacOS.  One ref on the web
said that it was available on the Mac - but I don't have a mac, and
don't know how to set things up to access it.  Palatino is the font
being used for the main documentation.

-Marshall

Jörn Kottmann wrote:
> Hi,
>
> when I am building our docbook on linux or mac os. I get this exception:
>
>     [java] SEVERE: Exception
>     [java] org.apache.fop.apps.FOPException: Failed to resolve font
> with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'
>     [java]     at
> org.apache.fop.util.LogUtil.handleError(LogUtil.java:38)
>     [java]     at
> org.apache.fop.render.PrintRendererConfigurator.getFontInfoFromConfiguration(PrintRendererConfigurator.java:275)
>
>     [java]     at
> org.apache.fop.render.PrintRendererConfigurator.buildFontListFromConfiguration(PrintRendererConfigurator.java:207)
>
>     [java]     at
> org.apache.fop.render.PrintRendererConfigurator.configure(PrintRendererConfigurator.java:95)
>
>     [java]     at
> org.apache.fop.render.pdf.PDFRendererConfigurator.configure(PDFRendererConfigurator.java:71)
>
>     [java]     at
> org.apache.fop.render.RendererFactory.createRenderer(RendererFactory.java:187)
>
>     [java]     at
> org.apache.fop.area.RenderPagesModel.<init>(RenderPagesModel.java:68)
>     [java]     at
> org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:127)
>     [java]     at
> org.apache.fop.area.AreaTreeHandler.<init>(AreaTreeHandler.java:102)
>     [java]     at
> org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:224)
>
>     [java]     at
> org.apache.fop.fo.FOTreeBuilder.<init>(FOTreeBuilder.java:100)
>     [java]     at
> org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)
>     [java]     at org.apache.fop.apps.Fop.<init>(Fop.java:78)
>     [java]     at
> org.apache.fop.apps.FopFactory.newFop(FopFactory.java:247)
>     [java]     at
> org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:104)
>     [java]     at org.apache.fop.cli.Main.startFOP(Main.java:166)
>     [java]     at org.apache.fop.cli.Main.main(Main.java:197)
>
>
> Does it makes a difference in the result if its build on a non-windows
> os ?
>
> Jörn
>
>