Re: Font substitution
Jeremias Maerki a écrit : The fallback that is currently implemented in FOP only addresses the case where a whole font is not available. What you want is the fallback per character. And that's not implemented just by hacking the PDF renderer. So the ultimate goal is to implement: http://www.w3.org/TR/xsl11/#font-selection-strategy Or if you are sure that the Lucida font contains all the characters you need, you can directly specify this font for the whole FO document: fo:page-sequence font-family=Lucida... for each page-sequence, plus you setup the Lucida font as usual in your config file: http://xmlgraphics.apache.org/fop/0.93/fonts.html#custom That way every character will appear in Lucida, you have both a consistent and working result. Is that what you need? snip/ Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
fop 0.93 and use of OTF
Hi, I've read in the release notes that FOP 0.93 supports the use of otf, but it doesn't explain how, or at least I didn't find that explanation. With ttf, I obtain the xml with a certain instruction. Which one is the instruction to obtain the xml file from an .otf? And should I modify the fop.xconf in the same way I did it for the .ttf? Thanks in advance -- View this message in context: http://www.nabble.com/fop-0.93-and-use-of-OTF-tf3838627.html#a10868634 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop 0.93 and use of OTF
Yes, just substitute .tff with .otf but please note that OTF fonts with CFF glyphs are still not supported. So there's no guarantee that all OTF fonts will work. You will have to try it out. On 30.05.2007 09:11:39 Oz wrote: Hi, I've read in the release notes that FOP 0.93 supports the use of otf, but it doesn't explain how, or at least I didn't find that explanation. With ttf, I obtain the xml with a certain instruction. Which one is the instruction to obtain the xml file from an .otf? And should I modify the fop.xconf in the same way I did it for the .ttf? Thanks in advance -- View this message in context: http://www.nabble.com/fop-0.93-and-use-of-OTF-tf3838627.html#a10868634 Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Ref-IDs in custom FOP 0.93 extension
Hi Jeremias, PageViewport page = (PageViewport) context.getProperty(PAGE_VIEWPORT); int pageCount = page.getPageSequence().getPageCount(); already tried this, but as you say, the page count is not the final one but only includes the pages added so far to the PageSequence. The PageNumberCitationLayoutManager can insert an UnresolvedPageNumber area tree object into the area tree. UnresolvedPageNumber implements Resolvable. Maybe something could be done with this interface but I'm not sure without going deeper. I'll look into it but thinking about it I rather like your second approach... Let me just say that I'm usually post-processing the print files if I have to add packaging marks (like OMR etc.). That would certainly be easier to implement and provides options for parallelizing document production as FOP is usually the most CPU-eating part of the chain. I had a look at the rendered PS files and it seems like the PS FOP renderer is producing easily processable output. I'll go ahead and try to use the EPSTranscoder of FOP to render the SVG DOM containing the barcode into EPS and then enrich the original PS file. I'll let you know of the results. BTW, what's that barcode you're implementing? The barcode applied to the output is read by the BOEWE 154/2-91SB mass printing facility, so that the printed output ends up in the correct envelope for postal shipment. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop 0.93 and use of OTF
Hi, Unfortunatelly, my font contains CFF glyphs. Is version 1.0 going to support this kind of fonts? This support will be for pdf and pcl? only for pdf? Do you have an approximate date of release for version 1.0? Thanks in advance Jeremias Maerki-2 wrote: Yes, just substitute .tff with .otf but please note that OTF fonts with CFF glyphs are still not supported. So there's no guarantee that all OTF fonts will work. You will have to try it out. On 30.05.2007 09:11:39 Oz wrote: Hi, I've read in the release notes that FOP 0.93 supports the use of otf, but it doesn't explain how, or at least I didn't find that explanation. With ttf, I obtain the xml with a certain instruction. Which one is the instruction to obtain the xml file from an .otf? And should I modify the fop.xconf in the same way I did it for the .ttf? Thanks in advance -- View this message in context: http://www.nabble.com/fop-0.93-and-use-of-OTF-tf3838627.html#a10868634 Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/fop-0.93-and-use-of-OTF-tf3838627.html#a10873434 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Not able generate parse html from xml using XSL Fo
Hi, I am using an xml file which has the below tag AddInfolt;fo:block font-style=quot;italicquot;gt;URGENT! Please note that comments have changed. Please review thoroughly.lt;/fo:blockgt; /AddInfo And an xsl fo which is of the below form fo:block text-align=justify line-height=20pt space-after.optimum=7pt xsl:value-of select=AddInfo disable-output-escaping=yes/ /fo:block The XSL Output.html is below fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block I use org.apache.fop.apps.XSLTInputHandler to input the xml and xsl file and set driver render to pdfformat to generate pdf But the parser does not seems to be parsing the fo:block font-style in the XML file . The pdf output looks like below fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block But I expect that the italic should be applied to the text The xml would generated dynamically with different attributes of fo:block or html tags How could I use these dynamically generated xml tags which has an fo:block or html tag that is parsed and converted to a pdf using xsl fo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able generate parse html from xml using XSL Fo
Hi Balamurali, I believe you are using an older 0.20 release of FOP which is no longer actively supported. I'm not sure about the support for what you are trying to do in that version. If it is possible to do so, I'd recommend upgrading to 0.93 and try again. Cheers, Adrian. [EMAIL PROTECTED] wrote: Hi, I am using an xml file which has the below tag AddInfolt;fo:block font-style=quot;italicquot;gt;URGENT! Please note that comments have changed. Please review thoroughly.lt;/fo:blockgt; /AddInfo And an xsl fo which is of the below form fo:block text-align=justify line-height=20pt space-after.optimum=7pt xsl:value-of select=AddInfo disable-output-escaping=yes/ /fo:block The XSL Output.html is below fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block I use org.apache.fop.apps.XSLTInputHandler to input the xml and xsl file and set driver render to pdfformat to generate pdf But the parser does not seems to be parsing the fo:block font-style in the XML file . The pdf output looks like below fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block But I expect that the italic should be applied to the text The xml would generated dynamically with different attributes of fo:block or html tags How could I use these dynamically generated xml tags which has an fo:block or html tag that is parsed and converted to a pdf using xsl fo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP0.93: png-output in optimized height
Hi Jeremias! Thanks for your hint - it works well. But now I have another problem regarding evaluating the height. I use Arial as font and the area renderer does not calculate the height in Arial. I configured my userconfig.xml as following: http://www.nabble.com/file/p10876199/userconfig.xml userconfig.xml Is there anything wrong? Or is X-fop-areatree not able to calculate in Arial? Thanks, Franz -- View this message in context: http://www.nabble.com/FOP0.93%3A-png-output-in-optimized-height-tf3788704.html#a10876199 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not able generate parse html from xml using XSL Fo
Hi, I am using an xml file which has the below tag AddInfolt;fo:block font-style=quot;italicquot;gt;URGENT! Please note that comments have changed. Please review thoroughly.lt;/fo:blockgt; /AddInfo this is XML with quoted XML inside. The XSL-FO parser will never see the block inside AddInfo (it is just text). Why have you mixed XML with quoted XSL-FO? And an xsl fo which is of the below form fo:block text-align=justify line-height=20pt space-after.optimum=7pt xsl:value-of select=AddInfo disable-output-escaping=yes/ /fo:block This should select the AddInfo element and take the string value. Using d-o-e won't help here, I think, to 'unescape' the text. The XSL Output.html is below fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block No. To me it seems that this is what you see when you view it in an XML renderer (like when you view your output in a browser), but this part is actually lt;fo:block etc (if you view it in a browser, try viewing the source instead). I use org.apache.fop.apps.XSLTInputHandler to input the xml and xsl file and set driver render to pdfformat to generate pdf But the parser does not seems to be parsing the fo:block font-style in the XML file . It cannot, there is no fo:block instruction with font-style attribute, see above, it is escaped. fo:block font-style=italicURGENT! Please note that comments have changed. Please review thoroughly./fo:block But I expect that the italic should be applied to the text No. The xml would generated dynamically with different attributes of fo:block or html tags How could I use these dynamically generated xml tags which has an fo:block or html tag that is parsed and converted to a pdf using xsl fo The simple solution should be: let your XSLT do what it should do: generate XSL-FO. Let your system design be what it should be: separated content from layout; meaning: remove the xsl-fo like stringized XML from your input XML file. Then all will be easy. If you really MUST use this 'embedded' XSL-FO information, you should consider using an extension function that allows re-parsing of a string that contains XML-like text. Saxon provides such an extension function in its XSLT parser. Not sure of others though. No need to try to get the XSL-FO renderer to do what you want, you will have to tackle this in an earlier stage and generate correct XSL-FO. HTH, Cheers, -- Abel Braaksma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop 0.93 and use of OTF
On 30.05.2007 15:46:28 Oz wrote: Hi, Unfortunatelly, my font contains CFF glyphs. Is version 1.0 going to support this kind of fonts? Maybe. FOP is open source. Anything's possible if someone invests the necessary resources. This support will be for pdf and pcl? only for pdf? It may already work for PCL since PCL can use Java2D for painting text. But for PDF a little additional work will be necessary. Do you have an approximate date of release for version 1.0? I'd guess in 2008. http://xmlgraphics.apache.org/fop/faq.html#when Thanks in advance Jeremias Maerki-2 wrote: Yes, just substitute .tff with .otf but please note that OTF fonts with CFF glyphs are still not supported. So there's no guarantee that all OTF fonts will work. You will have to try it out. On 30.05.2007 09:11:39 Oz wrote: Hi, I've read in the release notes that FOP 0.93 supports the use of otf, but it doesn't explain how, or at least I didn't find that explanation. With ttf, I obtain the xml with a certain instruction. Which one is the instruction to obtain the xml file from an .otf? And should I modify the fop.xconf in the same way I did it for the .ttf? Thanks in advance -- View this message in context: http://www.nabble.com/fop-0.93-and-use-of-OTF-tf3838627.html#a10868634 Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
