Hi dear Vincent!

First of all, thank you a lot for your explanations!!!

...the reason was to make the Jeuclid plug-in work more out of the box...

I checked on my system - I don't have the Jeuclid plug-in on my system
(should be in /lib directory, right?).
Does it come by default with FOP or its a separate utility?

...The workaround is to explicitly define the font-family property, and not
rely on the default value provided by FOP (this is usually done by
setting it on the fo:root or fo:page-sequence elements)....

I tried the following in my stylesheet:

<xsl:attribute-set name="root.properties">
  <xsl:attribute name="font-family">
    <xsl:value-of select="sans-serif"/>
  </xsl:attribute>
</xsl:attribute-set>

it did change the font-family in <fo:root> but warnings did not disappear. I
don't know how to customize fo:page-sequence elements. Please, advise!

I also tried customizing the fop conf file:
        
          <font-triplet name="Symbol" style="normal" weight="bold"/>
        

        
          <font-triplet name="ZapfDingbats" style="normal" weight="700"/>
        

        
          <font-triplet name="ZapfDingbats" style="italic" weight="700"/>
        

        
          <font-triplet name="ZapfDingbats" style="italic" weight="400"/>
        

The warnings completely disappear, but when I try to use a Zapfdingbat
character in my XML (for example, 
&#x260E; - for a phone icon), # appears instead. Does FOP find Zapfdingbat
font at all? If not, why doesn't show the warning?

Thanks a lot in advance!
nancy



Vincent Hennebert-2 wrote:
> 
> Hi Nancy,
> 
> nancy_b wrote:
>> Hi,
>> 
>> Thanks a lot for suggestions. It seems that I have increased JAVA heap
>> space, by specifying -Xmx1000m (I have 2Gb) , although I am not sure how
>> much I should really allocate for running compilation of large docs. 
> 
> If that works with -Xmx1000m, then go for it. If for some reason you
> want to use as few memory as possible, then gradually increase the value
> of -Xmx until the OutOfMemoryError disappears. But you probably don’t
> want/need to bother so much.
> 
> 
>> The question that remained unclear is that while FOP 0.94 doesn't 
>> complain
>> on the fonts, FOP 0.95 generates the following error message:
> 
> A change was made in FOP 0.95 about the default value of the font-family
> property. Until 0.94 that was "sans-serif", in 0.95 it was changed to
> "sans-serif,Symbol,ZapfDingats". IIRC the reason was to make the Jeuclid
> plug-in work more out of the box, but it has the unfortunate side effect
> of issuing the warnings below as soon as you use bold text. There is an
> open bug about that:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=47279
> 
> The workaround is to explicitly define the font-family property, and not
> rely on the default value provided by FOP (this is usually done by
> setting it on the fo:root or fo:page-sequence elements).
> 
> 
>> WARNING: Font 'Symbol,normal,700' not found. Substituting with
>> 'Symbol,normal,400'.
>> Jun 2, 2009 2:14:25 PM org.apache.fop.fonts.FontInfo
>> notifyFontReplacement
>> WARNING: Font 'ZapfDingbats,normal,700' not found. Substituting with
>> 'ZapfDingbats,normal,400'.
>> Jun 2, 2009 2:14:31 PM org.apache.fop.hyphenation.Hyphenator
>> getHyphenationTree 
>> 
>> I don't understand why FOP 0.94 did not have such a problem, while FOP
>> 0.95
>> does. I checked on my Linux Debian system - it does have the Symbol font
>> in
>> /usr/share/cups/fonts/. For Zapfdinbats I found the following file:
>> /usr/lib/openoffice/share/psprint/fontmetric/ZapfDingbats.afm. I think
>> that's just a metric file for the font. So, I put the following in FOP's
>> conf file:
>> 
>>        
>>           <font-triplet name="Symbol" style="normal" weight="700"/>
>>         
>> 
>>      
>>           <font-triplet name="ZapfDingbats" style="normal" weight="700"/>
>>         
>> 
>>      
>>           <font-triplet name="ZapfDingbats" style="italic" weight="700"/>
>>         
>> 
>>      
>>           <font-triplet name="ZapfDingbats" style="italic" weight="400"/>
>>         
>> 
>> And guess what, the warning disappeared. The question is whether it
>> really
>> solved the problem - whether FOP really identified these fonts. For
>> example,
>> I don't have ZapfDingbats font - just its metric?!
> 
> You must have put those font-triplet elements inside a font element,
> haven’t you? A font-triplet element is not allowed elsewhere.
> 
> FWIW, the gsfonts package contains clones of the Symbol and ZapfDingbats
> fonts, they can be found in the /usr/share/fonts/type1/gsfonts/
> directory, under the names s050000l.* and d050000l.* (obvious names,
> isn’t it ;-) ). But bold/italic versions aren’t available. If you do
> something like the following, which I suspect is what you meant with
> your font triplets above:
>   
>     <font-triplet name="Symbol" style="normal" weight="bold"/>
>   
> then you effectively use the normal Symbol as a replacement for the bold
> one (the text won’t appear in bold!).
> 
> All that said, stick to the advice above and explicitly define the
> font-family property instead, and you should get rid of those warnings.
> 
>> Thanks for your in put in advance!!!
>> 
>> Regards,
>> Nancy
> 
> <snip/>
> 
> HTH,
> Vincent
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/FOP-0.95-fails-to-compile-large-PDF-files---java-heap-space-tp23816647p23851440.html
Sent from the FOP - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Reply via email to