RE: FOP and different XERCES versions
Thank you very much for the quick answer. I've downloaded the latest fop 0.20.5, put the fop.jar, xalan.jar, xercesImpl.jar and xml-apis.jar in my ant's lib directory and generated a set of reference pdf using the build file from the examples\fo directory. After this I've changed in the xalan and xerces version's from the ant's lib to xalan 2.5.1 and xerces 2.4.0. I generated the pdfs again using the same build file. These pdf proved to be identical to the reference pdfs (binary diff). I would conclude from here that the combination: - fop 0.20.5 - xerces 2.4.0 - xalan 2.5.1 works. As for my own safety I've also built my own pdfs and they were generated correctly. cheers, Artur - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Font-metrics file
Title: Font-metrics file Folks: This may sound like an unusual question, but Why is the font metrics file needed/used by FOP. What does it provide to FOP. I have been using it blindly for the last year, just wondering. Thanks in advance Rob
Re: Font-metrics file
The metric file contains information about a font such as its name and is bounding box. The fact that we use such a special file has historical reasons, mostly. A long time ago, the only way to make a font work in FOP was to create such a file by hand (or to create a font class like Helvetica.java which even today is generated using XSLT). After that there was the PFMReader which took a Type 1 PFM file to generate that file which improved the whole thing a lot, not to mention the ability to add fonts without recompiling FOP. :-) Sure, that XML font metric file is not really necessary, but especially for Type 1 fonts it may be an important thing to have because the PFM file does not provide all the needed values. The missing ones can be found in the PFA or PFB file. But we don't have parsers for these two, yet. I often had to manually patch the generated XML font metrics. I think this was also necessary for certain TrueType fonts. Another point may be speed. Especially for the TrueType fonts it could be that reading the XML file is faster than interpreting the TrueType font. But there are ways around that. At any rate, the need for the XML font metric files will go away, eventually. Help is, as always, highly welcome. Folks: This may sound like an unusual question, but Why is the font metrics file needed/used by FOP. What does it provide to FOP. I have been using it blindly for the last year, just wondering. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Font-metrics file
Title: RE: Font-metrics file Thanks, excellent explanation as usual. I have found a tool that converts a PFB to a PFM. If the newly created PFM file has the missing values will they be picked up by the PFM parser? That question maybe out in left field, we can take it off-line if you want. Rob -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Friday, October 03, 2003 12:43 PM To: [EMAIL PROTECTED] Subject: Re: Font-metrics file The metric file contains information about a font such as its name and is bounding box. The fact that we use such a special file has historical reasons, mostly. A long time ago, the only way to make a font work in FOP was to create such a file by hand (or to create a font class like Helvetica.java which even today is generated using XSLT). After that there was the PFMReader which took a Type 1 PFM file to generate that file which improved the whole thing a lot, not to mention the ability to add fonts without recompiling FOP. :-) Sure, that XML font metric file is not really necessary, but especially for Type 1 fonts it may be an important thing to have because the PFM file does not provide all the needed values. The missing ones can be found in the PFA or PFB file. But we don't have parsers for these two, yet. I often had to manually patch the generated XML font metrics. I think this was also necessary for certain TrueType fonts. Another point may be speed. Especially for the TrueType fonts it could be that reading the XML file is faster than interpreting the TrueType font. But there are ways around that. At any rate, the need for the XML font metric files will go away, eventually. Help is, as always, highly welcome. Folks: This may sound like an unusual question, but Why is the font metrics file needed/used by FOP. What does it provide to FOP. I have been using it blindly for the last year, just wondering. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font-metrics file
Well, the discussion would be better suited for fop-dev, not fop-user, but please let's NOT hold it off-line. Your idea, unfortunately, doesn't work. The PFM file by specification does not contain all the necessary values. The PFB alone would probably be enough, to make it work (GhostScript proves that), but the PFM alone doesn't help. It's probably a one-day job to write the code for a PFB parser. I simply don't have enough time lately and/or a big-enough itch for that matter. On 03.10.2003 18:20:41 Rob Stote wrote: I have found a tool that converts a PFB to a PFM. If the newly created PFM file has the missing values will they be picked up by the PFM parser? That question maybe out in left field, we can take it off-line if you want. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Converting to uppercaseusing text-transform
Hi, I am using the text-transform property to convert some content to uppercase if an attribute has a specif value. I tried using font-variant=small-caps but it doesnt give me the desired results. I looked through the FOP documentation and it says that the text-transform property is NOT yet implemented in FOP. I am wondering if there is any chance that this will be implemented in FOP and if yes how long would it take. I tried writing a template to convert to capital letters but it doesnt work the way I need coz I am setting the attribute in the parent and I need its children to inherit it irrespective of the level of depth. Hence I cant pass a specific string to the conversion template. If anyone has suggestion then will really appreciate them. Thanks, Abhi __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting to uppercaseusing text-transform
Abhijit Junnare wrote: Hi, I am using the text-transform property to convert some content to uppercase if an attribute has a specif value. I tried using font-variant=small-caps but it doesnt give me the desired results. I looked through the FOP documentation and it says that the text-transform property is NOT yet implemented in FOP. I am wondering if there is any chance that this will be implemented in FOP and if yes how long would it take. According to the FOP Compliance page (watch wrap): http://xml.apache.org/fop/compliance.html#fo-property-text-transform There is basic support for text-transform, but extended support is not available. I clicked on the §7.16.6 link: http://www.w3.org/TR/xsl/slice7.html#text-transform and according to that page, the proper usage would be: text-transform=uppercase Are you saying this doesn't work? If you are trying to do it based on an attributes value, you could try: xsl:choose !-- ATTRIBUTE EXISTS -- xsl:when test=XPATH/TO/@[.='Y'] xsl:attribute name=text-transformuppercase/xsl:attribute /xsl:when !-- ATTRIBUTE DOES NOT EXIST -- xsl:otherwise xsl:attribute name=text-transformnone/xsl:attribute /xsl:otherwise /xsl:choose I tried writing a template to convert to capital letters but it doesnt work the way I need coz I am setting the attribute in the parent and I need its children to inherit it irrespective of the level of depth. Hence I cant pass a specific string to the conversion template. For the children, you might need them wrapped with text-transform=inherit (...although I would think it would automatically inherit...) If anyone has suggestion then will really appreciate them. Thanks, Abhi HTH! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting to uppercaseusing text-transform
Below is the output I get on the screen. As you can see it says not yet implemented. I believe I am using the latest version. Do let me know if I am doing something wrong. Thanks, Abhi C:\Abhi\fop-0.20.5fop -c lib\conf\userconfig.xml -xml xml\CancellationNotice.xm l -xsl xml\ExpereStandard_New.xsl -pdf xml\CancellationNotice1.pdf [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] FOP 0.20.5 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [ERROR] property - text-transform is not implemented yet. [ERROR] property - text-transform is not implemented yet. [ERROR] property - text-transform is not implemented yet. [ERROR] property - text-transform is not implemented yet. [ERROR] property - text-transform is not implemented yet. [INFO] [1] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on ta ble. [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on ta ble. [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] area contents overflows area in line [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] [2] [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] area contents overflows area in line [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] [3] [WARNING] table-layout=auto is not supported, using fixed! [ERROR] At least one of minimum, optimum, or maximum IPD must be specified on ta ble. [INFO] Parsing of document complete, stopping renderer --- Clay Leeds [EMAIL PROTECTED] wrote: Abhijit Junnare wrote: Hi, I am using the text-transform property to convert some content to uppercase if an attribute has a specif value. I tried using font-variant=small-caps but it doesnt give me the desired results. I looked through the FOP documentation and it says that the text-transform property is NOT yet implemented in FOP. I am wondering if there is any chance that this will be implemented in FOP and if yes how long would it take. According to the FOP Compliance page (watch wrap): http://xml.apache.org/fop/compliance.html#fo-property-text-transform There is basic support for text-transform, but extended support is not available. I clicked on the §7.16.6 link: http://www.w3.org/TR/xsl/slice7.html#text-transform and according to that page, the proper usage would be: text-transform=uppercase Are you saying this doesn't work? If you are trying to do it based on an attributes value, you could try: xsl:choose !-- ATTRIBUTE EXISTS -- xsl:when test=XPATH/TO/@[.='Y'] xsl:attribute name=text-transformuppercase/xsl:attribute /xsl:when !-- ATTRIBUTE DOES NOT EXIST -- xsl:otherwise xsl:attribute name=text-transformnone/xsl:attribute /xsl:otherwise /xsl:choose I tried writing a template to convert to capital letters but it doesnt work the way I need coz I am setting the attribute in the parent and I need its children to inherit it irrespective of the level of depth. Hence I cant pass a specific string to the conversion template. For the children, you might need them wrapped with text-transform=inherit (...although I would think it would automatically inherit...) If anyone has suggestion then will really appreciate them. Thanks, Abhi HTH! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting to uppercaseusing text-transform
Abhijit Junnare wrote: I looked through the FOP documentation and it says that the text-transform property is NOT yet implemented in FOP. I am wondering if there is any chance that this will be implemented in FOP and if yes how long would it take. The spec itself recommends against using this feature. Uppercasing arbitrary Unicode letters is a quite non-trivial task. I tried writing a template to convert to capital letters but it doesnt work the way I need coz I am setting the attribute in the parent and I need its children to inherit it irrespective of the level of depth. Hence I cant pass a specific string to the conversion template. Ouch! Pass a mode or a parameter to templates applying to the child element, and do a translate(.,$lower,$upper) in th ecorrespondinggly moded template matching text(), or if the text() template senses the parameter. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
