That depends what you mean by simple versus not simple.  It would be a
lot easier to understand what you're talking about if you have one that
works and one that doesn't work on the same machine,
Are they referencing the same fop config file?
Can you send a sample of each xslt or fo file?

________________________________

From: Roberto Cahanap [mailto:rcaha...@bioreference.com] 
Sent: Wednesday, February 02, 2011 9:57 AM
To: fop-users@xmlgraphics.apache.org
Subject: RE: font missing warning



Hello Eric,

 

What I don't understand is that a simple page does not get this error
and finds the font.

 

The file is installed on the production machine (Windows Server 2003
Enterprise Edition), it's called CONSOLA.TTF (Consolas True Type).

 

I'm going to run a couple of experiments today to see what's up with
this issue.

 

 

Roberto Cahanap

Developer, Reporting Department

Bio-Reference Laboratories, Inc.

Phone: 800-229-5227 x8499

Cell: 201-693-0132

Fax: 201-475-0344

Email: rcaha...@bioreference.com

 

From: Eric Douglas [mailto:edoug...@blockhouse.com] 
Sent: Wednesday, February 02, 2011 9:19 AM
To: fop-users@xmlgraphics.apache.org
Subject: RE: font missing warning

 

Obviously it means it can't find the font.  auto-detect is usually not a
good idea.  It depends on the font file being found on the machine it's
running on.

What file contains that font triplet?  Is that installed on the
production machine?  Obviously it's either not installed there or
there's something different about the search path.

 

________________________________

From: Roberto Cahanap [mailto:rcaha...@bioreference.com] 
Sent: Wednesday, February 02, 2011 9:12 AM
To: fop-users@xmlgraphics.apache.org
Subject: font missing warning

Hello!

 

We are getting this warning when we try to create a PDF:

 

Feb 1, 2011 4:35:03 PM org.apache.fop.fonts.FontInfo
notifyFontReplacement

WARNING: Font 'Consolas,normal,400' not found. Substituting with
'any,normal,400'.

 

Our environment - we have another program that creates the XML and XSL.
We use FOP to create the PDF from these files.

 

Some things to note about our problem:

-          If we have a simple XSL, then we don't get this error

-          We have two environments (TEST and PRODUCTION), it works OK
in our TEST environment

-          We are using FOP 0.95

-          We use <auto-detect/> in the fop configuration file to detect
the font.

 

Does anybody know what could be causing this issue?

 

Thank you!

The information transmitted in this email and any of its attachments is
intended only for the person or entity to which it is addressed and may
contain BioReference Laboratories proprietary information, which is
privileged, confidential, or subject to copyright belonging to
BioReference Laboratories. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is prohibited
and may be unlawful. If you received this in error, please contact the
sender immediately and delete and destroy the communication and all of
the attachments you have received and all copies thereof.
The information transmitted in this email and any of its attachments is
intended only for the person or entity to which it is addressed and may
contain BioReference Laboratories proprietary information, which is
privileged, confidential, or subject to copyright belonging to
BioReference Laboratories. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is prohibited
and may be unlawful. If you received this in error, please contact the
sender immediately and delete and destroy the communication and all of
the attachments you have received and all copies thereof.

Reply via email to