Using Saxon transformer together with Xalan and XSLTC
Hi, I try to use Saxon 7.6 together with Xalan There is the following warning in the logs when I try to place saxon.jar to WEB-INF/lib: Date: Mon Jun 30 14:01:53 EEST 2003 (1056970913164) Thread: PoolThread-4 Message #: 1 Level: WARN NDC: Category: sitemap.serializer.xhtml Message:Cannot know if transformer needs namespaces attributes - assuming NO. Location: org.apache.avalon.framework.logger.LogKitLogger.warn(LogKitLogger.java:159) Thrown: org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of each element at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:170) at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:128) at org.apache.cocoon.serialization.AbstractTextSerializer.needsNamespacesAsAttributes(AbstractTextSerializer.java:341) at org.apache.cocoon.serialization.AbstractTextSerializer.configure(AbstractTextSerializer.java:268) at org.apache.cocoon.serialization.XMLSerializer.configure(XMLSerializer.java:76) ... The result is the HTML and XHTML serializers work properly only after Saxon transformer. They work incorrectly after XSLT and Xalan transformers (f.e. the attribute href isn't generated, although as far as I've found the xml-s after all transformers are the same). My emviroment is Win2000, jdk1.4.1_02, Jetty4.2.9, Cocoon2.1m3-dev -- Best regards, Peter mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Saxon transformer together with Xalan and XSLTC
Hi, PV I try to use Saxon 7.6 together with Xalan PV There is the following warning in the logs when I try to place PV saxon.jar to WEB-INF/lib: PV Date: Mon Jun 30 14:01:53 EEST 2003 (1056970913164) PV Thread: PoolThread-4 PV Message #: 1 PV Level: WARN PV NDC: PV Category: sitemap.serializer.xhtml PV Message:Cannot know if transformer needs namespaces attributes - assuming NO. PV Location: org.apache.avalon.framework.logger.LogKitLogger.warn(LogKitLogger.java:159) PV Thrown: PV org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of each element PV at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:170) PV at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:128) PV at org.apache.cocoon.serialization.AbstractTextSerializer.needsNamespacesAsAttributes(AbstractTextSerializer.java:341) PV at org.apache.cocoon.serialization.AbstractTextSerializer.configure(AbstractTextSerializer.java:268) PV at org.apache.cocoon.serialization.XMLSerializer.configure(XMLSerializer.java:76) PV ... PV The result is the HTML and XHTML serializers work properly only after PV Saxon transformer. They work incorrectly after XSLT and Xalan PV transformers (f.e. the attribute href isn't generated, although as PV far as I've found the xml-s after all transformers are the same). My apologies, but the same is the input xml. The output xml-s are different: for Saxon - ?xml version=1.0 encoding=UTF-8? html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head titleSamples/title meta http-equiv=Content-Type content=text/xhtml; charset=UTF-8/ link href=/styles/main.css type=text/css rel=stylesheet/ /head body h1List/h1 p xmlns= class=block2 Sample 1 - a href=examples/linotype/view/a /p p xmlns= class=block2 Sample 2 - a href=examples/charts/view/a /p /body /html for Xalan - ?xml version=1.0 encoding=UTF-8? html xmlns=http://www.w3.org/1999/xhtml; head xmlns=http://www.w3.org/1999/xhtml; title xmlns=http://www.w3.org/1999/xhtml;Samples/title meta xmlns=http://www.w3.org/1999/xhtml/ link xmlns=http://www.w3.org/1999/xhtml/ /head body xmlns=http://www.w3.org/1999/xhtml; h1 xmlns=http://www.w3.org/1999/xhtml;List/h1 p xmlns=http://www.w3.org/1999/xhtml; xmlns= Sample 1 - a xmlns=http://www.w3.org/1999/xhtml; xmlns=view/a /p p xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns= Sample 2 - a xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns=view/a /p /body /html So there is duplicating xmlns attributes in XML generated by Xalan. PV My emviroment is Win2000, jdk1.4.1_02, Jetty4.2.9, Cocoon2.1m3-dev -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLFORM and Cirilic encoding
Hello Galia, Try to set the form encoding. It is in the web.xml file: init-param param-nameform-encoding/param-name param-valueutf-8/param-value /init-param Simply incomment it for cocoon 2.1. GA Hello, GA I have a problem with Cirilic encoding when working with xmlforms. Everything is ok exept when I submit a cirilic text in a textbox: GA I write: GA and on the server it appears like: #208;#208;?#208;?#209;#143; GA In select or labels the text appears as cirilic. But in textboxes and textareas - not. GA Any idea? GA Thanks GA Galia GA - GA Do you Yahoo!? GA SBC Yahoo! DSL - Now only $29.95 per month! -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[2]: CSS in Cocoon
Hello, Monday, June 9, 2003, 11:46:57 PM, you wrote: TB So if I replaced the dialog.xsl to read: TB headxsl:param name= css-stylesheet select=global.css'/ TB xsl:param name=css-stylesheettext/css/xsl:param TB Assuming the sitemap has not changed, it should work? TB It does not. ??? You may try to use xsl:param name=html.stylesheet select='global.css'/ In your sample there is only closing quotation mark as a default value of the xsl:param / that is incorrect. TB -Original Message- TB From: Conal Tuohy [mailto:[EMAIL PROTECTED] TB Sent: Monday, June 09, 2003 3:41 PM TB To: [EMAIL PROTECTED] TB Subject: RE: CSS in Cocoon TB Tim, presumably dialog.xsl is supposed to insert a link element into TB the html, pointing at the stylesheet which is passed as a parameter? TB But the dialog.xsl appears to expect a parameter called TB html.stylesheet, whereas the parameter you are actually passing it TB (from the sitemap) is called css-stylesheet. TB Cheers! TB Con -Original Message- From: Tim Bachta [mailto:[EMAIL PROTECTED] Sent: Tuesday, 10 June 2003 08:19 To: [EMAIL PROTECTED] Subject: CSS in Cocoon I am trying to use a stylesheet in a xsl page and am getting a null pointer exception coming from my xsl page. My syntax is below, I am new to Cocoon so please excuse my mistakes. I appreciate the help. dialog.xsl xsl:param name=html.stylesheet select=global.css'/ xsl:param name=html.stylesheet.typetext/css/xsl:param sitemap map:match pattern=login map:generate type=serverpages src=xsp/login.xsp/ map:transform type=xslt src=style/dialog.xsl map:parameter name=css-stylesheet value=global.css/ /map:transform map:serialize type=html/ /map:match map:match pattern=global.css map:read src=global.css mime-type=text/css/ /map:match Thank you Tim B - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] TB - TB To unsubscribe, e-mail: [EMAIL PROTECTED] TB For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[2]: FOP/HSSFSerializer's and non-english characters
Wednesday, May 28, 2003, 8:08:47 AM, you wrote: YM On Tue, 27 May 2003 11:44:48 +0400 YM Yury Mikhienko [EMAIL PROTECTED] wrote: On Mon, 26 May 2003 21:35:18 +0200 J.Pietschmann [EMAIL PROTECTED] wrote: Yury Mikhienko wrote: Cocoon's FOP/HSSFSerializer still does not support non-english characters, can I solve this problem? I don't know about the HSSFSerializer, but the PDFSerializer does not have problems with non-ASCII characters. You'll have to install appropriate fonts though, refer to http://xml.apache.org/fop/faq.html#pdf-characters and http://xml.apache.org/fop/faq.html#pdf-characters Check the Cocoon docs for how to supply a user configuration with user fonts to the PDF serializer. If this still doesn't solve your problem, you'll have to supply more details. Thank you, will try. YM Ok, the PDF serializer works properly (but with .ttf fonts only), but what about the HSSFSerializer? YM I still does not properly generate the exel document with russian characters :(( There is the jakarta-poi-1.7.0-dev-20020624.jar library in the cocoon-2.1/src/blocks/poi/lib. It does not support russian characters. The support begins from version 1.8-dev. See http://jakarta.apache.org/poi/changes.html#1.8-dev; The current version of POI is 2.0-pre1. -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
