Re: [ANN] XSLfast: Authoring tool for XSL-FO
On Friday 12 October 2001 23:14, Stephan Albers wrote: after a long development period, we have finaly released the very first version of XSLfast for public review and test. Interesting, thanks for the info! How is XSLfast licensed? Open Source? Commercial? -- -- Bertrand Delacrétaz, www.codeconsult.ch -- web technologies consultant - OO, Java, XML, C++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Embedding Printer Control parameters in PCL
On Brian T. Wolf wrote: We are working on that as well, though I don't have any good solutions yet either. If you run across something please let me know. Just as an FYI, I tried hardcoding a duplex print escape sequence into PCLRenderer.java and it printed both sides as expected. So I figure once we solve how to pass through the landscape code, this should be resolved as well. There is more to this than a FOP coding issue I believe however. The xsl:fo standard has nothing to do with how a particular printer should behave. So we also need to figure out how to get the information from the stylesheet to the renderer without damaging the integrity of the xsl. Regards, Brian - Original Message - From: Raj [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 12, 2001 7:45 AM Subject: Embedding Printer Control parameters in PCL Hi Art, I am trying to send fop generated PCL from web server to network printers. For each document, we know the print controls(like duplex etc.) Is there a way to embed these controls as part of the PCL stream so that duplex prints are automatically delivered as duplex without any other intervention. All our printers support duplex printing. Thanks -rajendran. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Embedding Printer Control parameters in PCL
On -MM-ddT Brian T. Wolf wrote: We are working on that as well, though I don't have any good solutions yet either. If you run across something please let me know. Just as an FYI, I tried hardcoding a duplex print escape sequence into PCLRenderer.java and it printed both sides as expected. So I figure once we solve how to pass through the landscape code, this should be resolved as well. There is more to this than a FOP coding issue I believe however. The xsl:fo standard has nothing to do with how a particular printer should behave. So we also need to figure out how to get the information from the stylesheet to the renderer without damaging the integrity of the xsl. Regards, Brian - Original Message - From: Raj [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 12, 2001 7:45 AM Subject: Embedding Printer Control parameters in PCL Hi Art, I am trying to send fop generated PCL from web server to network printers. For each document, we know the print controls(like duplex etc.) Is there a way to embed these controls as part of the PCL stream so that duplex prints are automatically delivered as duplex without any other intervention. All our printers support duplex printing. Thanks -rajendran. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Embedding Printer Control parameters in PCL
On -MM-ddT Brian T. Wolf wrote: We are working on that as well, though I don't have any good solutions yet either. If you run across something please let me know. Just as an FYI, I tried hardcoding a duplex print escape sequence into PCLRenderer.java and it printed both sides as expected. So I figure once we solve how to pass through the landscape code, this should be resolved as well. There is more to this than a FOP coding issue I believe however. The xsl:fo standard has nothing to do with how a particular printer should behave. So we also need to figure out how to get the information from the stylesheet to the renderer without damaging the integrity of the xsl. Regards, Brian - Original Message - From: Raj [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 12, 2001 7:45 AM Subject: Embedding Printer Control parameters in PCL Hi Art, I am trying to send fop generated PCL from web server to network printers. For each document, we know the print controls(like duplex etc.) Is there a way to embed these controls as part of the PCL stream so that duplex prints are automatically delivered as duplex without any other intervention. All our printers support duplex printing. Thanks -rajendran. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Embedding Printer Control parameters in PCL
That's also going to be an issue for the PostScript renderer, when we want to apply individual PPDs (Files that contain control commands for individual printers) or controlling the PostScript Level to be used. What comes to my mind as an idea is a FOP extension where we can supply some configuration in form of a (sub-)element tree that gets converted internally into Avalon Configuration objects that can be used to configure a particular renderer. On the other side, this mechanism should only complement (not replace) the configuration possibilities from the system/user configuration supplied to FOP. I think it's also important that the extension can take configuration for several renderers simultaneously. On 12.10.2001 19:52:37 Brian T. Wolf wrote: We are working on that as well, though I don't have any good solutions yet either. If you run across something please let me know. Just as an FYI, I tried hardcoding a duplex print escape sequence into PCLRenderer.java and it printed both sides as expected. So I figure once we solve how to pass through the landscape code, this should be resolved as well. There is more to this than a FOP coding issue I believe however. The xsl:fo standard has nothing to do with how a particular printer should behave. So we also need to figure out how to get the information from the stylesheet to the renderer without damaging the integrity of the xsl. Regards, Brian - Original Message - From: Raj [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 12, 2001 7:45 AM Subject: Embedding Printer Control parameters in PCL Hi Art, I am trying to send fop generated PCL from web server to network printers. For each document, we know the print controls(like duplex etc.) Is there a way to embed these controls as part of the PCL stream so that duplex prints are automatically delivered as duplex without any other intervention. All our printers support duplex printing. Thanks -rajendran. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Polluting the list
I'm really sorry for having polluted the list with several empty answers. I was fiddling around with my mail client and... I still seem to be asleep. Sorry! Regards, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - Fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2001-10-13/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan1: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 0.20.1 [1999-2001] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 35 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/allprops.xml [xslt] style: ./build/src/codegen/genconst.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/Constants.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/foproperties.xml [xslt] style: ./build/src/codegen/properties.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/fo_ignore_this.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/foproperties.xml [xslt] style: ./build/src/codegen/propmap.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/foproperties.xml [xslt] style: ./build/src/codegen/enumgen.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/foenums_ignore_this.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/extproperties.xml [xslt] style: ./build/src/codegen/properties.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/ext_ignore_this.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/extproperties.xml [xslt] style: ./build/src/codegen/propmap.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/ExtensionPropertyMapping.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/extproperties.xml [xslt] style: ./build/src/codegen/enumgen.xsl [xslt] out: ./build/src/org/apache/fop/fo/properties/extenums_ignore_this.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/charlist.xml [xslt] style: ./build/src/codegen/code-point-mapping.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/CodePointMapping.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/Courier.xml [xslt] style: ./build/src/codegen/font-file.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Courier.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/Courier-Oblique.xml [xslt] style: ./build/src/codegen/font-file.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/Courier-Bold.xml [xslt] style: ./build/src/codegen/font-file.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/Courier-BoldOblique.xml [xslt] style: ./build/src/codegen/font-file.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [xslt] [xslt] [xslt] xslt [xslt] in: ./build/src/codegen/Helvetica.xml [xslt] style: ./build/src/codegen/font-file.xsl [xslt] out: ./build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [xslt] [xslt] [xslt] xslt [xslt] in:
[ANn] XSLfast at SYSTEMS exhibition, Munich
Dear subscribers, XSLfast will be presented at the SYSTEMS exhibition in Munich, Germany. You find XSLfast from Oct, 15-19 2001 in Hall B2, Stand 442 at jCatalog Software AG *** *** *** *** *** *** XSLfast is the first graphical editor for authoring XSL-FO *** *** *** *** *** *** For more information about XSLfast and downloading an evalution version, please check: http://www.xslfast.com Best Regards Stephan Albers jCatalog Software AG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
