On 04/12/2012 13:08, Peter Sparkes wrote:
On 04/12/2012 09:15, Peter Sparkes wrote:
On 04/12/2012 08:46, Francesco Chicchiriccò wrote:
On 04/12/2012 09:40, Peter Sparkes wrote:
I am using C.2.11
I have a CForm implementation and there are, in the xml text,
special characters such as:
£, Â,
On 04/12/2012 09:15, Peter Sparkes wrote:
On 04/12/2012 08:46, Francesco Chicchiriccò wrote:
On 04/12/2012 09:40, Peter Sparkes wrote:
I am using C.2.11
I have a CForm implementation and there are, in the xml text, special
characters such as:
£, Â, ⅗ and â
I am using UTF-8 encoding and such
On 04/12/2012 08:46, Francesco Chicchiriccò wrote:
On 04/12/2012 09:40, Peter Sparkes wrote:
I am using C.2.11
I have a CForm implementation and there are, in the xml text, special
characters such as:
£, Â, ⅗ and â
I am using UTF-8 encoding and such characters in the xml file are correctly d
On 04/12/2012 09:40, Peter Sparkes wrote:
I am using C.2.11
I have a CForm implementation and there are, in the xml text, special
characters such as:
£, Â, ⅗ and â
I am using UTF-8 encoding and such characters in the xml file are
correctly displaced in the CForm and when the form is saved t
I am using C.2.11
I have a CForm implementation and there are, in the xml text, special
characters such as:
£, Â, ⅗ and â
I am using UTF-8 encoding and such characters in the xml file are correctly displaced in the CForm
and when the form is saved they are correctly saved in the xml file.
H
On Mon, Jan 11, 2010 at 10:34 AM, Jos Snellings wrote:
> That is right!
> It is just a confusing situation :-(
> The filter works fine. The init() method of a generator does not give a
> chance to call setCharacterEncoding, as the parsing already happened.
> The good thing is that the code is alre
he encoding of request
> parameters. The plain HttpServletRequest as provided by the servlet
> container is used.
>
> IIRC Tomcat uses ISO-8859-1 by default which follows the recommendation
> of the Servlet API spec:
>
> ~~~~~~~
> SRV.4.9 Request data e
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
~~
SRV.4.9 Request data encoding
Currently, many browsers do not send a char encoding qualifier with the
Content-Type header, leaving open the determination of the character
encoding for reading HTTP requests. The default encoding of a request
the container uses to create the request reader
On Mon, Jan 11, 2010 at 9:12 AM, Jos Snellings wrote:
> 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 b
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
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
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.
Best,
Jos
On Sat, 2010-01-09 at 08:01 +0100, Jos Snellings wrote:
> Hi,
>
> Http
Hi,
HttpServletRequest looks 'imperfect':
Cocoon 3, alpha 2.
A generator accesses the HttpServletRequest in the setup method:
request = HttpContextHelper.getRequest(parameters);
text = request.getParameter("tekst");
The pages, including forms are ecoded in utf-8.
The String 'text' is strange: th
05.01.2009 14:54
Please respond to
users@cocoon.apache.org
To
users@cocoon.apache.org
cc
Subject
Character encoding problem with umlauts (ä ö ü)
Hi!
I have a pipeline that takes a couple of parameters, does an sql query
with
them and returns the result. The problem is that it doesn't
ä, it works.
How could this be fixed, eg. by changing the whole encoding or converting
the parameters somehow?
--
View this message in context:
http://www.nabble.com/Character-encoding-problem-with-umlauts-%28%C3%A4-%C3%B6-%C3%BC%29-tp21291365p21291365.html
Sent from the Cocoon - Users mailing
On Dec 31, 2008, at 1:25 AM, Bertrand Delacretaz wrote:
On Wed, Dec 31, 2008 at 2:11 AM, Mark Lundquist
wrote:
...Cocoon is serving a web page with a bunch of occurrences of the
"ndash"
character (Unicode #8211). These displayed correctly with the old
Saxon,
but now with the new version
On Wed, Dec 31, 2008 at 2:11 AM, Mark Lundquist wrote:
> ...Cocoon is serving a web page with a bunch of occurrences of the "ndash"
> character (Unicode #8211). These displayed correctly with the old Saxon,
> but now with the new version they instead look like this:
>
>â€"...
Did you try
solved! Except that now, I seem to have a new problem with character
encoding...
Cocoon is serving a web page with a bunch of occurrences of the
"ndash" character (Unicode #8211). These displayed correctly with the
old Saxon, but now with the new version they instead look like this:
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
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-8 and work
> 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 for
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.
-8859-1
Peter
On 08.12.2007 13:37, Peter Sparkes wrote:
I am using Cforms in Cocoon 2.1.10 to amend an XML file. The
character encoding is UTF-8
The Euro sign € gets converted to € and UK pound sign £ to £
from the field widget. I am using the saveDocument function from the
samples and have
On 08.12.2007 13:37, Peter Sparkes wrote:
I am using Cforms in Cocoon 2.1.10 to amend an XML file. The character
encoding is UTF-8
The Euro sign € gets converted to € and UK pound sign £ to £
from the field widget. I am using the saveDocument function from the
samples and have set
: Re: Need help Character Encoding :-((
On 12.12.2007 8:37 Uhr, Johannes Textor wrote:
>> Instead of creating a link with you should create a form
>> with hidden elements and a button. The form values will get encoded
>> ISO-8859-1 correctly.
>
> Or you set form-encoding t
On 12.12.2007 8:37 Uhr, Johannes Textor wrote:
Instead of creating a link with you should create a form
with hidden elements and a button. The form values will get encoded
ISO-8859-1 correctly.
Or you set form-encoding to UTF-8 specifically for this pipeline. But given this bug, it is probab
> Unfortunately, creating your own links does not work with special
> characters. While your pages are in ISO-8859-1 and probably work fine
> with all forms and stuff since the server also expects ISO-8859-1, these
> links get *always* UTF-8 encoded so that you have a mismatch on the
> server.
to use for each pipeline like this:
Hope this helps,
Johannes
Original-Nachricht
> Datum: Wed, 12 Dec 2007 13:54:08 +0100
> Von: "Andreas Busch" <[EMAIL PROTECTED]>
> An: users@cocoon.apache.org
> Betreff: RE: Need help Charac
On 12.12.2007 3:09 Uhr, Andreas Busch wrote:
I have a problem with search and paging,
I do search with a post from form and then do pagination with the
search-result.
work's , but if there are some spezial charachters in the search like ü
etc the paging makes problems.
some codesnippets ..
}
};
Thanks in advance
Andreas
-Original Message-
From: Johannes Textor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 11:44 AM
To: users@cocoon.apache.org
Subject: Re: Need help Character Encoding :-((
Hi Andreas,
if something goes wrong with the encoding, it&#
Hi Andreas,
if something goes wrong with the encoding, it's almost certainly a
generator issue. Which generator are you using? Could you post the
corresponding part of sitemap.xmap so we can have a look at your pipeline?
Johannes
Andreas Busch wrote:
Hello,
I have a problem with search an
Hello,
I have a problem with search and paging,
I do search with a post from form and then do pagination with the
search-result.
work's , but if there are some spezial charachters in the search like ü
etc the paging makes problems.
some codesnippets ..
form method="get" action="/op
Hi,
I am using Cforms in Cocoon 2.1.10 to amend an XML file. The character
encoding is UTF-8
The Euro sign € gets converted to € and UK pound sign £ to £
from the field widget. I am using the saveDocument function from the
samples and have set
transformer.setOutputProperty
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 use the fol
September 15, 2006 10:08 AM
> To: users@cocoon.apache.org
> Subject: character encoding: utf-8 and ISO-8859-1 on Mac OS X with Safari
>
> Hi all,
>
> I have a problem with some special characters in a request parameter.
>
> This is the URL with the correct representati
Have you set the form parameter encoding to UTF-8?
(http://wiki.apache.org/cocoon/RequestParameterEncoding).
Peter
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Frank MW
Sent: Friday, September 15, 2006 10:08 AM
To: users@cocoon.apache.org
Subject: character
Hi all,
I have a problem with some special characters in a request parameter.
This is the URL with the correct representation of characters:
http://localhost:8080/webapp/gangyin/vokabelSuchen-rgyaḥ·mtsho.html
Now 'rgyaḥ·mtsho' is what I need in an xslt-stylesheet.
So in the sitemap I have the
On 27.03.2004 11:26, beyaNet Consultancy wrote:
Hi Marc,
I am trying to achieve the following:
1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible.
If it is, the XHTML 1.1 serializer is used, which when view sourced in
the browser you see:
http://www.w3.org/TR/xhtml1/DTD/xh
Hi Marc,
I am trying to achieve the following:
1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible. If it is, the XHTML 1.1 serializer is used, which when view sourced in the browser you see:
Now, as part of the XHTML 1.1 specification you also need to say the following in t
Peter,
sorry for the bad advice then, but you lost me,
pls elaborate on where you see what and how your setup is looking
and what you try to achieve
regards,
-marc=
beyaNet Consultancy wrote:
Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned,
but nothing has really cha
Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned, but nothing has really changed. If I now and change the encoding in the page so that it now reads ISO-8859-1"?> i still only get what is specified in the web.xml document and not in the web-page. Any ideas?
Peter
On 26
beyaNet Consultancy wrote:
Hi,
I am trying to obtain the encoding type as specified in at the top of my
site page when you view source the page. At the moment the encoding type
is specified as:
http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>
I was under the impression that if i used
that i
Hi,
I am trying to obtain the encoding type as specified in at the top of
my site page when you view source the page. At the moment the encoding
type is specified as:
http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>
I was under the impression that if i used
that it would return UTF-8, in
this
On Tue, Dec 02, 2003 at 03:10:51PM +0100, Jakub Kaniewski wrote:
> I have problem with character encoding, when using standart Cocoon
> database actions (like explained in tutorial action-set, that use class
> org.apache.cocoon.acting.DatabaseAddAction). All my Cocoon engine i set
&g
I have problem with character encoding, when using standart Cocoon
database actions (like explained in tutorial action-set, that use class
org.apache.cocoon.acting.DatabaseAddAction). All my Cocoon engine i set
to encode in iso-8859-2 charset, I have no problem in fetching good
encoded record
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
½ as follows:
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 meth
48 matches
Mail list logo
