Greg,
On 3/31/22 12:17, Christopher Schultz wrote:
Greg,
On 3/29/22 13:41, gelo1234 wrote:
Have you also tried HTMLT or XHTMLT Serializers?
Default HTMLSerializer cannot handle some unicode characters:
https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc
Hmm. Are the HTMLT
Hi,
To help isolate the issue, could you test with a simpler pipeline with
only generator/single simple XSLT/xml serializer ?
Cédric
Le 31/03/2022 à 17:54, Christopher Schultz a écrit :
Cédric,
On 3/29/22 12:52, Cédric Damioli wrote:
Do you use Xalan as XSLT Processor ?
If so, I remember
Greg,
On 3/31/22 12:13, Christopher Schultz wrote:
On 3/29/22 13:37, gelo1234 wrote:
Hello Chris,
I think you will not get any icon-type character on output without
using proper font rendering - like Emoji support? Emoji might not be
supported by default in Cocoon.
This isn't a
Greg,
On 3/29/22 13:41, gelo1234 wrote:
Have you also tried HTMLT or XHTMLT Serializers?
Default HTMLSerializer cannot handle some unicode characters:
https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc
Hmm. Are the HTMLT / XHTMLT serializers built-in? I have disabled all
Greg,
On 3/29/22 13:37, gelo1234 wrote:
Hello Chris,
I think you will not get any icon-type character on output without using
proper font rendering - like Emoji support? Emoji might not be supported
by default in Cocoon.
This isn't a font-rendering issue; it's just ... wrong. Either the
Cédric,
On 3/29/22 12:52, Cédric Damioli wrote:
Do you use Xalan as XSLT Processor ?
If so, I remember https://issues.apache.org/jira/browse/XALANJ-2617
which could be a cause of your issue.
I resolved it on my side years ago by compiling my own patched version
> of Xalan.
I'm using
Chris,
Have you also tried HTMLT or XHTMLT Serializers?
Default HTMLSerializer cannot handle some unicode characters:
https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc
Greetings,
Greg
wt., 29 mar 2022 o 19:37 gelo1234 napisał(a):
> Hello Chris,
>
> I think you will not get
Hello Chris,
I think you will not get any icon-type character on output without using
proper font rendering - like Emoji support? Emoji might not be supported by
default in Cocoon.
So this might be the reason why you get HTML entities instead of
Emoji-icons.
Also notice:
Do you use Xalan as XSLT Processor ?
If so, I remember https://issues.apache.org/jira/browse/XALANJ-2617
which could be a cause of your issue.
I resolved it on my side years ago by compiling my own patched version
of Xalan.
For "markers", you may use labels on your sitemap steps associated
Cédric,
On 3/29/22 12:06, Cédric Damioli wrote:
Could you provide more details ?
How is your XML processed before outputting the wrong UTF-8 sequence ?
It's somewhat straightforward:
https://source/; />
attempting to do everything with UTF-8 in Cocoon 2.1.11. I have
a servlet generating XML in UTF-8 encoding and I have a pipeline
with a few transforms in it, ultimately serializing to XHTML.
If I have a Unicode character in the XML which is outside of the
BMP, such as this one: (that's an American
,
Some additional information at the end.
On 10/30/18 11:58, Christopher Schultz wrote:
All,
I'm attempting to do everything with UTF-8 in Cocoon 2.1.11. I have
a servlet generating XML in UTF-8 encoding and I have a pipeline
with a few transforms in it, ultimately serializing to XHTML.
If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Some additional information at the end.
On 10/30/18 11:58, Christopher Schultz wrote:
> All,
>
> I'm attempting to do everything with UTF-8 in Cocoon 2.1.11. I have
> a servlet generating XML in UTF-8 encoding and I hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm attempting to do everything with UTF-8 in Cocoon 2.1.11. I have a
servlet generating XML in UTF-8 encoding and I have a pipeline with a
few transforms in it, ultimately serializing to XHTML.
If I have a Unicode character in the XML which
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
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
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
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 â
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.
However, I am building another CForm, within the same Cocoon
application, this time using the JXTemplate Generator
Hi,
C2.11, I moved my app from one server to another, which resulted some
pages to broke that is scands won't encode properly.
I have this in my sitemap:
map:match pattern=linkki/html/*
map:generate src=cocoon:/linkki/{1} type=text
/map:generate
!--map:transform type=xslt src=linkki.xslt/--
The one that does not work has following encoding in head
meta content=text/html; charset=ISO-8859-1 http-equiv=Content-Type
Robby
-Original Message-
From: m...@digikartta.net [mailto:m...@digikartta.net]
Sent: Thursday, September 20, 2012 9:23 AM
To: users@cocoon.apache.org
Subject
following encoding in head
meta content=text/html; charset=ISO-8859-1
http-equiv=Content-Type
Robby
-Original Message-
From: m...@digikartta.net [mailto:m...@digikartta.net]
Sent: Thursday, September 20, 2012 9:23 AM
To: users@cocoon.apache.org
Subject: more encoding problems
Hi,
C2.11
and did you explicitly
set the encoding?
http://cocoon.apache.org/2.1/userdocs/default/html-serializer.html
http://cocoon.apache.org/2.1/userdocs/xhtml-serializer.html
-Original Message-
From: m...@digikartta.net [mailto:m...@digikartta.net]
Sent: Thursday, September 20, 2012 10:11 AM
Hi Mika,
Your page declares utf-8 as a character set, but the text you send is not
in utf-8. Hence the question mark
characters.
Question 1: is it the same database that is accessed? (or rather, a copy)
Question 2: what is the database url?
Cheers,
Jos
On Thu, Sep 20, 2012 at 9:22 AM,
Hi Jos,
yep, that's right, the text seems not to be utf-8.
Same problem occurs in another page where the text not working comes
from flowscript.
1) No it's not, it's a copy. But you can verify everything is ok in
http://88.148.163.59/cocoon/palaute_app/linkki/1059 (database reader).
Seems to
this out. Even this one will fail.
sitemap:
map:match pattern=koe
map:generate type=serverpages src=koe.xsp
/map:generate
map:serialize type=xml/
/map:match
koe.xsp:
?xml version=1.0 encoding=utf-8?
xsp:page language=java
xmlns:xsp=http://apache.org/xsp;
page
Äiti/Äiti
/page
/xsp:page
=xml/
/map:match
koe.xsp:
?xml version=1.0 encoding=utf-8?
xsp:page language=java
xmlns:xsp=http://apache.org/**xsp http://apache.org/xsp
page
Äiti/Äiti
/page
/xsp:page
Works locally.
- mika -
On Thu, 20 Sep 2012 15:14:35 +0300, m...@digikartta.net wrote:
Hi Jos,
yep
if you are referring to this part, it's like this:
init-param
param-namecontainer-encoding/param-name
param-valueISO-8859-1/param-value
/init-param
!--
Set form encoding. This will be the character set used to decode
request
parameters. If not set the ISO
Just wanted to have a look.
I compared to with what I had, and it is the same. No luck.
On Thu, Sep 20, 2012 at 3:18 PM, m...@digikartta.net wrote:
if you are referring to this part, it's like this:
init-param
param-namecontainer-**encoding/param-name
param-valueISO-8859-1
, August 29, 2012 12:37 PM
To: users@cocoon.apache.org
Subject: encoding issue
Hi.
C2.11 and CForms. I loose scands after binding, they are all replaced
by a question mark. I have read all the sites possible to resolve this,
but without luck. All is UTF-8, except container-encoding iso-8859-1
, August 29, 2012 12:37 PM
To: users@cocoon.apache.org
Subject: encoding issue
Hi.
C2.11 and CForms. I loose scands after binding, they are all replaced
by a question mark. I have read all the sites possible to resolve this,
but without luck. All is UTF-8, except container-encoding iso-8859-1
: encoding issue
Hi.
C2.11 and CForms. I loose scands after binding, they are all
replaced
by a question mark. I have read all the sites possible to resolve
this,
but without luck. All is UTF-8, except container-encoding
iso-8859-1.
Changing container to utf-8 will change the question marks
Problem is I'm not using C2.1.x anymore so it's really hard to properly help
you out here.
I know that for C2.2 we have to set 2 properties:
org.apache.cocoon.containerencoding=utf-8
org.apache.cocoon.formencoding=utf-8
As a side note: Check encoding in your xslt's
xsl:output method=xml
to
properly help you out here.
I know that for C2.2 we have to set 2 properties:
org.apache.cocoon.containerencoding=utf-8
org.apache.cocoon.formencoding=utf-8
As a side note: Check encoding in your xslt's
xsl:output method=xml version=1.0 encoding=UTF-8
indent=yes/
Robby
-Original Message
Hi.
C2.11 and CForms. I loose scands after binding, they are all replaced
by a question mark. I have read all the sites possible to resolve this,
but without luck. All is UTF-8, except container-encoding iso-8859-1.
Changing container to utf-8 will change the question marks to some other
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
I did found a workaround by the way…
If you add an extra request parameter called cocoon-form-encoding and set it to
utf-8 it will work
Snippet from RequestProcessor.java:
protected Environment getEnvironment(String uri,
HttpServletRequest req
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 here is brief problem description
When I test file generation from WEB URL, (source-output
entries in this issue, but pretty lost in this case.
Regards,
Funky
--
View this message in context:
http://old.nabble.com/XML-%3E-PDF-bad-encoding-tp32911752p32911752.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
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 context:
http://old.nabble.com/XML-%3E-PDF-bad-encoding-tp32911752p32911752
]
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 here is brief
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 context:
http://old.nabble.com/XML-%3E-PDF-bad-encoding-tp32911752p32911752.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Laurent,
On 12/17/2010 11:25 AM, Laurent Medioni wrote:
Have a look at http://wiki.apache.org/tomcat/FAQ/CharacterEncoding I
think the comment you refer to tries to say that if no
charset/encoding is set when producing a response then assume
can consume in my XSLT. However, this is appearing as:
?xml version=1.0 encoding=ISO-8859-1?html...etc
depite the fact that the sitemap.xmap says very clearly:
map:serializer logger=sitemap.serializer.xml
mime-type=application/xml name=xml
src
which
I take for the framework is
http://www.ucc.ie/en/old-design-base/
and that says quite clearly
meta http-equiv=Content-Type content=text/html; charset=UTF-8 /
Something, somewhere is sticking a bogus encoding in the works.
///Peter
What is your
init-param
param-namecontainer-encoding/param-name
param-valueUTF-8/param-value
/init-param
In web.xml ?
• This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use
On 17/12/10 15:37, Laurent Medioni wrote:
What is your
init-param
param-namecontainer-encoding/param-name
param-valueUTF-8/param-value
/init-param
In web.xml ?
Interesting. ISO-8859-1, because
!--
Set encoding used by the container. If not set the ISO-8859-1 encoding
Setting container-encoding to UTF-8 enables you to share your servlet container
(keeping its Latin1 default) with other applications not supporting UTF-8 (and
not fiddling with encodings...), if relevant (we had the case...).
Have a look at http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
I
Hi,
have you tried:
serialize type=xhtml status-code=200 ...
...
encoding{charsetEncoding}/encoding
...
/serialize
?
Laurent
From: Ali Mahdoui [mailto:mahd...@hotmail.de]
Sent: dimanche, 7. novembre 2010 12:10
To: Cocoon users; d
Hi,no that does not help (and the syntax is not allowed in the schema of the
sitemap)thanksAli
Subject: RE: Set Encoding for XMLSerializer dynamically
Date: Mon, 8 Nov 2010 12:56:11 +0100
From: lmedi...@odyssey-group.com
To: users@cocoon.apache.org
Hi,
have you tried:
serialize type
So this changed from 2.1, pity…
From: Ali Mahdoui [mailto:mahd...@hotmail.de]
Sent: lundi, 8. novembre 2010 13:08
To: Cocoon users
Subject: RE: Set Encoding for XMLSerializer dynamically
Hi,
no that does not help (and the syntax is not allowed
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 serialize type=xhtml status-code=200 encoding={charsetEncoding}/
...For the moment i can only set the encoding in the bean
of SendMailTransformer.java I see that when mime-type 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
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
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 Nabble.com
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
-valueUTF-8/param-value
/init-param
/filter
..
filter-mapping
filter-nameSetCharacterEncoding/filter-name
servlet-nameDispatcherServlet/servlet-name
/filter-mapping
.
I have test put encoding on HTML FORM, so with the parameter:
accept-charset=UTF-8 on FORM tag, but it isn't
param-nameencoding/param-name
param-valueUTF-8/param-value
/init-param
/filter
..
filter-mapping
filter-nameSetCharacterEncoding/filter-name
servlet-nameDispatcherServlet/servlet-name
/filter-mapping
.
I have test put encoding on HTML FORM, so
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
init-param
param-nameencoding/param-name
param-valueUTF-8/param-value
/init-param
/filter
..
filter-mapping
filter-nameSetCharacterEncoding/filter-name
servlet-nameDispatcherServlet/servlet-name
/filter-mapping
.
I have test put encoding on HTML
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.
map:parameter name=cuerpo value={request-param:id_cuerpo} /
can be the problematic part, since you take
a map:serialize type=utf8-xml/? Can you attach the xml
to exclude problems that the mail client may produce? The underlying
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
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.html
Sent from the Cocoon - Users mailing list archive at Nabble.com
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 encoding, and is curious only the field body, the subject is ok.
I work with encoding UTF
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 encoding, and is curious only
remitente: prueba, Miguelbr /
Mensaje:Prueba de mensaje en españa, camión./body
reply-tomiguel.valen...@juntadeandalucia.es/reply-to
/sendmail
/document
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
Hi,
I'm stumbling on a character encoding issue (cocoon-2.1.10) and really
can't see why. Apparently, text input in a form is passed on in a wrong
encoding. I've set Cocoon's default encoding in all thinkable places as
UTF-8:
web.xml:
servlet
servlet-nameCocoon/servlet-name
direction.
Cheers,
Robby Pelssers
-Oorspronkelijk bericht-
Van: Ron Van den Branden [mailto:ron.vandenbran...@kantl.be]
Verzonden: wo 29-9-2010 11:11
Aan: users@cocoon.apache.org
Onderwerp: form encoding issues
Hi,
I'm stumbling on a character encoding issue (cocoon-2.1.10) and really
Hi,
check out request character encoding. For tomcat look at
http://confluence.atlassian.com/display/DOC/Configuring+Tomcat%27s+URI+encoding
and in your tomcat installation at
webapps/examples/WEB-INF/classes/filters/SetCharacterEncodingFilter.java
that worked for me
regards
Thomas
Am
', and that consequently
'container_encoding should always be ISO-8859-1 (unless you have a
broken servlet container), and form_encoding should be the same one as
on your serializer.'.
And lo: changing the (over-eager?) container-encoding parameter in
web.xml back to the default:
init-param
param
to specification, servlet engine are suppose to decode using ISO-8859-1
by default.
And lo: changing the (over-eager?) container-encoding parameter in
web.xml back to the default:
init-param
param-namecontainer-encoding/param-name
param-valueISO-8859-1/param-value
/init-param
Do I
be the same one as
on your serializer.'.
And lo: changing the (over-eager?) container-encoding parameter in
web.xml back to the default:
init-param
param-namecontainer-encoding/param-name
param-valueISO-8859-1/param-value
/init-param
...seems to do the trick!
(phew!)
(note: I found this info also
Hi Thomas,
I'm not much of an expert in encoding matters, and could indeed be happy
with ISO-8859-1 instead of UTF-8.
However, testing with ISO-8859-1 set as container-encoding, even Arabic
input is passed through correctly: ص (Arabic letter 'sad' -
http://www.fileformat.info/info/unicode
?) container-encoding parameter in
web.xml back to the default:
init-param
param-namecontainer-encoding/param-name
param-valueISO-8859-1/param-value
/init-param
Do I understand this correctly: you have encoded everything in UTF8,
but to able to read your input fields (UTF8) you need to decode
hi,
that arabic character should fail with latin1.
we see a difference between jetty and tomcat (6.0). tomcat follows specs
(see Andre's mail) and uses iso per default. you can switch completely
to UTF-8 with:
- send html content in utf-8
- set container-encoding to utf-8
- set form
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron,
On 9/29/2010 5:43 AM, Ron Van den Branden wrote:
There is stated that
apparently (and counter-intuitively, IMO), 'request parameters are
always decoded using ISO-8859-1 ', and that consequently
'container_encoding should always be
completely
to UTF-8 with:
- send html content in utf-8
- set container-encoding to utf-8
- set form-encoding to utf-8
- set URIEncoding to utf-8
- and include a class like SetCharacterEncodingFilter to set request
character encoding
Note that this item sets the character encoding for reading
Hello
I followed the instruction here http://cocoon.apache.org/2.2/1366_1_1.html
. For cocoon-2.1.11 I set
init-param
param-namecontainer-encoding/param-name
param-valueUTF-8/param-value
/init-param
init-param
param-nameform-encoding/param-name
param
Hi all,
I'm generating an html table using Chinese characters and i set the encoding
and mimetype as follows:
var response = cocoon.response;
response.setContentType(application/vnd.ms-excel; charset=utf-8);
response.setHeader(
Content
[mailto:robby.pelss...@ciber.com]
Verzonden: ma 13-9-2010 14:31
Aan: users@cocoon.apache.org
Onderwerp: wrong encoding used when opening xml file with encoding utf-8
Hi all,
I'm generating an html table using Chinese characters and i set the encoding
and mimetype as follows:
var response
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robby,
On 9/13/2010 8:31 AM, Robby Pelssers wrote:
I'm generating an html table using Chinese characters and i set the encoding
and mimetype as follows:
var response = cocoon.response;
response.setContentType(application
-Oorspronkelijk bericht-
Van: Christopher Schultz [mailto:ch...@christopherschultz.net]
Verzonden: ma 13-9-2010 15:46
Aan: users@cocoon.apache.org
Onderwerp: Re: wrong encoding used when opening xml file with encoding utf-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robby,
On 9/13/2010
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
The two tomcat versions on the machines are the same, but, can you
please make a diff between the two server.xml under $CATALINA_HOME/conf?
Just to be sure ...
Jos
On Thu, 2010-02-11 at 11:47 +0100, Søren Krum wrote:
Hello!
I have a small problem with a cocoon application and forms.
The
On Thu, Feb 11, 2010 at 6:40 AM, Jos Snellings jos.snelli...@pandora.bewrote:
The two tomcat versions on the machines are the same, but, can you
please make a diff between the two server.xml under $CATALINA_HOME/conf?
Just to be sure ...
The other thing to check are the system properties
Hi again!
:-) You see me smiling, the file encoding on the one machine is utf-8,
there it works, and the other is iso-8859-1. I am not sure if it fixes
the problem if i change it, but that i figure out soon (if i have
figured out why this differs at all, and how to change it.) :-) Thx
And that fixed the problem! Winner of the cake is Dominic Mitchell,
thanks a lot :-)
--
Med vennlig hilsen
Søren D. Krum
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail:
2010/1/10 Jos Snellings jos.snelli...@pandora.be
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
-nameform-encoding/param-name
param-valueUTF-8/param-value
/init-param
Cheers, thanks for the hint. I will post the result... I will certainly
not be the only person who is confronted with this problem.
Jos
On Mon, 2010-01-11 at 08:54 +, Dominic Mitchell wrote:
2010/1/10 Jos
that there used to be a cocoon servlet
setting,
init-param
param-nameform-encoding/param-name
param-valueUTF-8/param-value
/init-param
Cheers, thanks for the hint. I will post the result... I will certainly
not be the only person who is confronted with this problem
.
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 coming from the client. So, a second conversion is happening
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
filter
filter
of utf-8 encoding the two byte
character coming from the client. So, a second conversion is happening.
Now:
new String(request.getParameter(text).getBytes(ISO-8859-1)) works
fine.
Where should this be corrected?
Jos,
in Cocoon 3 there isn't any code that changes the encoding
On Mon, Jan 11, 2010 at 10:34 AM, Jos Snellings jos.snelli...@pandora.bewrote:
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
: 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 happening.
Now:
new String(request.getParameter
: 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 happening.
Now:
new String(request.getParameter
Hi all,
I can't seem to set encoding properly when writing xml to a file using
the write-source transformer. Googling around has not yet resulted in a
solution ;-(
In my sitemap I have declared the serializer like below:
map:serializer logger=sitemap.serializer.xml
mime-type
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: users
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:
!--
Set encoding used by the container
1 - 100 of 565 matches
Mail list logo
