Re: [SPAM] Font setup is very slow
Yes, of course. I'm using FOP v0.20.5. -- View this message in context: http://www.nabble.com/Font-setup-is-very-slow-tf3349208.html#a9327965 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: zero width space displayed in pdf file
Hi Andreas L Delmelle napisał(a): On Mar 5, 2007, at 17:39, lecki wrote: Are you using an explicit XML metrics file? If so, check whether an element like bf us=8203.../ exists in the metrics file. If present, try removing it manually. Not sure if that will solve the problem, but give it a try anyway... First i have generated metrics file and then i have registered in configuration file. In my metrics file there is no element bf us=8203.../ i have found only bf gi=8203 ... / but removing doesn't help. btw how i cant wrap the text when font doesn't support zwsp e.g. Tahoma? Can you elaborate a bit on this? In my text i have got long words and sometimes they overflow the paper. In faq i have found an advise to insert zero width spaces (U+200B or #x200B;) to allow FOP to wrap. So how i can allow fop to wrap long words without using zero width spaces. Cheers, lukasz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: print to none default printer
liam grimes wrote: Hi its me again. Sorry guys no luck with changing the default printer thing. I found the easy why is to render it to postscript and chuck it in an outputstream. Now I got a different of topic easy question. How do you turn your layout to landscape of the xsl.? You need to change your fo:simple-page-master element. The attributes page-width and page-height should be set to the dimensions of a landscape page. If you are printing on A4 paper thats: page-width=297mm page-height=210mm Chris snip/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: impact of daylight saving time changes in USA on FOP
Desai, Sandeep wrote: Hi, I want to know whether FOP 0.20.3 has any impact of daylight saving time changes in USA. Not sure what you mean. FOP doesn't automatically adjust any dates or times in the XSL-FO. It certainly doesn't alter anything in the environment when it is running either. Perhaps you could elaborate a little. BTW, FOP 0.20.3 is over 5 years old now. Please consider upgrading to the far superior v0.93. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pdf meta information
Hello, I'm trying to add meta information to my PDF output. I'm using docbook, but since it seems like it is specific to the fo processor, I have to do some manual work to achieve this. Is it possible to add meta information to a PDF? Things like version, comment, author etc.. I'm using FOP 0.93. Thanks Hinrich
Re: zero width space displayed in pdf file
On Mar 6, 2007, at 10:47, lecki wrote: snip / First i have generated metrics file and then i have registered in configuration file. In my metrics file there is no element bf us=8203.../ i have found only bf gi=8203 ... / but removing doesn't help. OK, my bad. It should be a bf element with @us = 8203 and @ue = 8203... The gi attribute has nothing to do with the unicode-codepoint. It refers to the glyph-index. The us and ue attributes are unicode-start and unicode-end, bounding a range of codepoints. (Notice that a font like Verdana has the range 32 to 126 mapped to the same gi.) The actual glyph-index for a ZWSP would resolve to something like: @gi + 8203 - @us which, if I interpret correctly, should give you the index/position of the corresponding wx element, a bit further on the file. snip / In my text i have got long words and sometimes they overflow the paper. In faq i have found an advise to insert zero width spaces (U +200B or #x200B;) to allow FOP to wrap. So how i can allow fop to wrap long words without using zero width spaces. Right, now I see what you mean. Indeed, if I'm correct then FOP does not perform forced breaking of words upon overflow (as in wrap-option=wrap). Currently, with FOP Trunk, the situation is such that if hyphenation is turned off, the content will /never/ be broken in the middle of a word, unless there is an explicit Unicode codepoint that allows breaking (such as ZWSP or SHY) FOP 0.93 still lacks the Unicode linebreaking algorithm, but I thought ZWSP was functioning correctly and did generate a break- possibility, regardless of whether the font contains a glyph for it... The only workaround that immediately enters my head is to use hyphenation, and use a ZWSP, not in the words themselves, but to suppress the hyphenation character: fo:block hyphenate=true hyphenation-character=#x200B; YourVeryLongWordWillBeHyphenatedIfItDoesNotFit ... Mind that you will need hyphenation pattern files in case you want to try this. These are not distributed with FOP, but can be found at OFFO. Read all about configuring hyphenation in FOP here: http://xmlgraphics.apache.org/fop/0.93/hyphenation.html HTH! Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] pdf meta information
Hi, For metadata, you can find informations at this page : http://wiki.apache.org/xmlgraphics-fop/HowTo/XMP http://wiki.apache.org/xmlgraphics-fop/HowTo/XMP I have tested on my pdf files created with FOP Trunk and it works fine for Author, title, subject, keyword and application meta data. In acrobat reader 8, the subject is also in the keyword zone. It is a bug, I don't know. In acrobat reader 7, that's OK. I don't know the way to add permission for comments in a pdf file. Try pdftk ? Hugues. Hinrich Aue-2 wrote: Hello, I'm trying to add meta information to my PDF output. I'm using docbook, but since it seems like it is specific to the fo processor, I have to do some manual work to achieve this. Is it possible to add meta information to a PDF? Things like version, comment, author etc.. I'm using FOP 0.93. Thanks Hinrich -- View this message in context: http://www.nabble.com/pdf-meta-information-tf3355402.html#a9335693 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XPath version
What version of XPath is used in FOP 0.93 when parsing through an XSLT-FO file? Is there a way to control the XPath version being used? I'm trying to use: xsl:if test=upper-case( ../NAME ) = quot;SITE NAMEquot; But I get the error: SystemId Unknown; Line #27; Column #73; Could not find function: upper-case SystemId Unknown; Line #27; Column #73; function token not found. (Location of error unknown)java.lang.NullPointerException Mar 6, 2007 1:18:31 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:160) at org.apache.fop.cli.Main.main(Main.java:191) I'm using FOP 0.93, and am converting XML to PDF through XSLT: .\fop-0.93\Fop.bat -xml upper-case_test.xml -xsl upper-case_test.xslt -pdf upper-case_test.pdf Thanks! Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XPath version
Jeff Vannest wrote: What version of XPath is used in FOP 0.93 when parsing through an XSLT-FO file? Is there a way to control the XPath version being used? I'm trying to use: xsl:if test=upper-case( ../NAME ) = quot;SITE NAMEquot; I don't know whether you can control what XSLT/XPath processor is being used, but if you want to control the version, you can do so in the XSLT header. There is no way to control an XPath version, as a simple rule of the standard states that XSLT 2.0 is always chained with XPath 2.0 and XSLT 1.0 with XPath 1.0 (not vice versa, XPath can also be used stand alone). Changing the version won't have any effect, because FOP uses, if you specify an XSLT file, an XSLT 1.0 processor. XSLT-FO does not exist. I think you meant an XSLT stylesheet that, with some input file, will result in an XSL-FO file, which in turn will be processed by FOP. If you want to use upper-case() and don't want to use the obvious and ugly translate() hack you need for XSLT 1.0, you should consider XSLT 2. Processors that support XSLT 2.0 (and as a result must process XPath 2.0) are Saxon 8 (.Net and Java), Gestalt (standalone and Eiffel), AltovaXML (only standalone, free, no source). Only the first is by most people considered both stable, fast and compliant. Gestalt is getting closer, AltovaXML still has a long way to go, but does claim compliancy. If you go that path, I suggest you split your process in two steps. This can be done from a windows batch file, or any other means of course. First step: process your input XML with XSLT, second step: process the resulting XSL-FO(s). With time, you will probably find this way more convenient and more versatile (I did). Cheers, -- Abel Braaksma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XPath version
On Mar 6, 2007, at 19:51, Abel Braaksma wrote: Hi, Jeff Vannest wrote: What version of XPath is used in FOP 0.93 when parsing through an XSLT-FO file? Is there a way to control the XPath version being used? I'm trying to use: xsl:if test=upper-case( ../NAME ) = quot;SITE NAMEquot; snip / In addition to Abel's fine explanation, note that to make FOP work with Saxon, you can also do this in one of the following ways: Add saxon8.jar to your classpath, and a) modify (or create) /$JAVA_HOME$/lib/jaxp.properties add: javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryIm pl b) modify fop.bat, and change the final line to: %JAVACMD% - Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryI mpl ... a) will make any Java application that uses the JAXP API use Saxon. b) will do the same, but only when you run FOP. HTH! Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XPath version
On Mar 6, 2007, at 20:54, Jeff Vannest wrote: If you go that path, I suggest you split your process in two steps. Okay, I understand. I assumed that XPath 1.0 came along for the ride with XSLT 1.0, but I wanted to make certain. If you go that path, I suggest you split your process in two steps. I'm working with an embedded application, so Saxon sounds like the way to go. Unfortunately, I just don't have time for that additional work in my development timeline. Well, in that case, see my mail previous mail. Either change the TransformerFactory implementation for *all* Java applications using JAXP (including FOP), or IIC, it should also work if you set the related Java System property programmatically, before calling upon the TransformerFactory in the embedding application: System.setProperty(javax.xml.transform.TransformerFactory, net.sf.saxon.TransformerFactoryImpl); Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Writing to a file
Hi everyone, Im trying to figure out if it is possible to write som variable/text to a file and append the file if needed. Do anyone have a soloution for this? regards Johan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
