Re: encoding, UTF-8
we have solve the same problem using action map:actions map:action name=set-encoding src=org.apache.cocoon.acting.SetCharacterEncodingAction/ ... ... ... !-- === order form === -- map:pipeline map:act type=set-encoding map:parameter name=form-encoding value=iso-8859-7/ /map:act map:act type=locale map:match pattern=order/proceed map:aggregate element=order map:part src=cocoon:/order/product/ map:part src=cocoon:/order/def/ /map:aggregate map:transform src=../htdocs/serverpages/order.xsl/ map:serialize type=html/ /map:match map:match pattern=order/product map:generate src=../htdocs/serverpages/product.xsp type=serverpages/ map:serialize type=xml/ /map:match map:match pattern=order/def map:generate src=../htdocs/serverpages/def.xml/ map:serialize type=xml/ /map:match /map:act /map:pipeline -- stavros On Thu, 27 Nov 2003, Boris Althaus wrote: Hallo Lionel, we had problems with this issues several times. Play arround with these two initparams. The strange thing was, that on different engines we had to change the container-encoding to avoid encoding problems. Now we do not have any problems with encoding anymore and we don't need entries in the sitemaps. init-param param-nameform-encoding/param-name param-valueUTF-8/param-value /init-param init-param param-namecontainer-encoding/param-name param-valueISO-8859-1/param-value /init-param Boris - Original Message - From: Lionel Crine To: [EMAIL PROTECTED] Sent: Thursday, November 27, 2003 11:57 AM Subject: encoding, UTF-8 Hi, I want to put the entire plateform into UTF-8. For now, cocoon is using ISO-8859-1. Here what I've already done : map:serializer logger=sitemap.serializer.html mime-type=text/html name=html pool-grow=4 pool-max=32 pool-min=4 src=org.apache.cocoon.serialization.HTMLSerializer buffer-size1024/buffer-size encodingUTF-8/encoding /map:serializer But that's not enough because I have many problem with the form. When I reload it with some request parameter (using xsl:value-of). The characters are not display good. For example the become f . Any idea ? I use Cocoon 2.0.4 Lionel Lionel CRINE Ingnieur Systmes documentaires Socit : 4DConcept 22 rue Etienne de Jouy 78353 JOUY EN JOSAS Tel : 01.34.58.70.70 Fax : 01.39.58.70.70 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding, UTF-8
Thx. At 16:03 27/11/2003 +0200, you wrote: we have solve the same problem using action map:actions map:action name=set-encoding src=org.apache.cocoon.acting.SetCharacterEncodingAction/ ... ... ... !-- === order form === -- map:pipeline map:act type=set-encoding map:parameter name=form-encoding value=iso-8859-7/ /map:act map:act type=locale map:match pattern=order/proceed map:aggregate element=order map:part src=cocoon:/order/product/ map:part src=cocoon:/order/def/ /map:aggregate map:transform src=../htdocs/serverpages/order.xsl/ map:serialize type=html/ /map:match map:match pattern=order/product map:generate src=../htdocs/serverpages/product.xsp type=serverpages/ map:serialize type=xml/ /map:match map:match pattern=order/def map:generate src=../htdocs/serverpages/def.xml/ map:serialize type=xml/ /map:match /map:act /map:pipeline -- stavros On Thu, 27 Nov 2003, Boris Althaus wrote: Hallo Lionel, we had problems with this issues several times. Play arround with these two initparams. The strange thing was, that on different engines we had to change the container-encoding to avoid encoding problems. Now we do not have any problems with encoding anymore and we don't need entries in the sitemaps. init-param param-nameform-encoding/param-name param-valueUTF-8/param-value /init-param init-param param-namecontainer-encoding/param-name param-valueISO-8859-1/param-value /init-param Boris - Original Message - From: Lionel Crine To: [EMAIL PROTECTED] Sent: Thursday, November 27, 2003 11:57 AM Subject: encoding, UTF-8 Hi, I want to put the entire plateform into UTF-8. For now, cocoon is using ISO-8859-1. Here what I've already done : map:serializer logger=sitemap.serializer.html mime-type=text/html name=html pool-grow=4 pool-max=32 pool-min=4 src=org.apache.cocoon.serialization.HTMLSerializer buffer-size1024/buffer-size encodingUTF-8/encoding /map:serializer But that's not enough because I have many problem with the form. When I reload it with some request parameter (using xsl:value-of). The characters are not display good. For example the é become Ãf© . Any idea ? I use Cocoon 2.0.4 Lionel Lionel CRINE Ingénieur Systèmes documentaires Société : 4DConcept 22 rue Etienne de Jouy 78353 JOUY EN JOSAS Tel : 01.34.58.70.70 Fax : 01.39.58.70.70 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Lionel CRINE Ingénieur Systèmes documentaires Société : 4DConcept 22 rue Etienne de Jouy 78353 JOUY EN JOSAS Tel : 01.34.58.70.70 Fax : 01.39.58.70.70 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
URL Encoding (Coccon 2.1 cvs as of about 2 weeks ago)
Hi,
I am very new to coccon so please excuse any glaring errors in my
question.
I have written a transformer whose job in part is to extrat a uri
from a knowledge article returned from our knowledgebase.
swsolution
cinclude:include select=*|text()
xsl:attribute
name=srccocoon:/soldoc?url=xsl:value-of
select=normalize-space(LongDescLink)/
/xsl:attribute
/cinclude:include
/swsolution
The snippet above indicates my attempt. -
The cinclude transformer then transforms the xml and finds the
correct matcher in my sitemap.
I want to use the html generator to return the file. see below
map:pipeline
map:match pattern=soldoc
map:generate src={request-param:url} type=html/
map:serialize/
/map:match
/map:pipeline
This solution works until I try to generate a uri with an illegal
character ie a space.
It appears that the request-param is (correctly) decoding the
parameter I am passing it but unfortunately this is not the behaviour I
require.
Is there any way that I can re-code the parameter before generating it ?
Or can anyone suggest an alternative means of achieving the same
end. ie generating html from a remote server.
Any help would be appreciated.
Cheers
Si
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL Encoding (Coccon 2.1 cvs as of about 2 weeks ago)
Simon Hutchinson wrote: This solution works until I try to generate a uri with an illegal character ie a space. It appears that the request-param is (correctly) decoding the parameter I am passing it but unfortunately this is not the behaviour I require. Is there any way that I can re-code the parameter before generating it ? Or can anyone suggest an alternative means of achieving the same end. ie generating html from a remote server. I think what you need is the RawRequestParameterModule. See http://wiki.cocoondev.org/Wiki.jsp?page=InputModules HTH Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem - browser doesn\'t care of set encoding
Hi, It really seams that this is the reason!! I had master copy on Tomcat 4.1.27, and the new copy on 4.1.29. As I changed to 4.1.27 everything is fine :-) I'm pretty suprised, I must say! Thanks for help! Marcin On Tue, Nov 18, 2003 at 11:10:38AM +0100, [EMAIL PROTECTED] wrote: Hi, I have copied my Cocoon based WebApp from one Tomcat to another. On the new copy, the page is displayed incorrectly - browser takes encoding as ISO-8859-1 instead of UTF-8. When I change encoding manually to UTF-8 it is displayed correctly. I'm also checking both copies using the same browser. I have set XHTML serializer encoding to UTF, and it still doesn't work! snip/ What might be the reasong? if new Tomcat is 4.1.29 - switch back to 4.1.27 - had the same problem, no idea what causes it - I think it does not relate to cocoon. ouzo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding
Hi, I've asked the same question yesterday. And the solution (unfortunately) was exactly the same! Regards, Marcin This looks to be a problem with Tomcat 4.1.29. I'm not quite sure how to resolve it, but running Cocoon 2.1.3 in Tomcat 4.1.27 seems to work. - Justin On Nov 18, 2003, at 4:42 PM, Justin Makeig wrote: I'm having problems with character encodings. I've specified in every place I could think of that I want all XHTML pages to be rendered as UTF-8. However, when I view them in a browser I get garbage for all of the special characters. When I manually toggle the browser's text encoding the UTF-8 everything is fine. Can any one suggest how I can configure Cocoon 2.1.3 to output UTF-8? sitemap.xmap === map:serializers default=xhtml map:serializer logger=sitemap.serializer.xhtml mime-type=text/html name=xhtml pool-grow=2 pool-max=64 pool-min=2 src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Strict//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/ doctype-system encodingUTF-8/encoding /map:serializer /map:serializers transform == xsl:output method=xml doctype-public=-//W3C//DTD XHTML 1.0 Strict//EN doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; encoding=UTF-8 indent=no omit-xml-declaration=yes cdata-section-elements=script/ XHTML result === html xml:lang=en xmlns=http://www.w3.org/1999/xhtml; head meta content=text/html; charset=utf-8 http-equiv=content-type/ Thanks. - Justin Makeig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL Encoding (Coccon 2.1 cvs as of about 2 weeks ago)
Tony Collen wrote:
Simon Hutchinson wrote:
This solution works until I try to generate a uri with an illegal
character ie a space.
It appears that the request-param is (correctly) decoding the
parameter I am passing it but unfortunately this is not the behaviour
I require.
Is there any way that I can re-code the parameter before generating
it ?
Or can anyone suggest an alternative means of achieving the same
end. ie generating html from a remote server.
I think what you need is the RawRequestParameterModule.
See http://wiki.cocoondev.org/Wiki.jsp?page=InputModules
Thanks for the suggestion. From the documentation this seems like the
correct input module for my issue.
It does allow me to reduce my probelm to a simpler case however.
With the following sitemap match
map:match pattern=soldoc
map:generate src={raw-request-param:url} type=html/
map:serialize/
/map:match
If I request
http://localhost:8080/cocoon/soldoc?url=http://example.com/foo.html
the html is returned
However even with the raw-request-param module specified if I request
http://localhost:8080/cocoon/soldoc?url=http://example.com/fo%20o.html
I get a file not found exception (the file fo o.html does exist and I
can get it with the plain url http://example.com/fo%20o.html)
Can anyone advise me as to why this might be ?
Thanks
Si
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding problem - browser doesn\'t care of set encoding
On Tue, Nov 18, 2003 at 11:10:38AM +0100, [EMAIL PROTECTED] wrote: Hi, I have copied my Cocoon based WebApp from one Tomcat to another. On the new copy, the page is displayed incorrectly - browser takes encoding as ISO-8859-1 instead of UTF-8. When I change encoding manually to UTF-8 it is displayed correctly. I'm also checking both copies using the same browser. I have set XHTML serializer encoding to UTF, and it still doesn't work! snip/ What might be the reasong? if new Tomcat is 4.1.29 - switch back to 4.1.27 - had the same problem, no idea what causes it - I think it does not relate to cocoon. ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(501)720812 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Encoding
I'm having problems with character encodings. I've specified in every place I could think of that I want all XHTML pages to be rendered as UTF-8. However, when I view them in a browser I get garbage for all of the special characters. When I manually toggle the browser's text encoding the UTF-8 everything is fine. Can any one suggest how I can configure Cocoon 2.1.3 to output UTF-8? sitemap.xmap === map:serializers default=xhtml map:serializer logger=sitemap.serializer.xhtml mime-type=text/html name=xhtml pool-grow=2 pool-max=64 pool-min=2 src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Strict//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/ doctype-system encodingUTF-8/encoding /map:serializer /map:serializers transform == xsl:output method=xml doctype-public=-//W3C//DTD XHTML 1.0 Strict//EN doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; encoding=UTF-8 indent=no omit-xml-declaration=yes cdata-section-elements=script/ XHTML result === html xml:lang=en xmlns=http://www.w3.org/1999/xhtml; head meta content=text/html; charset=utf-8 http-equiv=content-type/ Thanks. - Justin Makeig -- Product Manager The Center for Document Engineering University of California, Berkeley http://cde.berkeley.edu/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[JXForm/XMLForm] how to set encoding
Hello, I would like to use accents (for french) and I'm looking for a solution to set the encoding in ISO-8859-1. Is someone has an experience? Thanks Sylvain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JXForm/XMLForm] how to set encoding
I would like to use accents (for french) and I'm looking for a solution to set the encoding in ISO-8859-1. I don't know, if I undestand you correctly, but if you have form encoding problems, this may help (I received when asking for woody, but I think it doesn't matter): It's a problem with the default configuration of Cocoon, but it's easy to fix: * edit the web.xml file, and uncomment the form-encoding init parameter and set it to UTF-8 (do NOT touch the container-encoding parameter) * edit the root sitemap.xmap, and set the encoding of the html serializer to UTF-8: map:serializer logger=sitemap.serializer.html mime-type=text/html name=html pool-grow=4 pool-max=32 pool-min=4 src=org.apache.cocoon.serialization.HTMLSerializer encodingUTF-8/encoding /map:serializer Regards, Marcin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [JXForm/XMLForm] how to set encoding
Hello, Yes it was my problem and it WORKS! Thanks Sylvain -Message d'origine- De: Marcin Okraszewski [mailto:[EMAIL PROTECTED] Date: lundi, 17. novembre 2003 11:05 À: [EMAIL PROTECTED] Objet: Re: [JXForm/XMLForm] how to set encoding I would like to use accents (for french) and I'm looking for a solution to set the encoding in ISO-8859-1. I don't know, if I undestand you correctly, but if you have form encoding problems, this may help (I received when asking for woody, but I think it doesn't matter): It's a problem with the default configuration of Cocoon, but it's easy to fix: * edit the web.xml file, and uncomment the form-encoding init parameter and set it to UTF-8 (do NOT touch the container-encoding parameter) * edit the root sitemap.xmap, and set the encoding of the html serializer to UTF-8: map:serializer logger=sitemap.serializer.html mime-type=text/html name=html pool-grow=4 pool-max=32 pool-min=4 src=org.apache.cocoon.serialization.HTMLSerializer encodingUTF-8/encoding /map:serializer Regards, Marcin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Woody and encoding forms.
Hi. I have problem with encoding of Woody webforms. I tried registration sample and when I write non-us characters the form comes refilled with two strange singns instead of one I've inputed (co is converted to co). How to manage with this? Regards, Marcin Okraszewski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Woody and encoding forms.
This is an encoding problem. It seems UTF-8 interpreted as the Western encoding (sorry I don't remember its name) David -Mensaje original- De: Marcin Okraszewski [mailto:[EMAIL PROTECTED] Enviado el: viernes, 07 de noviembre de 2003 14:21 Para: [EMAIL PROTECTED] Asunto: Woody and encoding forms. Hi. I have problem with encoding of Woody webforms. I tried registration sample and when I write non-us characters the form comes refilled with two strange singns instead of one I've inputed (co is converted to co). How to manage with this? Regards, Marcin Okraszewski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Woody and encoding forms.
On Fri, 2003-11-07 at 14:20, Marcin Okraszewski wrote: Hi. I have problem with encoding of Woody webforms. I tried registration sample and when I write non-us characters the form comes refilled with two strange singns instead of one I've inputed (co is converted to co). How to manage with this? It's a problem with the default configuration of Cocoon, but it's easy to fix: * edit the web.xml file, and uncomment the form-encoding init parameter and set it to UTF-8 (do NOT touch the container-encoding parameter) * edit the root sitemap.xmap, and set the encoding of the html serializer to UTF-8: map:serializer logger=sitemap.serializer.html mime-type=text/html name=html pool-grow=4 pool-max=32 pool-min=4 src=org.apache.cocoon.serialization.HTMLSerializer encodingUTF-8/encoding /map:serializer this should fix it. Background information on this can be found at: http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[HELP]: How to set xml encoding?
Hallo, i need to set correctlythe encoding of my xml output files in apipeline. For example: if I use a simplepipeline like this map:generate src=""/map:transform src=""/map:serialize/ The xml encoding in the input.xml is ISO-8859-1, The xml encoding ofthe simple.xsls ISO-8859-1, The simple.xsl file contains a line like thisxsl:output method="xml" version="1.0" encoding="ISO-8859-1" / The output xml has always the encoding UTF-8. Any idea? Thank you Gianluca Morello
RE: [HELP]: How to set xml encoding?
use serialize type="xml" / Jelle -Oorspronkelijk bericht-Van: Gianluca Morello [mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003 17:21Aan: [EMAIL PROTECTED]Onderwerp: [HELP]: How to set xml encoding? Hallo, i need to set correctlythe encoding of my xml output files in apipeline. For example: if I use a simplepipeline like this map:generate src=""/map:transform src=""/map:serialize/ The xml encoding in the input.xml is ISO-8859-1, The xml encoding ofthe simple.xsls ISO-8859-1, The simple.xsl file contains a line like thisxsl:output method="xml" version="1.0" encoding="ISO-8859-1" / The output xml has always the encoding UTF-8. Any idea? Thank you Gianluca Morello
Re: [HELP]: How to set xml encoding?
Gianluca Morello wrote: Hallo, i need to set correctly the encoding of my xml output files in apipeline. For example: if I use a simple pipeline like this map:generate src=input.xml/ map:transform src=simple.xsl/ map:serialize/ The xml encoding in the input.xml is ISO-8859-1, The xml encoding of the simple.xsl s ISO-8859-1, The simple.xsl file contains a line like thisxsl:output method=xml version=1.0 encoding=ISO-8859-1 / The output xml has always the encoding UTF-8. Any idea? Have a look into the map:serializers section, search for the serializer you want to change and use and add encodingISO-8859-1/encoding as child of this map:serializer. Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [HELP]: How to set xml encoding?
Sorry,
al little too quick perhaps. You should also define the encoding in the
components section, for example:
map:serializers
default="html"
label="result"
map:serializer name="xml" mime-type="text/xml"
src=""
encodingUTF-8/encoding
/map:serializer
map:serializer name="html" mime-type="text/html"
src=""
encodingISO-8859-1/encoding
/map:serializer
/map:serializers
-Oorspronkelijk bericht-Van: Alten, Jelle Paul
(sds-sp) [mailto:[EMAIL PROTECTED]Verzonden: donderdag 6
november 2003 17:03Aan:
'[EMAIL PROTECTED]'Onderwerp: RE: [HELP]: How to set xml
encoding?
use
serialize type="xml" /
Jelle
-Oorspronkelijk bericht-Van: Gianluca Morello
[mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003
17:21Aan: [EMAIL PROTECTED]Onderwerp: [HELP]:
How to set xml encoding?
Hallo,
i need to set correctlythe encoding of my
xml output files in apipeline.
For example:
if I use a simplepipeline like
this
map:generate src=""/map:transform
src=""/map:serialize/
The xml encoding in the input.xml is
ISO-8859-1,
The xml encoding ofthe simple.xsls
ISO-8859-1,
The simple.xsl file contains a line like
thisxsl:output method="xml" version="1.0" encoding="ISO-8859-1"
/
The output xml has always the encoding
UTF-8.
Any idea?
Thank you
Gianluca Morello
Re: [HELP]: How to set xml encoding? SourceWritingTransformer
Hallo Jelle, My serializers map is like this: map:serializers default="html" map:serializer name="xml-iso" mime-type="text/xml" src="" encodingISO-8859-1/encoding /map:serializer /map:serializers And using the following pipeline the xml output encoding is correct! map:generate src=""/map:transform src=""/map:serialize type="xml-iso"/ Thank you for your help. I still have problems with encoding because i have to writexml to file system: I'm using SourceWritingTransformer and my real pipeline is like the following: map:generate src=""/map:transform src=""/ map:transform type="tofile"/map:serialize type="xml-iso"/ My transformers map is: map:transformer name="tofile" src="" !-- 'xml' is the default Serializer (if your Source needs one, like for instance FileSource) -- map:parameter name="serializer" value="xml-iso"//map:transformer The output files continue to have the encoding set to utf-8 Any idea? Thank you Gianluca - Original Message - From: Alten, Jelle Paul (sds-sp) To: '[EMAIL PROTECTED]' Sent: Thursday, November 06, 2003 5:07 PM Subject: RE: [HELP]: How to set xml encoding? Sorry, al little too quick perhaps. You should also define the encoding in the components section, for example: map:serializers default="html" label="result" map:serializer name="xml" mime-type="text/xml" src="" encodingUTF-8/encoding /map:serializer map:serializer name="html" mime-type="text/html" src="" encodingISO-8859-1/encoding /map:serializer /map:serializers -Oorspronkelijk bericht-Van: Alten, Jelle Paul (sds-sp) [mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003 17:03Aan: '[EMAIL PROTECTED]'Onderwerp: RE: [HELP]: How to set xml encoding? use serialize type="xml" / Jelle -Oorspronkelijk bericht-----Van: Gianluca Morello [mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003 17:21Aan: [EMAIL PROTECTED]Onderwerp: [HELP]: How to set xml encoding? Hallo, i need to set correctlythe encoding of my xml output files in apipeline. For example: if I use a simplepipeline like this map:generate src=""/map:transform src=""/map:serialize/ The xml encoding in the input.xml is ISO-8859-1, The xml encoding ofthe simple.xsls ISO-8859-1, The simple.xsl file contains a line like thisxsl:output method="xml" version="1.0" encoding="ISO-8859-1" / The output xml has always the encoding UTF-8. Any idea? Thank you Gianluca Morello
RE: [HELP]: How to set xml encoding for SourceWritingTransformer -
Sorry,
I don't know enough
about the SourceWritingTransformer to tell you how to set the encoding for the
SourceWritingTransformer.
Anybody
else?
-Oorspronkelijk
bericht-Van: Gianluca Morello
[mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003
18:07Aan: [EMAIL PROTECTED]Onderwerp: Re: [HELP]:
How to set xml encoding? SourceWritingTransformer
Hallo Jelle,
My serializers map is like this:
map:serializers
default="html" map:serializer name="xml-iso"
mime-type="text/xml"
src=""
encodingISO-8859-1/encoding
/map:serializer /map:serializers
And using the following pipeline the xml output
encoding is correct!
map:generate src=""/map:transform
src=""/map:serialize type="xml-iso"/
Thank you for your help.
I still have problems with encoding because i
have to writexml to file system:
I'm using SourceWritingTransformer and
my real pipeline is like the
following:
map:generate src=""/map:transform
src=""/
map:transform
type="tofile"/map:serialize
type="xml-iso"/
My transformers map is:
map:transformer
name="tofile"
src=""
!-- 'xml' is the default Serializer (if your Source needs one, like for
instance FileSource) --
map:parameter name="serializer"
value="xml-iso"//map:transformer
The output files continue to have the encoding
set to utf-8
Any idea?
Thank you
Gianluca
- Original Message -
From:
Alten, Jelle Paul (sds-sp)
To: '[EMAIL PROTECTED]'
Sent: Thursday, November 06, 2003 5:07
PM
Subject: RE: [HELP]: How to set xml
encoding?
Sorry, al little too quick perhaps. You should also define the
encoding in the components section, for example:
map:serializers
default="html"
label="result"
map:serializer name="xml" mime-type="text/xml"
src=""
encodingUTF-8/encoding
/map:serializer
map:serializer name="html" mime-type="text/html"
src=""
encodingISO-8859-1/encoding
/map:serializer
/map:serializers
-Oorspronkelijk bericht-Van: Alten, Jelle Paul
(sds-sp) [mailto:[EMAIL PROTECTED]Verzonden:
donderdag 6 november 2003 17:03Aan:
'[EMAIL PROTECTED]'Onderwerp: RE: [HELP]: How to set xml
encoding?
use
serialize type="xml"
/
Jelle
-Oorspronkelijk bericht-Van: Gianluca Morello
[mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november
2003 17:21Aan: [EMAIL PROTECTED]Onderwerp:
[HELP]: How to set xml encoding?
Hallo,
i need to set correctlythe encoding
of my xml output files in apipeline.
For example:
if I use a simplepipeline like
this
map:generate
src=""/map:transform
src=""/map:serialize/
The xml encoding in the input.xml is
ISO-8859-1,
The xml encoding ofthe
simple.xsls ISO-8859-1,
The simple.xsl file contains a line like
thisxsl:output method="xml" version="1.0" encoding="ISO-8859-1"
/
The output xml has always the encoding
UTF-8.
Any idea?
Thank you
Gianluca Morello
xhtml character encoding
Hi, I am using cocoon 2.1.2 and I need some help getting the xml serializer to behave like the html serializer. I can demostrate the problem using the hello-world sample. If I modify samples/hello-world/content/hello.xml and insert the code #189; as follows: ?xml version=1.0? !-- CVS $Id: hello.xml,v 1.3 2003/05/07 04:57:13 vgritsenko Exp $ -- page titleHello/title content paraThis is my #189; first Cocoon page!/para /content /page When I access it as hello.html I get pThis is my frac12; first Cocoon page!/p as hello.xhtml I get pThis is my ½ first Cocoon page!/p I'm not sure the extra char will appear in this email, however viewing the page in a browser displays an additional A with a caret in front of the half symbol. I would like to output as xhtml but would prefer the output using the text encoding as in the html example. Is this possible? Many thanks, John. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL encoding for request
Hello Joerg,
thank you for the quick answer. I will tell my case, resp. show my problem.
I use a search form with the input field searchString. The form action is
OCIprod (a matcher in the cocoon sitemap).
When i look to the log-files the request is URL encoded
(http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=sear
c)
The OCI prod matcher looks like this:
map:match pattern=OCIprod
map:generate type=request/
map:transform type=xslt src=product.xsl/
map:transform type=cinclude/
map:transform type=encodeURL/
map:serialize type=html/
/map:match
In the stylesheet product.xsl i use a cinclude to show the search result
xsl:param name=searchString
select=request:requestParameters/request:[EMAIL PROTECTED]'searchString']/re
quest:value/text()/
...
xsl:if test=$search='result'
cinclude:include
src=cocoon:/searchPageResult?lang={$lang}amp;searchString={$searchString}
/
/xsl:if
Now the param $searchString has the value Gießharz instead of
Gie%C3%9Fharz and can not be found in the database. I get an error on the
searchPage result page like Your search for GieEUR?harz has no hits. If I
call the searchPageResult direct in the browser with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator the decoding is okay. It gives the request
params in their string representation in an XML structure. It knows
nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF
encoded!!)
Maybe it's better to tell us your use case. If you transform the output
of the request generator back into a HTML page with links, the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request generator and a xml-serializer.
The result is:
...
h:requestParameters
h:parameter name=searchString
h:valueGießharz/h:value
/h:parameter
h:parameter name=search
h:valueresult/h:value
...
Why is the parameter searchString transformed? How can i aviod the
transforming? I need this param UTF-8 encoded (like in the calling URL)
Any idea?
Thanks...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL encoding for request
Seems to be more weird than it should be. In your database there is
Gießharz I think and not the URL encoded form of it. Furthermore the
string is correctly in your pipelines, so everything should work. But
some representations of this string are not correct, so that they don't
match. One of them is the search result HTML (Your search for
GieEUR?harz has no hits.). I guess you have to debug around a bit
where the string is Gießharz and where not. It should always be in
this representation internally. What about encoding (ISO-8859-1 vs.
UTF-8)? How does your searchPageResult pipeline look like?
Joerg
On 23.10.2003 09:11, Fleischer Roman wrote:
Hello Joerg,
thank you for the quick answer. I will tell my case, resp. show my problem.
I use a search form with the input field searchString. The form action is
OCIprod (a matcher in the cocoon sitemap).
When i look to the log-files the request is URL encoded
(http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=sear
c)
The OCI prod matcher looks like this:
map:match pattern=OCIprod
map:generate type=request/
map:transform type=xslt src=product.xsl/
map:transform type=cinclude/
map:transform type=encodeURL/
map:serialize type=html/
/map:match
In the stylesheet product.xsl i use a cinclude to show the search result
xsl:param name=searchString
select=request:requestParameters/request:[EMAIL PROTECTED]'searchString']/re
quest:value/text()/
...
xsl:if test=$search='result'
cinclude:include
src=cocoon:/searchPageResult?lang={$lang}amp;searchString={$searchString}
/
/xsl:if
Now the param $searchString has the value Gießharz instead of
Gie%C3%9Fharz and can not be found in the database. I get an error on the
searchPage result page like Your search for GieEUR?harz has no hits. If I
call the searchPageResult direct in the browser with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator the decoding is okay. It gives the request
params in their string representation in an XML structure. It knows
nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF
encoded!!)
Maybe it's better to tell us your use case. If you transform the output
of the request generator back into a HTML page with links, the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request generator and a xml-serializer.
The result is:
...
h:requestParameters
h:parameter name=searchString
h:valueGießharz/h:value
/h:parameter
h:parameter name=search
h:valueresult/h:value
...
Why is the parameter searchString transformed? How can i aviod the
transforming? I need this param UTF-8 encoded (like in the calling URL)
Any idea?
Thanks...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL encoding for request
I think it is a problem for the used searcheDatabase Servlet. For the
result I use a file-generator, but in reality it is a service like:
map:generate
src=http://server1.inside.com?cmd=configurator.SearchProductamp;output=xml
amp;keyword={request-param:searchString}amp;cmid={request-param:cmid}/
When I use UTF-8 encoding for form-encoding and ISO-8859-1 for
container-encoding Gießharz is sending to the servlet. If both are UTF-8
something like Gie~A#harz is sent to the servlet.
I ask the developer of the servlet, what kind of format he needs. He needs
the format Gie%C3%9Fharz and a special information in the http-request
header that the encoding is UTF-8.
Can i send a param with the request header to a generator, or should i use a
HTTP-generator instead?
Thanks
Roman
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 09:41
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Seems to be more weird than it should be. In your database there is
Gießharz I think and not the URL encoded form of it. Furthermore the
string is correctly in your pipelines, so everything should work. But
some representations of this string are not correct, so that they don't
match. One of them is the search result HTML (Your search for
GieEUR?harz has no hits.). I guess you have to debug around a bit
where the string is Gießharz and where not. It should always be in
this representation internally. What about encoding (ISO-8859-1 vs.
UTF-8)? How does your searchPageResult pipeline look like?
Joerg
On 23.10.2003 09:11, Fleischer Roman wrote:
Hello Joerg,
thank you for the quick answer. I will tell my case, resp. show my
problem.
I use a search form with the input field searchString. The form action is
OCIprod (a matcher in the cocoon sitemap).
When i look to the log-files the request is URL encoded
(http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=sear
c)
The OCI prod matcher looks like this:
map:match pattern=OCIprod
map:generate type=request/
map:transform type=xslt src=product.xsl/
map:transform type=cinclude/
map:transform type=encodeURL/
map:serialize type=html/
/map:match
In the stylesheet product.xsl i use a cinclude to show the search result
xsl:param name=searchString
select=request:requestParameters/request:[EMAIL PROTECTED]'searchString']/re
quest:value/text()/
...
xsl:if test=$search='result'
cinclude:include
src=cocoon:/searchPageResult?lang={$lang}amp;searchString={$searchString}
/
/xsl:if
Now the param $searchString has the value Gießharz instead of
Gie%C3%9Fharz and can not be found in the database. I get an error on
the
searchPage result page like Your search for GieEUR?harz has no hits. If
I
call the searchPageResult direct in the browser with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator the decoding is okay. It gives the request
params in their string representation in an XML structure. It knows
nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF
encoded!!)
Maybe it's better to tell us your use case. If you transform the output
of the request generator back into a HTML page with links, the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request generator and a xml-serializer.
The result is:
...
h:requestParameters
h:parameter name=searchString
h:valueGießharz/h:value
/h:parameter
h:parameter name=search
h:valueresult/h:value
...
Why is the parameter searchString transformed? How can i aviod the
transforming? I need this param UTF-8 encoded (like in the calling URL)
Any idea?
Thanks...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL encoding for request
On 23.10.2003 13:35, Fleischer Roman wrote:
I think it is a problem for the used searcheDatabase Servlet. For the
result I use a file-generator, but in reality it is a service like:
map:generate
src=http://server1.inside.com?cmd=configurator.SearchProductamp;output=xml
amp;keyword={request-param:searchString}amp;cmid={request-param:cmid}/
This was already mentioned short time ago: In the sitemap the request
params are available as strings, not in any encoded form. So, you are
right, the parameters are no longer URL encoded for the servlet request.
Tony, didn't you have a similar problem? How have you fix it (if)?
When I use UTF-8 encoding for form-encoding and ISO-8859-1 for
container-encoding Gießharz is sending to the servlet. If both are UTF-8
something like Gie~A#harz is sent to the servlet.
Container encoding should always be ISO-8859-1, independent on the form
handling. This is important for reading text files like properties or
similar.
I ask the developer of the servlet, what kind of format he needs. He needs
the format Gie%C3%9Fharz and a special information in the http-request
header that the encoding is UTF-8.
Can i send a param with the request header to a generator, or should i use a
HTTP-generator instead?
I don't know exactly what's all possible with the proxy generators.
Maybe Tony can jump in? But maybe having the parameters URL encoded
already works.
Joerg
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 09:41
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Seems to be more weird than it should be. In your database there is
Gießharz I think and not the URL encoded form of it. Furthermore the
string is correctly in your pipelines, so everything should work. But
some representations of this string are not correct, so that they don't
match. One of them is the search result HTML (Your search for
GieEUR?harz has no hits.). I guess you have to debug around a bit
where the string is Gießharz and where not. It should always be in
this representation internally. What about encoding (ISO-8859-1 vs.
UTF-8)? How does your searchPageResult pipeline look like?
Joerg
On 23.10.2003 09:11, Fleischer Roman wrote:
Hello Joerg,
thank you for the quick answer. I will tell my case, resp. show my
problem.
I use a search form with the input field searchString. The form action is
OCIprod (a matcher in the cocoon sitemap).
When i look to the log-files the request is URL encoded
(http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=sear
c)
The OCI prod matcher looks like this:
map:match pattern=OCIprod
map:generate type=request/
map:transform type=xslt src=product.xsl/
map:transform type=cinclude/
map:transform type=encodeURL/
map:serialize type=html/
/map:match
In the stylesheet product.xsl i use a cinclude to show the search result
xsl:param name=searchString
select=request:requestParameters/request:[EMAIL PROTECTED]'searchString']/re
quest:value/text()/
...
xsl:if test=$search='result'
cinclude:include
src=cocoon:/searchPageResult?lang={$lang}amp;searchString={$searchString}
/
/xsl:if
Now the param $searchString has the value Gießharz instead of
Gie%C3%9Fharz and can not be found in the database. I get an error on
the
searchPage result page like Your search for GieEUR?harz has no hits. If
I
call the searchPageResult direct in the browser with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator the decoding is okay. It gives the request
params in their string representation in an XML structure. It knows
nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF
encoded!!)
Maybe it's better to tell us your use case. If you transform the output
of the request generator back into a HTML page with links, the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request generator and a xml-serializer.
The result is:
...
h:requestParameters
h:parameter name=searchString
h:valueGießharz/h:value
/h:parameter
h:parameter name=search
h:valueresult/h:value
...
Why is the parameter searchString transformed? How can i aviod the
transforming? I need this param UTF-8 encoded (like in the calling URL)
Any idea?
Thanks...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
RE: URL encoding for request
I believe the RawRequestParameterModule input module may be the answer here.
This will provide access to the original (URLEncoded) parameter. Otherwise
it's like the RequestParameterModule.
Cheers
Con
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 October 2003 10:55
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
On 23.10.2003 13:35, Fleischer Roman wrote:
I think it is a problem for the used searcheDatabase
Servlet. For the
result I use a file-generator, but in reality it is a service like:
map:generate
src=http://server1.inside.com?cmd=configurator.SearchProduct;
amp;output=xml
amp;keyword={request-param:searchString}amp;cmid={request-pa
ram:cmid}/
This was already mentioned short time ago: In the sitemap the request
params are available as strings, not in any encoded form. So, you are
right, the parameters are no longer URL encoded for the
servlet request.
Tony, didn't you have a similar problem? How have you fix it (if)?
When I use UTF-8 encoding for form-encoding and ISO-8859-1 for
container-encoding Gießharz is sending to the servlet. If
both are UTF-8
something like Gie~A#harz is sent to the servlet.
Container encoding should always be ISO-8859-1, independent
on the form
handling. This is important for reading text files like properties or
similar.
I ask the developer of the servlet, what kind of format he
needs. He needs
the format Gie%C3%9Fharz and a special information in the
http-request
header that the encoding is UTF-8.
Can i send a param with the request header to a generator,
or should i use a
HTTP-generator instead?
I don't know exactly what's all possible with the proxy generators.
Maybe Tony can jump in? But maybe having the parameters URL encoded
already works.
Joerg
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 09:41
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Seems to be more weird than it should be. In your database there is
Gießharz I think and not the URL encoded form of it.
Furthermore the
string is correctly in your pipelines, so everything should
work. But
some representations of this string are not correct, so
that they don't
match. One of them is the search result HTML (Your search for
GieEUR?harz has no hits.). I guess you have to debug
around a bit
where the string is Gießharz and where not. It should
always be in
this representation internally. What about encoding (ISO-8859-1 vs.
UTF-8)? How does your searchPageResult pipeline look like?
Joerg
On 23.10.2003 09:11, Fleischer Roman wrote:
Hello Joerg,
thank you for the quick answer. I will tell my case, resp. show my
problem.
I use a search form with the input field searchString. The
form action is
OCIprod (a matcher in the cocoon sitemap).
When i look to the log-files the request is URL encoded
(http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9Fharzse
archMLFB=sear
c)
The OCI prod matcher looks like this:
map:match pattern=OCIprod
map:generate type=request/
map:transform type=xslt src=product.xsl/
map:transform type=cinclude/
map:transform type=encodeURL/
map:serialize type=html/
/map:match
In the stylesheet product.xsl i use a cinclude to show the
search result
xsl:param name=searchString
select=request:requestParameters/request:[EMAIL PROTECTED]'sea
rchString']/re
quest:value/text()/
...
xsl:if test=$search='result'
cinclude:include
src=cocoon:/searchPageResult?lang={$lang}amp;searchString={$
searchString}
/
/xsl:if
Now the param $searchString has the value Gießharz instead of
Gie%C3%9Fharz and can not be found in the database. I get
an error on
the
searchPage result page like Your search for GieEUR?harz
has no hits. If
I
call the searchPageResult direct in the browser with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator the decoding is okay. It gives
the request
params in their string representation in an XML structure. It knows
nothing about an URL encoded string. (%C3%9F is URl
encoded, not UTF
encoded!!)
Maybe it's better to tell us your use case. If you
transform the output
of the request generator back into a HTML page with links,
the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9Fharzsea
rchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request
Re: URL encoding for request
Hello Roman, for the request generator the decoding is okay. It gives the request params in their string representation in an XML structure. It knows nothing about an URL encoded string. (%C3%9F is URl encoded, not UTF encoded!!) Maybe it's better to tell us your use case. If you transform the output of the request generator back into a HTML page with links, the @href will be URL encoded again - at least that should be done by the XML serializer. Joerg On 21.10.2003 14:10, Fleischer Roman wrote: Hello, i have some problems with URL encoding. I call a matcher in this form: http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc h=result... (%C3%9F is the german ss) In the matcher i call a request generator and a xml-serializer. The result is: ... h:requestParameters h:parameter name=searchString h:valueGießharz/h:value /h:parameter h:parameter name=search h:valueresult/h:value ... Why is the parameter searchString transformed? How can i aviod the transforming? I need this param UTF-8 encoded (like in the calling URL) Any idea? Thanks... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
URL encoding for request
Hello, i have some problems with URL encoding. I call a matcher in this form: http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc h=result... (%C3%9F is the german ss) In the matcher i call a request generator and a xml-serializer. The result is: ... h:requestParameters h:parameter name=searchString h:valueGießharz/h:value /h:parameter h:parameter name=search h:valueresult/h:value ... Why is the parameter searchString transformed? How can i aviod the transforming? I need this param UTF-8 encoded (like in the calling URL) Any idea? Thanks... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MySQL encoding problems with connector/J not throug ODBC
hi people i have (as many other people here) encoding problems with greek language i have a mysql dadabase runing on winXP with greek content i try a very simple query using cocoon 2.1 using two different connection methods 1. using MySQLConnector/j (3.0) 2. using ODBC connection in case [1] i dont get greek characters in case [2] i get greek characters corectly but is not the way i want because in production mysql and cocoon will be in a linux box ? in my simple example i just execute a .xsp and a xml serialization i have try the simplest query: esql:connection esql:pooltalanto_work/esql:pool esql:execute-query esql:queryselect * from contact/esql:query esql:results customers esql:row-results customer esql:get-columns/ /customer /esql:row-results /customers /esql:results /esql:execute-query /esql:connection any idea ? thnx --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MySQL encoding problems with connector/J not throug ODBC
What encoding do you use in your DB? I solved all my encoding problems when I changed the encoding of my DB to UNICODE. (But I don't know if this possible in MySQL now. I migrated to PostgreSQL for this reason, a long time ago) /leo On Oct 17, 2003, at 4:02 PM, [EMAIL PROTECTED] wrote: hi people i have (as many other people here) encoding problems with greek language i have a mysql dadabase runing on winXP with greek content i try a very simple query using cocoon 2.1 using two different connection methods 1. using MySQLConnector/j (3.0) 2. using ODBC connection in case [1] i dont get greek characters in case [2] i get greek characters corectly but is not the way i want because in production mysql and cocoon will be in a linux box ? in my simple example i just execute a .xsp and a xml serialization i have try the simplest query: esql:connection esql:pooltalanto_work/esql:pool esql:execute-query esql:queryselect * from contact/esql:query esql:results customers esql:row-results customer esql:get-columns/ /customer /esql:row-results /customers /esql:results /esql:execute-query /esql:connection any idea ? thnx --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: MySQL encoding problems with connector/J not throug ODBC
Came across a similar problem a while back. The solution was to add parameters to the database url, setting the character encoding to the one that java uses. in WEB-INF/cocoon.xconf: datasources jdbc name=databaseName logger=core.datasources.databaseName pool-controller min=5 max=10/ dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEnco ding=Cp1252/dburl userusername/user passwordpassword/password /jdbc /datasources Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ]On Behalf Of leo leonid Sent: 17 October 2003 15:20 To: [EMAIL PROTECTED] Subject: Re: MySQL encoding problems with connector/J not throug ODBC What encoding do you use in your DB? I solved all my encoding problems when I changed the encoding of my DB to UNICODE. (But I don't know if this possible in MySQL now. I migrated to PostgreSQL for this reason, a long time ago) /leo On Oct 17, 2003, at 4:02 PM, [EMAIL PROTECTED] wrote: hi people i have (as many other people here) encoding problems with greek language i have a mysql dadabase runing on winXP with greek content i try a very simple query using cocoon 2.1 using two different connection methods 1. using MySQLConnector/j (3.0) 2. using ODBC connection in case [1] i dont get greek characters in case [2] i get greek characters corectly but is not the way i want because in production mysql and cocoon will be in a linux box ? in my simple example i just execute a .xsp and a xml serialization i have try the simplest query: esql:connection esql:pooltalanto_work/esql:pool esql:execute-query esql:queryselect * from contact/esql:query esql:results customers esql:row-results customer esql:get-columns/ /customer /esql:row-results /customers /esql:results /esql:execute-query /esql:connection any idea ? thnx --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: MySQL encoding problems with connector/J not throug ODBC
for example in UTF case te url will be like this ? : jdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEncoding=UTF-8 On Fri, 17 Oct 2003, Mark H wrote: Came across a similar problem a while back. The solution was to add parameters to the database url, setting the character encoding to the one that java uses. in WEB-INF/cocoon.xconf: datasources jdbc name=databaseName logger=core.datasources.databaseName pool-controller min=5 max=10/ dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEnco ding=Cp1252/dburl userusername/user passwordpassword/password /jdbc /datasources Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ]On Behalf Of leo leonid Sent: 17 October 2003 15:20 To: [EMAIL PROTECTED] Subject: Re: MySQL encoding problems with connector/J not throug ODBC What encoding do you use in your DB? I solved all my encoding problems when I changed the encoding of my DB to UNICODE. (But I don't know if this possible in MySQL now. I migrated to PostgreSQL for this reason, a long time ago) /leo On Oct 17, 2003, at 4:02 PM, [EMAIL PROTECTED] wrote: hi people i have (as many other people here) encoding problems with greek language i have a mysql dadabase runing on winXP with greek content i try a very simple query using cocoon 2.1 using two different connection methods 1. using MySQLConnector/j (3.0) 2. using ODBC connection in case [1] i dont get greek characters in case [2] i get greek characters corectly but is not the way i want because in production mysql and cocoon will be in a linux box ? in my simple example i just execute a .xsp and a xml serialization i have try the simplest query: esql:connection esql:pooltalanto_work/esql:pool esql:execute-query esql:queryselect * from contact/esql:query esql:results customers esql:row-results customer esql:get-columns/ /customer /esql:row-results /customers /esql:results /esql:execute-query /esql:connection any idea ? thnx --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[SOLUTION] RE: MySQL encoding problems with connector/J not throug ODBC
thnx to all of you finaly i have try to insert greek content in MySQL using connect/j i write down all the step i have to do cocoon.xconf dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEncoding=ISO-8859-7/dburl sitemap.xmap in actions: map:action name=set-encoding src=org.apache.cocoon.acting.SetCharacterEncodingAction/ in pipeline: map:act type=set-encoding map:parameter name=form-encoding value=UTF-8/ /map:act the action in site map help me to post greek text from html forms to .xsp where the data are appended to mysql --stavros On Fri, 17 Oct 2003 [EMAIL PROTECTED] wrote: for example in UTF case te url will be like this ? : jdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEncoding=UTF-8 On Fri, 17 Oct 2003, Mark H wrote: Came across a similar problem a while back. The solution was to add parameters to the database url, setting the character encoding to the one that java uses. in WEB-INF/cocoon.xconf: datasources jdbc name=databaseName logger=core.datasources.databaseName pool-controller min=5 max=10/ dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEnco ding=Cp1252/dburl userusername/user passwordpassword/password /jdbc /datasources Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ]On Behalf Of leo leonid Sent: 17 October 2003 15:20 To: [EMAIL PROTECTED] Subject: Re: MySQL encoding problems with connector/J not throug ODBC What encoding do you use in your DB? I solved all my encoding problems when I changed the encoding of my DB to UNICODE. (But I don't know if this possible in MySQL now. I migrated to PostgreSQL for this reason, a long time ago) /leo On Oct 17, 2003, at 4:02 PM, [EMAIL PROTECTED] wrote: hi people i have (as many other people here) encoding problems with greek language i have a mysql dadabase runing on winXP with greek content i try a very simple query using cocoon 2.1 using two different connection methods 1. using MySQLConnector/j (3.0) 2. using ODBC connection in case [1] i dont get greek characters in case [2] i get greek characters corectly but is not the way i want because in production mysql and cocoon will be in a linux box ? in my simple example i just execute a .xsp and a xml serialization i have try the simplest query: esql:connection esql:pooltalanto_work/esql:pool esql:execute-query esql:queryselect * from contact/esql:query esql:results customers esql:row-results customer esql:get-columns/ /customer /esql:row-results /customers /esql:results /esql:execute-query /esql:connection any idea ? thnx --stavros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSPGen. RequestParameter Encoding
Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSPGen. RequestParameter Encoding
On Fri, 19 Sep 2003 09:00:44 +0200 Christoph Strehl [EMAIL PROTECTED] wrote: Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi,Christoph! My experience small in use JSP, if you asked, how inquiry with HTML as Parameter name = query to receive with the coding distinct from ISO-8859-1, I did(made) it as follows: myfile.jsp: ... String requestEnc = request.getCharacterEncoding(); if( requestEnc==null ) requestEnc=ISO-8859-1; String clientEnc = request.getParameter(charset); if( clientEnc==null ) clientEnc=Cp1251; String queryString = new String(request.getParameter(query).getBytes(requestEnc),clientEnc); ... Vladimir Yuryev. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSPGen. RequestParameter Encoding
Tony ( others), Is this the same problem we talked about last week on wsproxy parameter encoding? http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h tml That thread was left hanging. Jeff -Original Message- From: Christoph Strehl [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 12:01 AM To: [EMAIL PROTECTED] Subject: JSPGen. RequestParameter Encoding Hello again, special characters in the request parameter in my JSP are somehow encrypted and even using java.net.URLDecoder.decode() doesn't change that. I tried to set the encoding to ISO-8859-1 but it didn't work at all. Has anyone had a similar problem yet? I am grateful for any hint. Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSPGen. RequestParameter Encoding
Jeff Ramsdale wrote: Tony ( others), Is this the same problem we talked about last week on wsproxy parameter encoding? http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h tml That thread was left hanging. Hrm.. it seems similar, but I'm not too sure. As far as the wsproxy, goes, perhaps we can try to track down where the spaces are being fiddled with. I would be curious to find out if the wsproxy generator is changing the spaces or if it's coming from somewhere else. Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serializing document in UTF-16 encoding
Yury Mikhienko [EMAIL PROTECTED] writes: in serializers section I have: map:serializer logger=sitemap.serializer.text mime-type=text/plain name=UTF_16_text src=org.apache.cocoon.serialization.TextSerializer encodingUTF-16/encoding /map:serializer in pipeline section: map:match pattern=test map:generate src=test.xml/ map:transform src=test.xsl/ map:serialize type=UTF_16_text/ /map:match my test.xml file: ?xml version=1.0 encoding=KOI8-R? text test /text my test.xsl file: ?xml version=1.0? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:template match=text xsl:value-of select=./ /xsl:template /xsl:stylesheet after serializing I get the following document (binary dump) ff fe 0a 00 20 00 42 04 35 04 41 04 42 04 20 00 74 00 65 00 73 00 74 00 0a 00 ^^^- WHY? That's the magic bytes that say that this is UTF_16 - i.e. Unicode. 16-bit (unicode) characters follow: 0x000a - '\n' 0x0020 - ' ' 0x0442 - russian '' 0x0435 - russian '' 0x0441 - russian '' 0x0442 - russian '' 0x0020 - ' ' 0x0074 - t 0x0065 - e 0x0073 - s 0x0074 - t 0x000a - '\n' Try to open this file(binary dump) under WindowsNT/XP notepad and it will show it nicely for you. -- Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Serializing document in UTF-16 encoding
Hi all! I use: cocoon2.0.4 + Tomcat 4.1.24 In first two octets document text body (first 2 bytes) I get the %FF%FE bytes when I try get UTF-16 encoded document (html, text, xml). Why? If I try get the document in other encoding I do not get that bytes (so ok). How I can solve this problem? Or I'm wrong? Many thanks for help! -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serializing document in UTF-16 encoding
Can you send more explanation. What is your pipeline!! You're encountering problem in a java class ? At 13:28 12/09/2003 +0400, you wrote: Hi all! I use: cocoon2.0.4 + Tomcat 4.1.24 In first two octets document text body (first 2 bytes) I get the %FF%FE bytes when I try get UTF-16 encoded document (html, text, xml). Why? If I try get the document in other encoding I do not get that bytes (so ok). How I can solve this problem? Or I'm wrong? Many thanks for help! -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding german http query parameters
I guess you build URLs using request parameters with German letters (something like a href=test.html?myname=Jörg/). This URL is encoded using UTF-8, while you have your documents encoded in ISO-8859-1 (configured at the serializer). If all these guesses are true you have different possibilities: 1. Replace the pure links by a form, the request params are now encoded with ISO-8859-1 too. 2. Change the serializer configuration to UTF-8 and set the form encoding either in the web.xml or using the SetCharacterEncodingAction to UTF-8 (now everything is handled as UTF-8). 3. The links are only for a specific group of matchers in the sitemap and it's enough to use the SetCharacterEncodingAction only for these links. It may not be a mixture of ISO-8859-1 forms and UTF-8 links. If my guesses are not true or the above does not work, you must provide some more information. Especially a sentence like when cocoon sends the request is irritating. There is also some information available at http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding. Joerg [EMAIL PROTECTED] wrote: I produce a webpage with links with German letters in the href attribute. The German letters are not encoded when cocoon sends the request. What shall I do to get this encoding, which is done for the normal text in the HTML-Page -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to change encoding for JSP reader
It seems that by default JSP reader encoding is UTF-8. How it can be changed to other encoding. I have tried like: map:reader name=jsp src=org.apache.cocoon.reading.JSPReader encodingShift_JIS/encoding /map:reader But it seems does not working. Any idea? Regards, Abolhassani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
on Tue, 19 Aug 2003 23:51:20 -0600 (CST) Antonio Gallardo [EMAIL PROTECTED] wrote: Hi: Why the web.xml of cocoon is still having: ?xml version=1.0 encoding=ISO-8859-1? I already changed it to ?xml version=1.0 encoding=UTF-8? and it works. Of course it works, UTF-8 is superset of ISO-8859-1. Regards, Rufio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Joerg Heinicke dijo: Is there any problem with ISO-8859-1 or do you think switching to UTF-8 would be good in general? I think switching all to UTF-8 would be good in general. It is a step ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a deprecated encoding. The IETF recommend UTF-8 instead of any other flavor of ISO-885x-x. Windows changed to UNICODE. Linux is already using UTF-8 as the default encoding. Well, we are moving there. AFAIK we (the world) are currently migrating all the computers and systems to the well know UNICODE. The idea is to allow all of us to mix on the same page code in German, Chinesse, English, etc. without have to worry of the encoding. The migration to UTF-8 is a important issue and since a date (sorry I dont remember the exactly date) any application cannot be considerated internet ready if it does not use UNICODE. Any application using ISO-8859 or similar will be cosiderated non-complaint. I learned about all this stuff (UNICODE, UTF-8, ISO-8859-1) when started in Cocoon I had the common problems generating the HTML pages. My target language (Spanish) needs ñ, Ñ, Á, á. etc. Of course other languages need other symbols that are not well rendered. XHTML 1.0 also has UTF-8 as the default encoding. Java has UTF-8 as the default encoding. Many other applications are migrating or are already migrated. Please read more about unicode at: http://www.unicode.org/standard/WhatIsUnicode.html By the way If we can change to UTF-8 I think many other problems will go away. On the other hand some old applications and browser will not be able to display UTF-8 correctly. I mean maybe IE 3.0 or below. It is part of all this thing. And the is the main reason why we are having problems seeing the copyright symbol on the Cocoon main page of the distribution. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
rufio dijo: Of course it works, UTF-8 is superset of ISO-8859-1. Yep. But the correct would be have all in UTF-8 and not using the deprecated ISO-8859-1 Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Wow, what a /hymn/ on UTF-8 :-) I know the advantages of UTF-8 and even if there is currently no need for switching I did it. The conversion was done hopefully correctly by jEdit. Joerg Antonio Gallardo wrote: Joerg Heinicke dijo: Is there any problem with ISO-8859-1 or do you think switching to UTF-8 would be good in general? I think switching all to UTF-8 would be good in general. It is a step ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a deprecated encoding. The IETF recommend UTF-8 instead of any other flavor of ISO-885x-x. Windows changed to UNICODE. Linux is already using UTF-8 as the default encoding. Well, we are moving there. AFAIK we (the world) are currently migrating all the computers and systems to the well know UNICODE. The idea is to allow all of us to mix on the same page code in German, Chinesse, English, etc. without have to worry of the encoding. The migration to UTF-8 is a important issue and since a date (sorry I dont remember the exactly date) any application cannot be considerated internet ready if it does not use UNICODE. Any application using ISO-8859 or similar will be cosiderated non-complaint. I learned about all this stuff (UNICODE, UTF-8, ISO-8859-1) when started in Cocoon I had the common problems generating the HTML pages. My target language (Spanish) needs ñ, Ñ, Á, á. etc. Of course other languages need other symbols that are not well rendered. XHTML 1.0 also has UTF-8 as the default encoding. Java has UTF-8 as the default encoding. Many other applications are migrating or are already migrated. Please read more about unicode at: http://www.unicode.org/standard/WhatIsUnicode.html By the way If we can change to UTF-8 I think many other problems will go away. On the other hand some old applications and browser will not be able to display UTF-8 correctly. I mean maybe IE 3.0 or below. It is part of all this thing. And the is the main reason why we are having problems seeing the copyright symbol on the Cocoon main page of the distribution. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Joerg Heinicke dijo: Wow, what a /hymn/ on UTF-8 :-) I know the advantages of UTF-8 and even if there is currently no need for switching I did it. The conversion was done hopefully correctly by jEdit. Thanks, I know this is a little change (and maybe meaningless), but I hope it would help us in the standarization. :) Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Encoding of web.xml
Hi: Why the web.xml of cocoon is still having: ?xml version=1.0 encoding=ISO-8859-1? I already changed it to ?xml version=1.0 encoding=UTF-8? and it works. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form encoding and database action
On Sun, Aug 10, 2003 at 11:25:24AM +0200, Joerg Heinicke wrote: Was the issue already solved (I read so many mails yesterday)? web.xml: init-param param-nameform-encoding/param-name param-valueiso-8859-2/param-value /init-param Or if you do not want to override default form encoding for whole cocoon I advise to use SetCharacterEncodingAction in your pipeline. LG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Character encoding
Hi all,
I'm having some trouble with character encoding on
cocoon. Basically, i'm using Jboss-Net to access webservices via SOAP. The Soap
Response has the encoding correct but the presentation (with cocoon) is showing
some characters all garbled.
Here's a simple method i've used to test
this:
public String teste()
{ return " : : : : : :
: : : : : : : : : : : : : ";
These are the special characters i'm having trouble
with. The SOAP encoding is UTF-8, according to the Jboss-Net log.
I've set up a small match on the sitemap to
serialize the response to HTML:
map:match
pattern="soap.html"
map:generate type="serverpages"
src=""/
map:serialize type="html"/
/map:match
teste.xsp has the SOAP call:
?xml version="1.0"
encoding="utf-8"?xsp:page language="java"
xmlns:xsp="http://apache.org/xsp"
xmlns:xsp-request="http://apache.org/xsp/request/2.0"
xmlns:xscript="http://apache.org/xsp/xscript/1.0"
xmlns:soap="http://apache.org/xsp/soap/3.0"
xmlns:xsp-session="http://apache.org/xsp/session/2.0"
page
soap:call url=""http://192.168.0.2:8080/jboss-net/services/Teste">http://192.168.0.2:8080/jboss-net/services/Teste"
ns1:teste
xmlns:ns1="urn:Teste"
/ns1:teste
/soap:call
/page/xsp:page
The output on the browser is showing these strange
characters:
: : : : : : : : : : : : :
: : : : : :
and the Source shows:
page xmlns:xsp="http://apache.org/xsp" xmlns:xsp-session="http://apache.org/xsp/session/2.0"
xmlns:xscript="http://apache.org/xsp/xscript/1.0"
xmlns:soap="http://apache.org/xsp/soap/3.0"
xmlns:xsp-request="http://apache.org/xsp/request/2.0"
soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"soapenv:Body
ns1:testeResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="urn:Teste" testeReturn
xsi:type="xsd:string"Atilde;iexcl; : Atilde;nbsp; :
Atilde;pound; : Atilde;cent; : Atilde;copy; :
Atilde;shy; : Atilde;sup3; : Atilde;micro; :
Atilde;ordm; : Atilde;#129; : Atilde;#128; :
Atilde;#131; : Atilde;#137; : Atilde;#141; :
Atilde;#147; : Atilde;#149; : Atilde;#148; :
Atilde;#154; : Atilde;sect; :
Atilde;#135;/testeReturn
/ns1:testeResponse/soapenv:Body/soapenv:Envelope
/page
I'm not sure why this is happening, but i guess it
has something to do with character encoding that cocoon is applying to the SOAP
response. I've tested the webservice with a small VB.Net console application,
and the output is correct, so the problem is definitely with
cocoon.
Any thoughts on this?
Thanks in advance.
--Nuno LeongPrxia
SI
Desperated about encoding issues
I'm really fond of using ISO-8859-2 encoding. I've set both xml i html serializer to this encoding. That's ok. Every generated paged is displayed properly (also data from database). But I can't get through proper encoding request parameters. The only way I was able to do it correctly was xsp page (but I don't want to be limited to it) and construction like xsp-request:get-parameter form-encoding=iso-8859-2 ... ^^ (I've written about it, but there was no answer. I thought it was a matter of DatabaseAction using, but it wasn't not.) I tried to use SetCharacterEncodingAction: map:act type=set-encoding map:parameter name=form-encoding value=iso-8859-2 / /map:act !-- . and my operation, RequestGenerator for example -- but it also didn't help. Please help, I don't know encoding issue very well, but there is no consistent description (in context of Cocoon). (I've searched polish pl.comp.xml and a lot of people had similar problem, not solved so far). (Additional info: web.xml (of COcoon) form-encoding and container-encoding set to utf-8 !! - the only good working setting with the others I've described earlier.) _ Best regards, Mariusz Sieraczkiewicz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Desperated about encoding issues
Hi: please check this: http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Desperated about encoding issues
On Mon, 2003-08-04 at 15:13, Mariusz Sieraczkiewicz wrote: snip/ (Additional info: web.xml (of COcoon) form-encoding and container-encoding set to utf-8 !! - the only good working setting with the others I've described earlier.) container-encoding must be set to ISO-8859-1 form-encoding should be set to ISO-8859-2 When you do this, you don't need to use the SetCharacterEncodingAction nor form-encoding attribute in XSP's. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Desperated about encoding issues
Hello, container-encoding must be set to ISO-8859-1 form-encoding should be set to ISO-8859-2 Yes, that really helped!!! thank you so much, I'm your deptor. This is what I've been looking for. I may go on holiday now ;-) Best regards - 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 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]
native encoding for xsp page output
Title: native encoding for xsp page output Hi I have posted a question on setting up html serializer with native encoding and I think I kind of understand that part. Within the xsp page, do I need to do something special to ensure such encoding or will the serializer can handle it automatically? I mean if I have a string coming back from my database as UTF-8. For that java string, do I need to explicitly convert it into shift-jis say if I am using japanese? Do I also need to specificly specify the encoding within the xsp xml file? 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.
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]
xsp to generate html page with different encoding?
Title: xsp to generate html page with different encoding? hi I want to have a xsp to render a html page containing a form. The character encoding of the page (presumably this will affect the form as well) is determined by a external parameter, e.g. a request param saying something like en, use english character set or something... How would I do that? I have some Strings coming back from my database and the database strings are already in UTF-8. So would that page automatically convert that into the encoding that I want when I do exprmyStringValue/expr in the final output page? Any help would be appreciated. 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.
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
Re: Form encoding problem in cocoon 2.0.4
Hello Charlene, this is configured in the sitemap in the map:serializers/. Simply add an encodingISO-8859-1/encoding. Example: map:serializer name=html src=org.apache.cocoon encodingISO-8859-1/encoding /map:serializer This has the same effect as the xsl:output encoding=/ declaration in the stylesheet, which is used normally, but should not be used in Cocoon. Joerg Yan, Charlene wrote: Joerg, My case was that I called cocoon from another web application. I had to set the encoding of the calling html page to ISO-8859-1. Now I'm using a htnl page generated by Cocoon. The default meta tag is META http-equiv=Content-Type content=text/html; charset=UTF-8. How or where can I change it to ISO-8859-1 from UTF-8? I've changed the encoding of form.xml, simple-page3html.xsl and sitemap.xmap to ISO-8859-1. It didn't help. What is the source code that sets the meta tag? More specifically, I'm using Cocoon 2.1 M2. you can go to http://localhost:8080/cocoon/samples/mail/sendmail/new.html. On this page, the meta is set to UTF-8. I need to have it changed to ISO-8859-1 to have some accented characters encoded correctly. Thanks in advance for any help. Charlene -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 1:42 PM To: [EMAIL PROTECTED] Subject: Re: Form encoding problem in cocoon 2.0.4 Sorry, but: please don't do this!! Even if ISO-8859-1 is the correct encoding, you shall not add the META tag by hand. The serializer does it for you. So you will simply set the serializer's encoding to ISO-8859-1. But UTF-8 is a super set of ISO-8859-1, so there should be no problem when using it. The working text inputs show this. Now file inputs: Why do they depend on the form encoding? Shouldn't they simply allow to upload a file? Am I missing something? Joerg Yan, Charlene wrote: I had encoding problems with accented characters too. Put META http-equiv=Content-Type content=text/html; charset=iso-8859-1 in your html. iso-8859-1 is the correct one. HTH. Charlene -Original Message- From: Vitor Rui Moreira [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 1:10 PM To: [EMAIL PROTECTED] Subject: Form encoding problem in cocoon 2.0.4 Hi! I'm having a little problem about form encoding. First of all, let me describe the development environment: - Tomcat 4.1.24 - Cocoon 2.0.4 - RedHat 9 Now, the problem: I've got a webpage, which has a form inside. There are several input fields, mostly of type text. There is also a input field of type file. If i click on the submit button, i'll go other page (a xsp one), which displays the contents of the parameters (passed through request and sitemap). While the values of the input which have the type text are correct, the field which has the file type isn't. The error occurs when i use accents (éèá, etc). I'm using UTF-8 encoding on all pages. My tries to solve the problem: 1) changed the web.xml file of cocoon ($TOMCAT_HOME/webapps/cocoon/WEB-INF/web.xml), which i included the form-encoding parameter to UTF-8 2) on the same file, i've tried to set the container-encoding value to UTF-8 (ok, i'm almost desesperating! ;-)) My opinion: Since the text type works correctly and the file type doesn't, i suspect that the form-encoding is not so right after all... but it's only my opinion, based on my cocoon's ignorance... ;-) Critical features: 1) i just can't upgrade the cocoon engine because i've got legacy applications running on that... at least, i can't change right now... :-( F1 wanted! If anyone could help me, i'd appreciate!! TIA -vrm -- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
