Re: [C2] Encoding value with I18n
I have tried this too, and it also doesn't work. Thanks for your help - Original Message - From: Piroumian, Konstantin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 7:16 PM Subject: Re: [C2] Encoding value with I18n I am not sure that the problem is with i18n but I'll take a look at it. I'm not sure, but maybe result encoding must be specified in the Serializer? Something like: map:serialize type=xml map:parameter name=encodingiso-8859-1/map:parameter /map:serialize I will investigate this problem and let you know if I find something. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 8:42 PM Subject: Re: [C2] Encoding value with I18n Thanks I'm working on C2.0b1 I understand that all the transformers work the same way, but it seems that i18n does not. The sitemap is as follow (in fact it's a sub/sitemap): map:match pattern=ManUser.xsli map:generate type=file src=ManUser.xsl/ map:transform type=i18n map:parameter name=src value=lang/ManUser.xml/ /map:transform map:serialize type=xml/ /map:match ManUser.xsl begin like that : ?xml version=1.0 encoding=iso-8859-1? !-- uv -- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:i18n=http://apache.org/cocoon/i18n/2.0; When opening http://localhost/cocoon/myPages/ManUser.xsli I obtain this : ?xml version=1.0 encoding=UTF-8 ? !-- uv-- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:i18n=http://apache.org/cocoon/i18n/2.0; - Original Message - From: Piroumian, Konstantin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 6:09 PM Subject: Re: [C2] Encoding value with I18n If you talk about i18nTransformer from latest C2 (which replaced the old i18n transformer), then it is not intended to specify encodings. It uses encodings from your files and simply replaces i18n text by values from the dictionary. If your XML file is in UTF-8 then the result will be also in UTF-8. If you want to specify other encoding then for your response then, I think, you have to look at the Serializers. If you post your pages I could look at them and try to understand what's the problem. Regards, Konstantin Piroumian. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 6:26 PM Subject: [C2] Encoding value with I18n How can I change the encoding value produced by the i18n transformer (by default UTF-8)? In sitemap file I tried map:transformer ... encoding value=iso-8859-1 then encodingiso-8859-1/encoding then map:parameter name=encoding value=iso-8859-1/ etc.. /map:transformer ... even in the map:transform tag NB: the dictionary and xml to translate begin with : ?xml version=1.0 encoding=iso-8859-1? but the xml file is always ?xml version=1.0 encoding=UTF-8? help!!! - Original Message - From: Matt Sergeant [EMAIL PROTECTED] To: Zeljko Rajic [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 4:09 PM Subject: Re: setting response headers with XSP On Tue, 19 Jun 2001, Zeljko Rajic wrote: Hi, I'm currently trying to find out how to set response headers within Cocoon, respectively XSP in general. Reading the Cocoon respectively Cocoon's XSP documentation and FAQs I couldn't find any information about this topic. So I still got some open questions and would appreciate it if somebody could give me some further information or could point me to a resource. My questions are: 1. Where in the XSP document do I have to place the xsp-response:set-header .../ tag? Does it matter where I place this tag? Concerning HTTP, it is necessary to send any header information prior any content/data. Thus, does Cocoon buffer the content/data and then writes header information and content/data in a 'single' run? Having a look at the generated Java source, shows that it generates/fires SAX events and thus makes me wonder how the response headers currently being set!? 2. The same probably applies to cookies, thus the same question for cookies: Where in the XSP document is it allowed to set a cookie using the xsp-cookie:cookie tag? These two questions are really implementation dependant, and belong on Cocoon-Users. My take on it, is that it doesn't matter in AxKit or Cocoon
Re: [C2] Encoding value with I18n
Look at the documentation of the sitemap on C2 site, the Serializers section. Somebody posted this solution today already: quot The Serializers example on the xml.apache.org/cocoon2/sitemap.html page uses the value attribute of the encoding element like this: encoding value=UTF-8/ I had to change it to: encodingiso-8859-1/encoding /quot Hope, this will help. Regards, Konstantin Piroumian. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 11:36 AM Subject: Re: [C2] Encoding value with I18n I have tried this too, and it also doesn't work. Thanks for your help - Original Message - From: Piroumian, Konstantin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 7:16 PM Subject: Re: [C2] Encoding value with I18n I am not sure that the problem is with i18n but I'll take a look at it. I'm not sure, but maybe result encoding must be specified in the Serializer? Something like: map:serialize type=xml map:parameter name=encodingiso-8859-1/map:parameter /map:serialize I will investigate this problem and let you know if I find something. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 8:42 PM Subject: Re: [C2] Encoding value with I18n Thanks I'm working on C2.0b1 I understand that all the transformers work the same way, but it seems that i18n does not. The sitemap is as follow (in fact it's a sub/sitemap): map:match pattern=ManUser.xsli map:generate type=file src=ManUser.xsl/ map:transform type=i18n map:parameter name=src value=lang/ManUser.xml/ /map:transform map:serialize type=xml/ /map:match ManUser.xsl begin like that : ?xml version=1.0 encoding=iso-8859-1? !-- uv -- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:i18n=http://apache.org/cocoon/i18n/2.0; When opening http://localhost/cocoon/myPages/ManUser.xsli I obtain this : ?xml version=1.0 encoding=UTF-8 ? !-- uv-- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:i18n=http://apache.org/cocoon/i18n/2.0; - Original Message - From: Piroumian, Konstantin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 6:09 PM Subject: Re: [C2] Encoding value with I18n If you talk about i18nTransformer from latest C2 (which replaced the old i18n transformer), then it is not intended to specify encodings. It uses encodings from your files and simply replaces i18n text by values from the dictionary. If your XML file is in UTF-8 then the result will be also in UTF-8. If you want to specify other encoding then for your response then, I think, you have to look at the Serializers. If you post your pages I could look at them and try to understand what's the problem. Regards, Konstantin Piroumian. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 6:26 PM Subject: [C2] Encoding value with I18n How can I change the encoding value produced by the i18n transformer (by default UTF-8)? In sitemap file I tried map:transformer ... encoding value=iso-8859-1 then encodingiso-8859-1/encoding then map:parameter name=encoding value=iso-8859-1/ etc.. /map:transformer ... even in the map:transform tag NB: the dictionary and xml to translate begin with : ?xml version=1.0 encoding=iso-8859-1? but the xml file is always ?xml version=1.0 encoding=UTF-8? help!!! - Original Message - From: Matt Sergeant [EMAIL PROTECTED] To: Zeljko Rajic [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 4:09 PM Subject: Re: setting response headers with XSP On Tue, 19 Jun 2001, Zeljko Rajic wrote: Hi, I'm currently trying to find out how to set response headers within Cocoon, respectively XSP in general. Reading the Cocoon respectively Cocoon's XSP documentation and FAQs I couldn't find any information about this topic. So I still got some open questions and would appreciate it if somebody could give me some further information or could point me to a resource. My questions are: 1. Where in the XSP document do I have to place the xsp-response:set-header .../ tag? Does it matter where I place this tag? Concerning HTTP, it is necessary to send any
[C2] Encoding value with I18n
How can I change the encoding value produced by the i18n transformer (by default UTF-8)? In sitemap file I tried map:transformer ... encoding value=iso-8859-1 then encodingiso-8859-1/encoding then map:parameter name=encoding value=iso-8859-1/ etc.. /map:transformer ... even in the map:transform tag NB: the dictionary and xml to translate begin with : ?xml version=1.0 encoding=iso-8859-1? but the xml file is always ?xml version=1.0 encoding=UTF-8? help!!! - Original Message - From: Matt Sergeant [EMAIL PROTECTED] To: Zeljko Rajic [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 4:09 PM Subject: Re: setting response headers with XSP On Tue, 19 Jun 2001, Zeljko Rajic wrote: Hi, I'm currently trying to find out how to set response headers within Cocoon, respectively XSP in general. Reading the Cocoon respectively Cocoon's XSP documentation and FAQs I couldn't find any information about this topic. So I still got some open questions and would appreciate it if somebody could give me some further information or could point me to a resource. My questions are: 1. Where in the XSP document do I have to place the xsp-response:set-header .../ tag? Does it matter where I place this tag? Concerning HTTP, it is necessary to send any header information prior any content/data. Thus, does Cocoon buffer the content/data and then writes header information and content/data in a 'single' run? Having a look at the generated Java source, shows that it generates/fires SAX events and thus makes me wonder how the response headers currently being set!? 2. The same probably applies to cookies, thus the same question for cookies: Where in the XSP document is it allowed to set a cookie using the xsp-cookie:cookie tag? These two questions are really implementation dependant, and belong on Cocoon-Users. My take on it, is that it doesn't matter in AxKit or Cocoon 1, because both use the build a DOM method. It probably matters in Cocoon 2 though. I think the C2 solution is to cache to a certain extent and hope you try and send the header early enough in the XSP file that it just works :-) But I await to be corrected on that. 3. Does any specification exists for XSP? Often it's not possible to say whether some XSP constructs do not work because of wrong usage or because of a bug in Cocoon's XSP implementation. An specification also would allow to build an XSP verifier - or does a verifier already exist? I think an XSP verifier would be very hard to write. Certainly not possible in W3C Schemas. Though perhaps possible in Schematron or RELAX. As for a spec, there is nothing formal as yet. We really need to get around to doing that. The problem though, is that with taglibs the XSP set of tags is infinite, and the way you can put them to use is also infinite. The upshot of this is just about any XML document is a valid XSP document, with the exception of items in the XSP namespace itself, which may have to appear in a certain hierarchy. -- Matt/ /||** Founder and CTO ** ** http://axkit.com/ ** file://||** AxKit.com Ltd ** ** XML Application Serving ** // ||** http://axkit.org ** ** XSLT, XPathScript, XSP ** // \\| // ** mod_perl news and resources: http://take23.org ** \\// //\\ // \\ - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C2] Encoding value with I18n
If you talk about i18nTransformer from latest C2 (which replaced the old i18n transformer), then it is not intended to specify encodings. It uses encodings from your files and simply replaces i18n text by values from the dictionary. If your XML file is in UTF-8 then the result will be also in UTF-8. If you want to specify other encoding then for your response then, I think, you have to look at the Serializers. If you post your pages I could look at them and try to understand what's the problem. Regards, Konstantin Piroumian. - Original Message - From: matthieu VIDAL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 6:26 PM Subject: [C2] Encoding value with I18n How can I change the encoding value produced by the i18n transformer (by default UTF-8)? In sitemap file I tried map:transformer ... encoding value=iso-8859-1 then encodingiso-8859-1/encoding then map:parameter name=encoding value=iso-8859-1/ etc.. /map:transformer ... even in the map:transform tag NB: the dictionary and xml to translate begin with : ?xml version=1.0 encoding=iso-8859-1? but the xml file is always ?xml version=1.0 encoding=UTF-8? help!!! - Original Message - From: Matt Sergeant [EMAIL PROTECTED] To: Zeljko Rajic [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 4:09 PM Subject: Re: setting response headers with XSP On Tue, 19 Jun 2001, Zeljko Rajic wrote: Hi, I'm currently trying to find out how to set response headers within Cocoon, respectively XSP in general. Reading the Cocoon respectively Cocoon's XSP documentation and FAQs I couldn't find any information about this topic. So I still got some open questions and would appreciate it if somebody could give me some further information or could point me to a resource. My questions are: 1. Where in the XSP document do I have to place the xsp-response:set-header .../ tag? Does it matter where I place this tag? Concerning HTTP, it is necessary to send any header information prior any content/data. Thus, does Cocoon buffer the content/data and then writes header information and content/data in a 'single' run? Having a look at the generated Java source, shows that it generates/fires SAX events and thus makes me wonder how the response headers currently being set!? 2. The same probably applies to cookies, thus the same question for cookies: Where in the XSP document is it allowed to set a cookie using the xsp-cookie:cookie tag? These two questions are really implementation dependant, and belong on Cocoon-Users. My take on it, is that it doesn't matter in AxKit or Cocoon 1, because both use the build a DOM method. It probably matters in Cocoon 2 though. I think the C2 solution is to cache to a certain extent and hope you try and send the header early enough in the XSP file that it just works :-) But I await to be corrected on that. 3. Does any specification exists for XSP? Often it's not possible to say whether some XSP constructs do not work because of wrong usage or because of a bug in Cocoon's XSP implementation. An specification also would allow to build an XSP verifier - or does a verifier already exist? I think an XSP verifier would be very hard to write. Certainly not possible in W3C Schemas. Though perhaps possible in Schematron or RELAX. As for a spec, there is nothing formal as yet. We really need to get around to doing that. The problem though, is that with taglibs the XSP set of tags is infinite, and the way you can put them to use is also infinite. The upshot of this is just about any XML document is a valid XSP document, with the exception of items in the XSP namespace itself, which may have to appear in a certain hierarchy. -- Matt/ /||** Founder and CTO ** ** http://axkit.com/ ** file://||** AxKit.com Ltd ** ** XML Application Serving ** // ||** http://axkit.org ** ** XSLT, XPathScript, XSP ** // \\| // ** mod_perl news and resources: http://take23.org ** \\// //\\ // \\ - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered
