Hi Andreas, Thank you a lot for your valuable help!!! I really appreciate that!
I decided not to use workarounds, and wait for the next FOP build. I can live with these warnings for a while - the main thing is to understand why they are generated. Could I ask the last question in this long thread please? Why are the Symbol and Zapfdiongbat fonts unavailable in italic/bold version? Thank you a lot in advance for building fop.jar for me. You are so kind! :clap: My best wishes, Nancy Andreas Delmelle-2 wrote: > > On 04 Jun 2009, at 17:01, nancy_b wrote: > > Hi Nancy > >> It seems that getting FOP from the trunk is too complicated for me. >> When is >> the next binary FOP version due to? > > Well, it was initially planned for early this year, but we didn't > quite get around to it yet. > > >> Regarding what you said about <fo:block linefeed- >> treatment="preserve"> - I >> have no idea how to translate this into XSL/XML. > > I admit, this probably requires a significant level of understanding > all the Docbook stylesheets' code... > >> Meantime, I did some other tests. Bob Stayton suggested the following >> workaround for producing special characters: >> <xsl:template match="symb...@role = 'symbolfont']"> >> <fo:inline font-family="Symbol"> >> <xsl:call-template name="inline.charseq"/> >> </fo:inline> >> </xsl:template> > > Personally, as mentioned, I'd make that fo:wrapper instead of > fo:inline. fo:inline is really only useful if you need borders or > special alignment (sub- or superscript), or if you need margins (which > FOP currently does not completely support on inlines anyway). Not that > it will have much impact on the result, but the memory consumption > should decrease slightly. Every little bit helps there. > >> So I modified it by adding Zapfdingbats before Symbol, and used >> <symbol role >> = 'symbolfont'>☎</symbol> in my XML. Guess what, it did show >> the phone >> symbol, but also converted my math symbol into scissors (rrrrrrr). >> So, I am sick and tired of this -- the only way out is to wait for >> bugfix in FOP, am >> I right? > > I think so. I'll build a fop.jar off today's trunk, and send it to you > off-list, so you can try it out and see if that fares better (although > I'd rather not see this becoming a standard practice, I'm always > willing to make an exception now and then, until we get the automated > snapshots operational again) > > > Regards > > Andreas > > --------------------------------------------------------------------- > 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-tp23816647p23909748.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
