Peter Sparkes wrote:
The problem turned out to be in web.xml
I amended
form-encoding
ISO-8859-1
To
form-encoding
UTF-8
and now everything is in UTF-8 and works properly
Just a word of caution: make sure you test your forms on every
possible web browser
> Peter Sparkes wrote:
> > The problem turned out to be in web.xml
> > I amended
> > form-encoding
> > ISO-8859-1
> > To
> > form-encoding
> > UTF-8
> > and now everything is in UTF-8 and works properly
&
Thanks for the advice
I have tested with various versions of IE and Firefox and all' fine
Peter
Peter Sparkes wrote:
The problem turned out to be in web.xml
I amended
form-encoding
ISO-8859-1
To
form-encoding
UTF-8
and now everything is in UTF-
On 23.01.2008 03:51, Tobia Conforto wrote:
The problem turned out to be in web.xml
I amended
form-encoding
ISO-8859-1
To
form-encoding
UTF-8
and now everything is in UTF-8 and works properly
Just a word of caution: make sure you test your forms on every
Hi Robin
Robin Wyles schrieb:
> Hi All,
> [...]
>
> So, my questions are
>
> a) Should ServletSource be encoding the URL it receives ? I would've
> thought probably not...
just my personal opinion: No. It would cause SSF to treat URLs different from
other protoco
Hi Rainer,
Thanks very much for your reply... shortly after writing my post I
thought about using an input module, and wrote my own url encoding
input module, not realising there was one already included with
Cocoon - after all these years using Cocoon I've never seen it!
However
(1) Check your web.xml. You should have the init-param "form-encoding"
set to "UTF-8". (It's set by default to ISO-8859-1 on at least some
versions of Cocoon.)
(2) Check your sitemaps, starting from the Cocoon root sitemap. You can
set the encoding of your seria
Petteri Sulonen wrote:
(1) Check your web.xml. You should have the init-param "form-encoding"
set to "UTF-8". (It's set by default to ISO-8859-1 on at least some
versions of Cocoon.)
/var/lib/tomcat5/webapps/cocoon/WEB-INF/web.xml says:
container-
Ok.
I already found out how-to ;-)
http://cocoon.apache.org/2.2/1366_1_1.html 4. Setting Cocoon's
encoding (especially CForms) solved my issue.
Cheers,
Robby
From: Robby Pelssers [mailto:robby.pelss...@ciber.nl]
Sent: Wednesday, May 27, 2009 12:34 PM
To:
ng 'text' is strange: the original content (utf-8) is encoded
once again:
if the string on the form was one character, say 'é', the string has a
length of 4 bytes. It is the result of utf-8 encoding the two byte
character coming from the client. So, a second conversion is happenin
Hello!
I have a small problem with a cocoon application and forms.
The application runs fine on one machine, but for some reason we want to
have a mirror of that machine. Higg Avalability and failover...
And here some more details: The part failing is a simple form build up
via cocoon forms (we
On Tue, 2010-10-05 at 05:26 -0700, mvalencia wrote:
> Hi all
>
> I have a problem using the code of:
> org.apache.cocoon.mail.transformation.SendMailTransformer, when I send an
> email, target user always receive the field body with strange characters, so
> seemd bad encodi
...@juntadeandalucia.es
It's seems that all text lose encoding, but I have checked that emails have
subject correct and bad encoding on body field.
I load a test email:
http://old.nabble.com/file/p29889393/test-email.txt test-email.txt
--
View this message in context:
http://old.nabble.com/pr
nderlying
server has the locale UTF8_ES?
> It's seems that all text lose encoding, but I have checked that emails have
> subject correct and bad encoding on body field.
> I load a test email:
> http://old.nabble.com/file/p29889393/test-email.txt test-email.txt
Hmm, let us do
r, really is
@version $Id: SendMailTransformer.java 607381 2007-12-29 05:42:58Z
vgritsenko) then the field body has lost the encoding.
However I come back to do the test that you tell me.
--
View this message in context:
http://old.nabble.com/problem-encoding-using-SendMailTransformer-tp29886850p29897843.
ail (It is a class that extend from AbstractSAXTransformer, really is
> @version $Id: SendMailTransformer.java 607381 2007-12-29 05:42:58Z
> vgritsenko) then the field body has lost the encoding.
>
> However I come back to do the test that you tell me.
can be the problematic part, si
defined on web.xml of Cocoon
Application:
SetCharacterEncoding
es.sadesi.filter.SetCharacterEncodingFilter
encoding
UTF-8
..
SetCharacterEncoding
DispatcherServlet
.
I have test put encoding on HTML FORM, so with the parameter:
accept
, SetCharacterEncodingFilter is a filter defined on web.xml of Cocoon
Application:
SetCharacterEncoding
es.sadesi.filter.SetCharacterEncodingFilter
encoding
UTF-8
..
SetCharacterEncoding
DispatcherServlet
.
I have test put
Hi Andre
I load file with HTTP header of web page to send email:
http://old.nabble.com/file/p29914700/HTTP_header_Email-send.txt
HTTP_header_Email-send.txt
I see that Accept-Charset parameter contains UTF-8 and in query-string data
are codified right.
Besides I check encoding browser is UTF-8
Hello, I think you need to set URIencoding in your tomcat connector:
http://tomcat.apache.org/tomcat-6.0-doc/config/http.html#Common_Attributes
|URIEncoding|
This specifies the character encoding used to decode the URI bytes,
after %xx decoding the URL. If not specified, ISO-8859-1 will be
rEncodingFilter in your code base.
>
>
> Yes, SetCharacterEncodingFilter is a filter defined on web.xml of Cocoon
> Application:
>
> SetCharacterEncoding
>
> es.sadesi.filter.SetCharacterEncodingFilter
>
> encoding
> UTF-8
The form used get method, because with the post method not work the
"request-param" of Cocoon.
--
View this message in context:
http://old.nabble.com/problem-encoding-using-SendMailTransformer-tp29886850p29931504.html
Sent from the Cocoon - Users mailing list archive at
Hi Charles
I have configured the parameter URIEncoding to UTF-8, even I used the
parameter useBodyEncodingForURI but I go on with the same problem.
--
View this message in context:
http://old.nabble.com/problem-encoding-using-SendMailTransformer-tp29886850p29931532.html
Sent from the Cocoon
the garbled characters and then went
back through the method calls to find the point where they were created.
In my case it was the tomcat Connector object using its default
character encoding.
On 10/8/10 8:02 AM, Charles Yates wrote:
Hello, I think you need to set URIencoding in your tomcat
e is
text/plain body set with MimeMessage variable and when mime-type is another
value the body field set with MimeBodyPart variable.
It seem that MimeMessage variable does not manage encoding correctly.
Anyway for me the matter is fixed.
Thanks all.
--
View this message in context:
http://ol
Hi,i am using cocoon 2.2 and i want to set the encoding for the xml serializer
dynamically depending on the return value of a previous action.for example like
this
...For the moment i can only set the encoding in the bean definition... Is
that possible? Thanks
]
Sent: Sonntag, 4. Dezember 2011 13:02
To: users@cocoon.apache.org
Subject: XML-> PDF bad encoding
Appologize in front if this is somewhere explained, but as I'm not guru in
Cocoon, after 5 days of google search and testing all possible combinations,
haven't found a solution. So
l character (ĐđČčĆć in unicode notation) remain as "#" signs).
>
> Is this really a bug or there is a solution, so please once more apologize
> for some dumb entries in this issue, but pretty lost in this case.
> Regards,
> Funky
> --
> View this message in conte
4. Dezember 2011 13:02
> To: users@cocoon.apache.org
> Subject: XML-> PDF bad encoding
>
>
> Appologize in front if this is somewhere explained, but as I'm not guru in
> Cocoon, after 5 days of google search and testing all possible
> combinations,
> haven't fou
when I implement a
>> feature
>> some national character (ĐđČčĆć in unicode notation) remain as "#"
>> signs).
>>
>> Is this really a bug or there is a solution, so please once more
>> apologize
>> for some dumb entries in this issu
Hi all,
Just wanted to have a short discussion on an issue that I wasted quite some
hours on. Let me first explain that I configured my cocoon block with
following two properties as per http://cocoon.apache.org/2.2/1366_1_1.html :
org.apache.cocoon.containerencoding=UTF-8
org.apache.cocoon.for
Is there any way to dynamically set the encoding of output on a serializer,
specifically the XML serializer? I have a customer who is having trouble
handing UTF-8 output from my application (he is using Lotus Notes), and
would like me to supply a different encoding. I can just create a
Hi,
I have a big problem!! I have changed "enctype" to "multipart/form-data"
in form definition and this caused problems with encoding characters -
instead of UTF-8 chars I receive "?"s.
Of course I have the form-encoding init parameter set to UTF-8. I tried
setti
Hi!
I am having a bit of a problem when trying to output UTF-8 encoded
(Japanese) html directly through. Everything works fine when I use the
default File generator. The problem only occurs when using the HTML
generator.
Am I doing something wrong, or is this a bug?
Thanks!!
Here is a simple
Hi!
I am having a bit of a problem when trying to output UTF-8 encoded
(Japanese) html directly through. Everything works fine when I use the
default File generator. The problem only occurs when using the HTML
generator.
Am I doing something wrong, or is this a bug?
Thanks!!
Here is a simple
Hi!
I am having a bit of a problem when trying to output UTF-8 encoded
(Japanese) html directly through. Everything works fine when I use the
default File generator. The problem only occurs when using the HTML
generator.
Am I doing something wrong, or is this a bug?
Thanks!!
Here is a simple
Brent L Johnson wrote:
Is there a way I can encode the {request-param:paramname} in
a sitemap? I'm trying to use a request parameter in
the HTMLGenerator as part of a GET request, but using
{request-param:paramname} decodes the parameter. So
if the parameter has a space - instead of putting a %2
Yeah I've searched around the archives quite a bit... and
I've found some hits on the HTMLGenerator and on encoding
parameters but nothing that's quite the same as what
I'm looking for.
But I'll keep looking.. and I'll focus some on the input
module and see if tha
: Geoff Howard [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 07, 2004 6:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Encoding Params in the Sitemap
>
>
> Brent L Johnson wrote:
>
> > Is there a way I can encode the {request-param:paramname} in a
> > sitemap?
o the mailing list.
I used his patched version and it works just
fine now.
Is his patch included in CVS now?
Thanks,
- Brent
> -Original Message-
> From: Geoff Howard [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 07, 2004 6:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: En
y Tang [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 09, 2004 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Encoding Params in the Sitemap
>
>
> It was - and the solution was to use the
> RawRequestParameterModule. I found some docs in the Wiki for
> using this... but
Brent L Johnson wrote:
Dangit - please ignore that slappy email address. This
is an email address I setup specifically to test
my webmail functionality. For some reason Outlook
keeps defaulting replies to this list to that
email address.
My apologies...
no problemo Slappy !
;)
Jorg
Hi!!!
I know this is a issue largely discussed here, but
for me the tips that I read didn't work.
I already try to set the current encoding in the
sitemap, like you can see here:
pool-grow="4"
pool-max="32" pool-min="4"
src="&qu
On 02.03.2004 20:04, Stefan Geelen wrote:
Hi,
I build a webpage with default charset=ISO-8859-1" encoding.
I need to include another .xml file built in utf-16 encoding:
Example currently unavailable
The result is :
..
ÿþ<
On Tue, 2004-03-02 at 20:04, Stefan Geelen wrote:
> Hi,
>
> I build a webpage with default charset=ISO-8859-1" encoding.
>
> I need to include another .xml file built in utf-16 encoding:
>
>encoding="UTF-16">
>
>
Hi,
How can i generate from an xml file which is "ISO-8859-15" encoded?
I've got the following error :
Invalid encoding name "ISO-8859-1"
thanks in advance
-
To unsubscribe, e-mail: [EMAIL
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". T
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
Title: RE: dynamic "encoding" for html serialiser?
So you are saying I could do some
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
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
>
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
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
ly: 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().
>
>
> ...
>
> src="org.apache.cocoon.serialization.XMLSerializer" ...>
> encoding1
>
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 impleme
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 implement
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 implemente
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:
>
>
> form-encoding
> iso-8859-2
>
Or if you do not want to override default form encoding for whol
Was the issue already solved (I read so many mails yesterday)?
web.xml:
form-encoding
iso-8859-2
Joerg
Mariusz Sieraczkiewicz wrote:
Hello,
I used to use
in XSP code in order to get properly encoded string in Polish.
How can I (if I can, of course) achieve similar effect
using one of
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
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
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
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
this
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 addit
Hi Abbas,
I think you should check
the settings in your web.xml (container-encoding
and form-encoding) and the
serializer settings in the sitemap.xmap. I think I remember having some
encoding-problems with CForms. I guess cocoon will provide content encoded in
the format set here. And
In your web.xml, you have the form-encoding configured correctly??
For example,
form-encoding
utf8
Regards Ard
>
>
> Hello,
>
> We are using Cocoon 2.1.9 (Windows XP/Tomcat 5.0.30 and Suse 9/Tomcat
> 5.0) and we have a problem with the encoding when passi
Yes, the form encoding is well configured.
We are able to retrieve correctly the accentuated characters from the
form in the flowsript.
The problem occurs when we pass the bean from the flowscript to the
component.
Ard Schrijvers wrote:
In your web.xml, you have the form-encoding
But is then the problem not just in your
myComponent? What does it do?
Ard
Yes,
the form encoding is well configured.We are able to retrieve correctly the
accentuated characters from the form in the flowsript.The problem occurs
when we pass the bean from the flowscript to the
ava object.
Ard Schrijvers wrote:
But is then the problem not
just in your myComponent? What does it do?
Ard
Yes, the form encoding is well configured.
We are able to retrieve correctly the accentuated characters from the
form in the flowsript.
The problem occurs when w
the problem not just in your myComponent? What does it do?
Ard
Yes, the form encoding is well configured.
We are able to retrieve correctly the accentuated characters from the form in
the flowsript.
The problem occurs when we pass the bean from the flowscript to the component.
Ard Schrij
wscript to java object.
Ard Schrijvers wrote:
But is then the problem not just in your myComponent? What does it do?
Ard
Yes, the form encoding is well configured.
We are able to retrieve correctly the accentuated characters from the form in
the flowsript.
The problem occurs when we pass
omponent.
> >If I do a myBean.getName() in the flowscript for exemple,
> the string is well encoded.
> >But if i do the same call in my component, the string is no
> more well encoded.
> >I think it's more a problem with the Rhino layer when
> passing the objects from f
wrote:
But is then the problem not just in your myComponent? What
does it do?
Ard
Yes, the form encoding is well configured.
We are able to retrieve correctly the accentuated characters
from the form in the flowsript.
The problem occurs when we pass the bean from
Hi cocooners !
I'va a little pb with upload widget and encoding.
Explanations:
i use upload widget in a form to upload ( ;-) , it sounds good!) an file
which is an XML file
XML file example :
in my flowscript, i try to handle the xml stream and give it to a cocoon
pipe.
i us
I have a flowscript that handles a simple contact form, sending an email
for each successful submit:
var form = new Form('cocoon:/contact.form')
form.showForm('contact.jx')
var fields = getFormFields(form)
var m = cocoon.getComponent(Packages.org.apache.cocoon.mail.MailSender.ROLE)
m.setSmtpHost
e (and the remote server tell
I use a "Mozilla/5.0 (Windows... Firefox/2.0.0.3" user-agent) when I
try the web service directly in a browser (with the very same parameters).
Why do you need a specific encoding? Do your request or response got
parsed wrongly? There is a discour
Hi Joerg
Joerg Heinicke a ecrit le 10/04/07 0:32:
Why do you need a specific encoding? Do your request or response got
parsed wrongly? There is a discouraging comment in the
WebServiceProxyGenerator [1, line 115 and following]:
Can you tell the actual error you want to solve? That might make
able to handle
them. But of course it needs a hint how to parse the XML, which is
normally the XML declaration. But maybe it makes sense to add a
parameter for response parsing encoding to the generator for such cases
where there is no hint in the response.
Joerg
[1] http://svn.apache.org/
Are you using Tomcat? If you do some searches, you'll probably turn up
other postings on this topic. I can't remember all the ins & outs, but
supposedly the browsers incorrectly supply encoding information in their
requests to Tomcat (ours were POST requests), and Tomcat by defau
On 23.06.2004 23:44, Christopher Painter-Wakefield wrote:
Are you using Tomcat? If you do some searches, you'll probably turn up
other postings on this topic. I can't remember all the ins & outs, but
supposedly the browsers incorrectly supply encoding information in their
requ
I'm not familiar with that setting. Where does it live?
-Christopher
Joerg Heinicke <[EMAIL PROTECTED]>
06/26/2004 10:27 AM
Please respond to users
To: [EMAIL PROTECTED]
cc:
Subject: Re: UTF-8 and Encoding Problems
On
me searches, you'll probably
turn up other postings on this topic. I can't remember all the ins
& outs, but supposedly the browsers incorrectly supply encoding
information in their requests to Tomcat (ours were POST requests),
and Tomcat by default assumes ISO-8859-1 encoding for the s
Cool, thanks!
Joerg Heinicke <[EMAIL PROTECTED]>
06/29/2004 09:04 PM
Please respond to users
To: [EMAIL PROTECTED]
cc:
Subject: Re: UTF-8 and Encoding Problems
On 27.06.2004 22:28, Christopher Painter-Wakefield wrote:
>
On Wed, 21 Jul 2004 [EMAIL PROTECTED] wrote:
i have solve my problem touching SQLTransformer.java
and seting default encoding to UTF-8
is this a case for bugzilla or not?
(must encoding be configurable from sitemap?)
-
/**
* configure
*/
public void configure
Björn Voigt wrote:
Hello cocooners,
I use the velocity-generator to load an utf-8 encoded XML-File and fill
in a UTF-8 encoded sitemap-parameter. OK the is parameter filled in
correctly
but the file seems to be decoded in ISO-8859.
Is it possible or how is it possible to configure the generator
Hello there cocoon community,
I've got some strange problems with form submiting and utf-8 encoding,
so i'm trying to write something in utf-8 in my form ( try it yourself
- http://dev.vzg.lt/Add/ ) and see what has been submited. After
submit I get some strange and really non utf-8
ut I'm
getting on my browser is still incorrect. Any ideas? I even modified
the container encoding in the web.xml file and had no luck.
Thanks,
Mike
Lopke
-Original Message-From: Lopke, Michael
Sent: Friday, January 21, 2005 10:20 AMTo:
users@cocoo
Lopke, Michael wrote:
Hi,
Hi.
Is your database supports UTF-8 encoding? I know I had this problems
with postgres if I don't create the database with -E unicode parameter.
Rgds.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Hi,
Yes the database supports UTF-8 encoding. Its oracle 9i. I can use the same
driver and data base with a standard java servlet and the data works. Also, I
am able to print the data out to a file with some java code I inserted into the
xsp page using the tag.
I've deployed cocoon
Title: Message
ï
We experienced a similar problem with the character encoding on
the http request processed by Cocoon. We also were attempting to use UTF-8
encoding but found that the encoding would always default to ISO-8859-1. Looking at the request in a debugger, we found that
the
utf-8
encoding
We experienced a similar problem with the character encoding
on the http request processed by Cocoon. We also were attempting to use UTF-8
encoding but found that the encoding would always default to ISO-8859-1. Looking at the request in a debugger, we found that
Hello,
Can You tell me if it is a known issue that matchers malform
encoding of nonUS characters? I have no problems when I run Cocoon
2.1.5.1 on Windows, but when I try on Linux with Cocoon 2.1.6 then
things go wrong.
If there are two matches
.
When using request generator the correct string (olá) is presented in
the generated xml document.
I've tried changing serializer encoding, container encoding, etc...but
until now a didn't find any solution to solve this problem.
Does anyone has any idea ho
Hi Christofer,
make sure the encoding you use in your files & form definition matches
the form-encoding parameter of your servlet engine, specified in web.xml
- I'm devoloping on linux, using utf-8 as default file encoding + form
encoding and had to set the form-encoding param to utf-8
Hi Andreas,
I'd bet that the screwed umlaut arises already at the level of the multisearch
generator, can you confirm this? (by looking at search.xml?cocoon-view=debug
and checking the source code).
If this is indeed the problem, your generator is not using the correct encoding
to decod
forms are ecoded in utf-8.
> The String 'text' is strange: the original content (utf-8) is encoded
> once again:
> if the string on the form was one character, say 'é', the string has a
> length of 4 bytes. It is the result of utf-8 encoding the two byte
> character
2010/1/10 Jos Snellings
> This is not a specific cocoon issue, I believe. It probably has to do
> with Tomcat 5.5.27.
> request.setCharacterEncoding simply does not work; it does not change a
> thing.
> request.getCharacterEncoding returns nothing.
>
You have to call request.setCharacterEncoding
Thanks, I will try CharacterEncodingFilter!
I will lookup in the code were filtering takes place, because the
problem is rather that it looks like the form data are filtered twice.
In addition, do I remember right that there used to be a cocoon servlet
setting,
form-encoding
t there used to be a cocoon servlet
> setting,
>
>form-encoding
>UTF-8
>
>
> Cheers, thanks for the hint. I will post the result... I will certainly
> not be the only person who is confronted with this problem.
>
There are so many places to set the
;
>
> The pages, including forms are ecoded in utf-8.
> The String 'text' is strange: the original content (utf-8) is encoded
> once again:
> if the string on the form was one character, say 'é', the string has a
> length of 4 bytes. It is the result of utf-8
This, to notify you that the solution you suggested works fine:
So, for all cocoon users: if you are experiencing problems with the
character encoding of POST form data (which is very likely to occur):
the problem is generally cured by
Inserting the following code in web.xml
encodingFilter
301 - 400 of 622 matches
Mail list logo
