Re: dynamic encoding for html serialiser?
Yury Mikhienko wrote: On Thu, 17 Jul 2003 10:25:56 -0400 Geoff Howard [EMAIL PROTECTED] wrote: Yury Mikhienko wrote: On Thu, 17 Jul 2003 09:43:27 -0400 Geoff Howard [EMAIL PROTECTED] wrote: Sometime ago this question was already asked on cocoon-dev list, but setup() method is not implemented in serializers at this time (( ... Hope that clears it up, Geoff Yes, you are right, but implementation of the setup() method make serialize step more flexible. It was decided to purposely deny that flexibility. You should be able achieve anything you need to with matchers and selectors. Ok, you set the rules. ;)) Well, it wasn't me but we (before I was part of we incidentally) but i do think I get the logic. However we (including you) set the rules, so if you think you have a good case for adding this feature, don't be afraid to bring it up on [EMAIL PROTECTED] First, search the archives to see if you can find and understand the original reasoning (if not ask on dev). Then, explain your use and ask for opinions about whether this should challenge the original decision. Only be ready to accept alternative solutions which preserve other important architectural protections. Geoff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic encoding for html serialiser?
Sometime ago this question was already asked on cocoon-dev list, but setup() method is not implemented in serializers at this time (( You declare the encoding as part of the serializer config in the sitemap. if you need the same serializer to use different encodings in different pipelines, you need to declare the serializer once for each of the encodings with a different name each time. Geoff Tsui, Alban wrote: Hi I am trying to write a xsp page directly generating html and my page will take in a parameter which would tell me what final encoding the page should use. SO I tried to manually generate that meta Content=text/html; charset=ISO-8859-1 http-equiv=Content-Type tag ... but my serializer seems to append meta Content=text/html; charset=UTF-8 http-equiv=Content-Type in my final html output. i have not specified any encoding in my html serializer defintion in my sitemap at all... and I have an entry as follows: map:serializers default=html map:serializer logger=sitemap.serializer.xml mime-type=text/xml name=xml src=org.apache.cocoon.serialization.XMLSerializer/ map:serializer logger=sitemap.serializer.html mime-type=text/html name=html src=org.apache.cocoon.serialization.HTMLSerializer buffer-size1024/buffer-size /map:serializer map:serializer logger=sitemap.serializer.svgxml mime-type=image/svg-xml name=svgxml src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD SVG 2303 Stylable//EN/doctype-public doctype-systemhttp://www.w3.org/TR/2000/03/WD-SVG-2303//doctype-system /map:serializer map:serializer mime-type=image/jpeg name=svg2jpeg src=org.apache.cocoon.serialization.SVGSerializer parameter name=quality type=float value=0.9/ /map:serializer map:serializer mime-type=image/png name=svg2png src=org.apache.cocoon.serialization.SVGSerializer/ /map:serializers Is there anyway I could effect the final encoding in that meta string generated from the serialiser from within the xsp generator? I am using version 2.0.3 cocoon. AT Join us at Cognos' biggest event of the year/ Enterprise 2003, The Cognos Business Forum/. Taking place in over 25 cities around the world, it's an opportunity for Business and IT leaders to learn about strategies for driving performance. Visit_ http://www.cognos.com/enterprise03_ for more details. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic encoding for html serialiser?
Yury Mikhienko wrote: Sometime ago this question was already asked on cocoon-dev list, but setup() method is not implemented in serializers at this time (( Sorry, I must not be coming across clearly: you must declare the encoding in the definition of your serializer in the map:components section of the sitemap. This configuration is read during configure(). map:components ... map:serializers ... map:serializer name=encoding1 src=org.apache.cocoon.serialization.XMLSerializer ... encodingencoding1/encoding /map:serializer map:serializer name=encoding2 src=org.apache.cocoon.serialization.XMLSerializer ... encodingencoding2/encoding /map:serializer /map:serializers then, in your pipeline something like: map:match .. ... map:serialize type=encoding1/ /map:match map:match .. ... map:serialize type=encoding2/ /map:match Hope that clears it up, Geoff You declare the encoding as part of the serializer config in the sitemap. if you need the same serializer to use different encodings in different pipelines, you need to declare the serializer once for each of the encodings with a different name each time. Geoff Tsui, Alban wrote: Hi I am trying to write a xsp page directly generating html and my page will take in a parameter which would tell me what final encoding the page should use. SO I tried to manually generate that meta Content=text/html; charset=ISO-8859-1 http-equiv=Content-Type tag ... but my serializer seems to append meta Content=text/html; charset=UTF-8 http-equiv=Content-Type in my final html output. i have not specified any encoding in my html serializer defintion in my sitemap at all... and I have an entry as follows: map:serializers default=html map:serializer logger=sitemap.serializer.xml mime-type=text/xml name=xml src=org.apache.cocoon.serialization.XMLSerializer/ map:serializer logger=sitemap.serializer.html mime-type=text/html name=html src=org.apache.cocoon.serialization.HTMLSerializer buffer-size1024/buffer-size /map:serializer map:serializer logger=sitemap.serializer.svgxml mime-type=image/svg-xml name=svgxml src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD SVG 2303 Stylable//EN/doctype-public doctype-systemhttp://www.w3.org/TR/2000/03/WD-SVG-2303//doctype-system /map:serializer map:serializer mime-type=image/jpeg name=svg2jpeg src=org.apache.cocoon.serialization.SVGSerializer parameter name=quality type=float value=0.9/ /map:serializer map:serializer mime-type=image/png name=svg2png src=org.apache.cocoon.serialization.SVGSerializer/ /map:serializers Is there anyway I could effect the final encoding in that meta string generated from the serialiser from within the xsp generator? I am using version 2.0.3 cocoon. AT Join us at Cognos' biggest event of the year/ Enterprise 2003, The Cognos Business Forum/. Taking place in over 25 cities around the world, it's an opportunity for Business and IT leaders to learn about strategies for driving performance. Visit_ http://www.cognos.com/enterprise03_ for more details. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic encoding for html serialiser?
Yury Mikhienko wrote: On Thu, 17 Jul 2003 09:43:27 -0400 Geoff Howard [EMAIL PROTECTED] wrote: Sometime ago this question was already asked on cocoon-dev list, but setup() method is not implemented in serializers at this time (( ... Hope that clears it up, Geoff Yes, you are right, but implementation of the setup() method make serialize step more flexible. It was decided to purposely deny that flexibility. You should be able achieve anything you need to with matchers and selectors. Geoff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic encoding for html serialiser?
On Thu, 17 Jul 2003 10:25:56 -0400 Geoff Howard [EMAIL PROTECTED] wrote: Yury Mikhienko wrote: On Thu, 17 Jul 2003 09:43:27 -0400 Geoff Howard [EMAIL PROTECTED] wrote: Sometime ago this question was already asked on cocoon-dev list, but setup() method is not implemented in serializers at this time (( ... Hope that clears it up, Geoff Yes, you are right, but implementation of the setup() method make serialize step more flexible. It was decided to purposely deny that flexibility. You should be able achieve anything you need to with matchers and selectors. Ok, you set the rules. ;)) -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dynamic encoding for html serialiser?
Title: RE: dynamic encoding for html serialiser?
So you are saying I could do something like:
map:match pattern=*/test
map:act type=characterencoding
map:parameter name=form-encoding value=utf-8/
/map:act
map:act type=sethtmlencparam/ !-- set up pipeline param html_enc for serializer --
map:generate type=serverpages src="">
map:serialize type={html_enc}/
/map:match
and have several html serializer for different encodings.
Correct?
I think I will need shiftjis for japanse, some chinese encodings and korean encoding plus standard iso encoding... would cocoon support that?
it just seems to me it is a bit strange we can pass that encoding as a parameter into the map:serialize tag.
Cheers
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]]
Sent: 16 July 2003 16:25
To: [EMAIL PROTECTED]
Subject: Re: dynamic encoding for html serialiser?
You declare the encoding as part of the serializer config in the
sitemap. if you need the same serializer to use different encodings in
different pipelines, you need to declare the serializer once for each of
the encodings with a different name each time.
Geoff
Tsui, Alban wrote:
Hi
I am trying to write a xsp page directly generating html and my page
will take in a parameter which would tell me what final encoding the
page should use. SO I tried to manually generate that
meta Content=text/html; charset=ISO-8859-1 http-equiv=Content-Type
tag ...
but my serializer seems to append
meta Content=text/html; charset=UTF-8 http-equiv=Content-Type
in my final html output.
i have not specified any encoding in my html serializer defintion in my
sitemap at all... and I have an entry as follows:
map:serializers default=html
map:serializer logger=sitemap.serializer.xml
mime-type=text/xml name=xml
src="">
map:serializer logger=sitemap.serializer.html
mime-type=text/html name=html
src="">
buffer-size1024/buffer-size
/map:serializer
map:serializer logger=sitemap.serializer.svgxml
mime-type=image/svg-xml name=svgxml
src="">
doctype-public-//W3C//DTD SVG 2303
Stylable//EN/doctype-public
doctype-systemhttp://www.w3.org/TR/2000/03/WD-SVG-2303//doctype-system
/map:serializer
map:serializer mime-type=image/jpeg name=svg2jpeg
src="">
parameter name=quality type=float
value=0.9/
/map:serializer
map:serializer mime-type=image/png name=svg2png
src="">
/map:serializers
Is there anyway I could effect the final encoding in that meta string
generated from the serialiser from within the xsp generator?
I am using version 2.0.3 cocoon.
AT
Join us at Cognos' biggest event of the year/ Enterprise 2003, The
Cognos Business Forum/. Taking place in over 25 cities around the
world, it's an opportunity for Business and IT leaders to learn about
strategies for driving performance. Visit_
http://www.cognos.com/enterprise03_ for more details.
This message may contain privileged and/or confidential information. If
you have received this e-mail in error or are not the intended
recipient, you may not use, copy, disseminate or distribute it; do not
open any attachments, delete it immediately from your system and notify
the sender promptly by e-mail that you have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Join us at Cognos' biggest event of the year Enterprise 2003, The Cognos Business Forum. Taking place in over 25 cities around the world, it's an opportunity for Business and IT leaders to learn about strategies for driving performance. Visit http://www.cognos.com/enterprise03 for more details.
This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
Re: dynamic encoding for html serialiser?
actually, the encoding I think has to get passed as a parameter to
map:serializer (that is in the component definition) not where you call
it in the sitemap. I don't know the exact param name or I'd give you an
example. There should be some in the docs, though.
Geoff
Tsui, Alban wrote:
So you are saying I could do something like:
map:match pattern=*/test
map:act type=characterencoding
map:parameter
name=form-encoding value=utf-8/
/map:act
map:act type=sethtmlencparam/ !--
set up pipeline param html_enc for serializer --
map:generate type=serverpages
src=test.xsp/
map:serialize type={html_enc}/
/map:match
and have several html serializer for different encodings.
Correct?
I think I will need shiftjis for japanse, some chinese encodings and
korean encoding plus standard iso encoding... would cocoon support that?
it just seems to me it is a bit strange we can pass that encoding as a
parameter into the map:serialize tag.
Cheers
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: 16 July 2003 16:25
To: [EMAIL PROTECTED]
Subject: Re: dynamic encoding for html serialiser?
You declare the encoding as part of the serializer config in the
sitemap. if you need the same serializer to use different encodings in
different pipelines, you need to declare the serializer once for each of
the encodings with a different name each time.
Geoff
Tsui, Alban wrote:
Hi
I am trying to write a xsp page directly generating html and my page
will take in a parameter which would tell me what final encoding the
page should use. SO I tried to manually generate that
meta Content=text/html; charset=ISO-8859-1 http-equiv=Content-Type
tag ...
but my serializer seems to append
meta Content=text/html; charset=UTF-8 http-equiv=Content-Type
in my final html output.
i have not specified any encoding in my html serializer defintion in my
sitemap at all... and I have an entry as follows:
map:serializers default=html
map:serializer logger=sitemap.serializer.xml
mime-type=text/xml name=xml
src=org.apache.cocoon.serialization.XMLSerializer/
map:serializer logger=sitemap.serializer.html
mime-type=text/html name=html
src=org.apache.cocoon.serialization.HTMLSerializer
buffer-size1024/buffer-size
/map:serializer
map:serializer logger=sitemap.serializer.svgxml
mime-type=image/svg-xml name=svgxml
src=org.apache.cocoon.serialization.XMLSerializer
doctype-public-//W3C//DTD SVG 2303
Stylable//EN/doctype-public
doctype-systemhttp://www.w3.org/TR/2000/03/WD-SVG-2303//doctype-system
/map:serializer
map:serializer mime-type=image/jpeg name=svg2jpeg
src=org.apache.cocoon.serialization.SVGSerializer
parameter name=quality type=float
value=0.9/
/map:serializer
map:serializer mime-type=image/png name=svg2png
src=org.apache.cocoon.serialization.SVGSerializer/
/map:serializers
Is there anyway I could effect the final encoding in that meta string
generated from the serialiser from within the xsp generator?
I am using version 2.0.3 cocoon.
AT
Join us at Cognos' biggest event of the year/ Enterprise 2003, The
Cognos Business Forum/. Taking place in over 25 cities around the
world, it's an opportunity for Business and IT leaders to learn about
strategies for driving performance. Visit_
http://www.cognos.com/enterprise03_ for more details.
This message may contain privileged and/or confidential information. If
you have received this e-mail in error or are not the intended
recipient, you may not use, copy, disseminate or distribute it; do not
open any attachments, delete it immediately from your system and notify
the sender promptly by e-mail that you have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Join us at Cognos' biggest event of the year/ Enterprise 2003, The
Cognos Business Forum/. Taking place in over 25 cities around the
world, it's an opportunity for Business and IT leaders to learn about
strategies for driving performance. Visit_
http://www.cognos.com/enterprise03_ for more details.
This message may contain privileged and/or confidential information. If
you have received this e-mail in error or are not the intended
recipient, you may not use, copy, disseminate or distribute it; do not
open any attachments, delete it immediately from your
