font-family and font names list
Hello there! I'm trying the following object in fop 0.20.3: fo:inline font-style=italic font-family=Arial, Helvetica, Geneva font-size=11.0ptTuesday, Mar. 5, 2002 12:33/fo:inline And got error message: [ERROR]: unknown font Arial, Helvetica, Geneva,normal,normal so defaulted font to any [ERROR]: defaulted font to any,normal,normal Is it a bug/unsupported feature or am I wrong with something here ? -- Oleg Tkachenko Multiconn International, Israel
Re: font-family and font names list
Oleg Tkachenko wrote: Hello there! I'm trying the following object in fop 0.20.3: fo:inline font-style=italic font-family=Arial, Helvetica, Geneva font-size=11.0ptTuesday, Mar. 5, 2002 12:33/fo:inline And got error message: [ERROR]: unknown font Arial, Helvetica, Geneva,normal,normal so defaulted font to any [ERROR]: defaulted font to any,normal,normal Is it a bug/unsupported feature or am I wrong with something here ? I remember a post which basically said that font lists are a last minute addendum to XSLFO imposed for CSS compatibility. I *hate* CSS for the havoc it wrecked on other otherwise quite sensible standards. The font list attribute introduces another language with a rather nontrivial grammar, which is incidentally incompatible with the expression language used for other properties. The parser in fop/expr doesn't obviously handle it, and i didn't find evidence that the font-family attribute is handled by another parser, the foproperties.xml declares this: property namefont-family/name inheritedtrue/inherited datatypeString/datatype defaultsans-serif/default /property So my guess is the feature is not implemented. :-( J.Pietschmann
RE: XSL Transformation
i am using 0.20.3.. If you have an example using a SaxSource and a StreamSource, that would be great.. i.e new Transformer(xsltStreamSource) trans.transform(xmlSaxSource, ???); -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: Friday, March 29, 2002 2:45 PM To: [EMAIL PROTECTED] Subject: Re: XSL Transformation Norr, Peter wrote: this did not work.. how does it render it without calling driver.run or driver.render(..)? The formatting process is driven through the transformation. You need at least FOP 0.20.2, in 0.20.1 the setup was a bit more complicated. HTH J.Pietschmann -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Re: Xerces compatibility question
Guillaume Mathe wrote: Now i have another question, this time about Xerces lib - with 1.2.3 i get : [ERROR]: Error in content-type property value 'content-type:image/jpg': org.apache.fop.fo.expr.PropertyException: illegal character for the following item: fo:external-graphic content-type=content-type:image/jpg width=150px height=34px src=hello.jpg / The exception is raised by FOP, not the XML parser. Try fo:external-graphic content-type=image/jpg .../ HTH J.Pietschmann
Re: font-family and font names list
Wayne Elliott wrote: Try putting sans-serif at the end ... font-family=Arial, Helvetica, Geneva, sans-serif [ERROR]: unknown font Arial, Helvetica, Geneva, sans-serif,italic,normal so defaulted font to any then try putting it at the beginning ... font-family= sans-serif, Arial, Helvetica, Geneva [ERROR]: unknown font sans-serif, Arial, Helvetica, Geneva,italic,normal so defaulted font to any then try ... font-family= sans-serif no error, it works. Well, it seems to me Mr. J.Pietschmann is right, fop gets it as string so font list is unsupported feature. -- Oleg Tkachenko Multiconn International, Israel
FO-API with RTF-Import
Hello, If you are looking for a Java-API that helps you generating formatting objects and imports from Rich Text Format visit us www.dig-dreams.de. There you can download an evaluation version of jFO. jFO can be used to create (small - middle) reports / documents, where creating XML and XSL is too expensive. The RTF-importer of jFO allows you filling rtf-fields with user-datas (which can be strings, fo:inline-elements or xsl-nodes). So you can design templates / forms with an RTF-Editor and jFO fills them during import. Kind regards, Sascha Schmidt.
Re: font-family and font names list
* Oleg Tkachenko; [EMAIL PROTECTED] on 01 Apr, 2002 wrote: Wayne Elliott wrote: [ERROR]: unknown font sans-serif, Arial, Helvetica, Geneva,italic,normal so defaulted font to any then try ... font-family= sans-serif no error, it works. Well, it seems to me Mr. J.Pietschmann is right, fop gets it as string so font list is unsupported feature. Sorry I may have missed the thread but if you use a onfiguration file and define the fonts and their names in it you can use these fonts, currently I am using truetype fonts by this method here is -- Togan Muftuoglu snipped from userconfig.xml !-- Add fonts here -- font metrics-file=ttfarial.xml kerning=yes embed-file=arial.ttf font-triplet name=Arial style=normal weight=normal/ font-triplet name=ArialMT style=normal weight=normal/ /font font metrics-file=ttfarialbd.xml kerning=yes embed-file=arialbd.ttf font-triplet name=Arial style=normal weight=bold/ font-triplet name=ArialMT style=normal weight=bold/ /font font metrics-file=ttfariali.xml kerning=yes embed-file=ariali.ttf font-triplet name=Arial style=italic weight=normal/ font-triplet name=ArialMT style=italic weight=normal/ /font font metrics-file=ttfarialbi.xml kerning=yes embed-file=arialbi.ttf font-triplet name=Arial style=italic weight=bold/ font-triplet name=ArialMT style=italic weight=bold/ /font font metrics-file=times.xml kerning=yes embed-file=times.ttf font-triplet name=TimesNewRoman style=normal weight=normal/ font-triplet name=Times Roman style=normal weight=normal/ /font font metrics-file=timesi.xml kerning=yes embed-file=timesi.ttf font-triplet name=TimesNewRoman style=italic weight=normal/ font-triplet name=Times Roman style=italic weight=normal/ /font font metrics-file=timesbd.xml kerning=yes embed-file=timesbd.ttf font-triplet name=TimesNewRoman style=normal weight=bold/ font-triplet name=Times Roman style=normal weight=bold/ /font font metrics-file=timesbi.xml kerning=yes embed-file=timesbi.ttf font-triplet name=TimesNewRoman style=italic weight=bold/ font-triplet name=Times Roman style=italic weight=bold/ /font /configuration --
fop configuration
Hello, I'm a new user of FOP 0.20.3 I would like to run my first sample simple.fo (set in docs\examples\fo) but unfortunately, it doesn't work. I guess it's a classpath problem because when I write the following instruction on the command line,the error message is: Exeptoin in thread "main" java.lang.NoClassDefFoundError: org:apache/log/format/Formatter at org.apache.fop.apps.Fop.main(Fop.java:16) belowis my complete classpath set: CLASSPATH=C:\tomcat\common\lib\servlet.jar;C:\xalan\bin\xalan.jar;C:\xalan\bin\xercesImpl.jar;C:\xalan\bin\xml-apis.jar;C:\xalan\bin\xalansamples.jar;C:\xalan\bin\xalanservlet.jar;c:\xalan\samples\ApplyXPath;C:\fop\build\fop.jar;C:\fop\lib\avalon-framework-4.0.jar;c:\fop\lib\xalanj1compat.jar;c:\fop\lib\batik.jar;c:\fop\lib\ant.jar Is something wrong? Is there any problem with xalan classes because I've installed Xalan too? Thanks a lot for your responses, Cyril.
Re: fop configuration
cyril vidal wrote: Exeptoin in thread main java.lang.NoClassDefFoundError: org:apache/log/format/Formatter You also have to include logkit-1.0.jar in the classpath. The file should be in the fop/lib directory. J.Pietschmann
About FOP 0.20.3
Hello ... I',m using FOP 0.20.3, the issue is when I try to my program send this messages ... [INFO]: FOP 0.20.3 [INFO]: building formatting object tree [ERROR]: ERROR: org.apache.fop.apps.FOPException: 'master-reference' for 'fo:page-sequence'matches no 'simple- page-master' or 'page-sequence-master' So, I've checked my XSL file and I think that it's fine ... What I need to check for fixing that ? Thanks. //jose.alberto.hernandez.maldonado System Integrator Engineer. Algorithmics Mexico. Tel. 5520-4293 Fax. 5520-4292 e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: About FOP 0.20.3
Jose Hernandez wrote: I',m using FOP 0.20.3, the issue is when I try to my program send this messages ... [INFO]: FOP 0.20.3 [INFO]: building formatting object tree [ERROR]: ERROR: org.apache.fop.apps.FOPException: 'master-reference' for 'fo:page-sequence'matches no 'simple- page-master' or 'page-sequence-master' Check again. FOP 0.20.3 catched up with a last minute change in the spec, the page master is referenced by the attribute master-reference rather than master-name. If you are actually using master-reference for referencing the page master, check for misspellings and whether you really defined the referenced page master. This is a FAQ. More about this can be found in the archive http://marc.theaimsgroup.com/?l=fop-userr=1w=2# and http://marc.theaimsgroup.com/?l=fop-devr=1w=2# J.Pietschmann
RE: When a page is not a page
Right. So, you'll end up with NaN, which is what I get when I attempted this before brain was engaged. -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: Sunday, March 31, 2002 5:40 AM To: [EMAIL PROTECTED] Subject: Re: When a page is not a page Matthew L. Avizinis wrote: Nope. Neither will work. Sorry. That's what I get for speaking b4 thinking. Where's the variable going to get it's value from? Certainly not from the fo:page-number instruction -- that's for the FOP processor to use not the XSLT processor. You'll get NaN. No. The value is an RTF with a fo:page-number element as its only node below the root. J.Pietschmann
Re: Xerces compatibility question
If the suggestion below works, it's not compatible with the spec, which allows two variants of content-type, e.g., content-type=content-type:xml/svg or content-type=namespace-prefix:svg (See 7.28.1) We can't even blame CSS for this one. Peter J.Pietschmann wrote: Guillaume Mathe wrote: Now i have another question, this time about Xerces lib - with 1.2.3 i get : [ERROR]: Error in content-type property value 'content-type:image/jpg': org.apache.fop.fo.expr.PropertyException: illegal character for the following item: fo:external-graphic content-type=content-type:image/jpg width=150px height=34px src=hello.jpg / The exception is raised by FOP, not the XML parser. Try fo:external-graphic content-type=image/jpg .../
RE: possible to specify required spaces?
This is a great subject. I recently struggled quite a bit with this problem. RTF2FO and FO to FOP gave me loads of problems with whitespaces. I am ready to give up. - sb -Original Message- From: Craeg K Strong [mailto:[EMAIL PROTECTED] Sent: Friday, March 22, 2002 1:45 PM To: [EMAIL PROTECTED] Subject: Re: possible to specify required spaces? Can you use fo:leader? Check out http://www.renderx.com/Tests/leader.fo HTH, --Craeg [EMAIL PROTECTED] wrote: Does anyone know a way to pass required spaces through FOP from XML to a PDF? The normal processing of x'20' spaces collapses adjacent spaces to eliminate extra white space, which is normally good but not in all cases, and 'white-space-treatment=pre' (which would preserve these) isn't implemented yet. Does anyone know, for example, of another way to preserve these or else another blank non-printing character that we could use in the XML file for spaces we want to preserve? Thanks for any advice! -- Craeg K Strong, General Partner Ariel Partners LLC http://www.arielpartners.com voice 781-647-2425 fax 781-647-9690 NOTICE: This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. 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. If you are not the intended recipient, please contact the sender by reply email and destroy all copies -- including electronic copies -- of the original message.
RE: possible to specify required spaces?
I use fo:block white-space-collapse=false which preserves spaces and works great with FOP. Scott -Original Message- From: Buonincontri, Steve (CAP, MMF, ITSS) [mailto:[EMAIL PROTECTED] Sent: Monday, April 01, 2002 5:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: possible to specify required spaces? This is a great subject. I recently struggled quite a bit with this problem. RTF2FO and FO to FOP gave me loads of problems with whitespaces. I am ready to give up. - sb -Original Message- From: Craeg K Strong [mailto:[EMAIL PROTECTED] Sent: Friday, March 22, 2002 1:45 PM To: [EMAIL PROTECTED] Subject: Re: possible to specify required spaces? Can you use fo:leader? Check out http://www.renderx.com/Tests/leader.fo HTH, --Craeg [EMAIL PROTECTED] wrote: Does anyone know a way to pass required spaces through FOP from XML to a PDF? The normal processing of x'20' spaces collapses adjacent spaces to eliminate extra white space, which is normally good but not in all cases, and 'white-space-treatment=pre' (which would preserve these) isn't implemented yet. Does anyone know, for example, of another way to preserve these or else another blank non-printing character that we could use in the XML file for spaces we want to preserve? Thanks for any advice! -- Craeg K Strong, General Partner Ariel Partners LLC http://www.arielpartners.com voice 781-647-2425 fax 781-647-9690 NOTICE: This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. 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. If you are not the intended recipient, please contact the sender by reply email and destroy all copies -- including electronic copies -- of the original message.
