Edwin Kapauni schrieb:
christian bindeballe wrote:
[...]
[quote] Since the servlet specification requires that the ISO-8859-1
encoding is used (by default), you should never change this value
unless you have a buggy servlet container.[/quote]
Citation without sources? Where did you get
christian bindeballe wrote:
[...]
also, Marc Portier wrote: (see this thread, message-ID
[EMAIL PROTECTED])
never change your container-encoding unless you have a servlet container
of which you can specify the used encoding applied in decoding of url's
and request parameters
[...]
Hi
Edwin Kapauni schrieb:
map:serializer name=xhtml
mime-type=test/html; charset=utf-8
logger=sitemap.serializer.xhtml
pool-grow=2 pool-max=64 pool-min=2
src=org.apache.cocoon.components.serializers.XHTMLSerializer
encodingUTF-8/encoding
indentno/indent
As I thought, it was the html-include serializer in
{base}/portal/sitemap.xmap that needed some fitting :)
cb
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Think you should have no problem at all when you just serialize everything as
utf-8:
map:serializer logger=sitemap.serializer.xml mime-type=text/xml name=xml
pool-grow=4 pool-max=32 pool-min=4
src=org.apache.cocoon.serialization.XMLSerializer
encodingUTF-8/encoding
/map:serializer
Thank you, Ard
I already did that. But it doesn't change anything. I found this in my
web.xml in the WEB-INF folder of my cocoon-build:
!--
Set encoding used by the container. If not set the ISO-8859-1 encoding
will be assumed.
Since the servlet specification requires
christian b wrote:
[...]
these are the feed-adresses that I want to incorporate. both don't
have an encoding set (do RSS-feeds have to have that?) but they
clearly contain UTF-8 encoded characters.
http://www.industrial-technology-and-witchcraft.de/index.php/ITW/itw-rss20/
http
christian b wrote:
[...]
these are the feed-adresses that I want to incorporate. both don't
have an encoding set (do RSS-feeds have to have that?) but they
clearly contain UTF-8 encoded characters.
http://www.industrial-technology-and-witchcraft.de/index.php/ITW/itw-rss20/
http
christian b wrote:
Thank you, Ard
I already did that. But it doesn't change anything. I found this in my
web.xml in the WEB-INF folder of my cocoon-build:
!--
Set encoding used by the container. If not set the ISO-8859-1 encoding
will be assumed.
Since the servlet
Edwin Kapauni schrieb:
Hi Christian,
Have a look at the HTTP response headers[1] of those feeds. The
netzpolitik feed's header clearly states it's iso-8859-1.
That's right. My mistake. I merely deducted the encoding from some
characters used inside the text of the feeds as for example 8221
Hello Marc,
Marc Portier schrieb:
never change your container-encoding unless you have a servlet container
of which you can specify the used encoding applied in decoding of url's
and request parameters
(if you don't understand what I just said: that translates to simply
never)
I think I got
Hi,
I have several newsfeeds that I want to incorporate in my portal, each
one of these feeds has its own coplet. but these feeds are encoded
differently. some are in ISO-8859-1, others in UTF-8. Now there is no
way that I can change the legacy encoding of these. unfortunately it
seems
Hi!
I use tomcat to be cocoon's servlet container, the default encoding for
tomcat is iso-8859-1, so I set the cocoon's container-encoding to iso-8859-1
before, and form-encoding to UTF-8 for chinese input, everything good.
But I found AJAX's encoding is UTF-8, see
req.setRequestHeader
Hello,
Some time ago there was a discussion about implementing possibility to
define flowscript encoding:
http://thread.gmane.org/gmane.text.xml.cocoon.devel/48228
Is it implemented now? What is the syntax of this line?
// encoding = UTF-8
--
Best regards,
Wojciech Gdela
%e9ral| whereas I'm
waiting for :
resultats-in.html?q=finstitutiontype:|Service%20g%C3%A9n%C3%A9ral|
Isn't url-encoding standardized? (to some iso codepage)
Does it make a difference to set default encoding of Cocoon to utf-8? I believe it is a property in
the cocoon.xconf or perhaps
Le 16 nov. 05, à 08:45, Myriam Delperier a écrit :
in fact the characters are well displayed, but I've in my file
some external links like :
fo:basic-link
external-destination=resultats-in.html?q=finstitutiontype:|Service
général|Service général/fo:basic-link and the result of the link
| | Does it make a difference to set default encoding of Cocoon to
| | utf-8? I believe it is a property in the cocoon.xconf or perhaps
| | the web.xml.
it's already the case, in my web.xml file I've :
init-param
param-nameform-encoding/param-name
param-valueUTF-8/param-value
/init-param
init
| I'm not 100% sure how this is handled in PDF, but my guess is that you
| should encode your URLs before they get to the serializer.
|
| See
| http://cocoon.apache.org/2.1/userdocs/transformers/encodeurl-
| transformer.html and try adding
|
|map:transform type=encodeURL/
|
| before the
| See
| http://cocoon.apache.org/2.1/userdocs/transformers/encodeurl-
| transformer.html and try adding
|
|map:transform type=encodeURL/
|
| before the fo2pdf serializer, assuming the encodeURL transformer is
| already configured in your sitemap.
i've tried it and my urls still aren't
Le 16 nov. 05, à 11:00, Myriam Delperier a écrit :
| See
| http://cocoon.apache.org/2.1/userdocs/transformers/encodeurl-
| transformer.html and try adding
| |map:transform type=encodeURL/
| | before the fo2pdf serializer, assuming the encodeURL transformer is
| already configured in your
| What do you see at the output of the encodeURL transformer?
| You can see this by replacing the fo2pdf serializer with an xml one,
| or using a view.
I don't see any changes:
fo:basic-link
src=org.apache.cocoon.transformation.EncodeURLTransformer
include-name.*/@external-destination/include-name
/map:transformer..
Looks like the encoreURL transformer is not encoding - I'm not too
familiar with its details but you might want to try
include-name.*external-destination/include
| Looks like the encoreURL transformer is not encoding - I'm not too
| familiar with its details but you might want to try
|
| include-name.*external-destination/include-name
|
| in case the namespace confuses it, or even
|
| include-name.*/include-name
i've this :
include-name.*/@external
On Wed, 2005-11-16 at 10:15 +0100, Myriam Delperier wrote:
| | Does it make a difference to set default encoding of Cocoon to
| | utf-8? I believe it is a property in the cocoon.xconf or perhaps
| | the web.xml.
it's already the case, in my web.xml file I've :
init-param
param-nameform
| | I'm not sure if it's a good idea to set the container-encoding to
| | utf-8. Cocoon's web.xml says about the container-encoding:
| | Since the servlet specification requires that the ISO-8859-1
| | encoding
| | is used (by default), you should never change this value unless you
| | have
with the sequence of encoding and concatenating since I'm
doubthing if this will encode the '?', '/', '' and '=' as well
Myriam Delperier wrote:
| | I'm not sure if it's a good idea to set the container-encoding to
| | utf-8. Cocoon's web.xml says about the container-encoding:
| | Since the servlet
| | you might want to use Java's urlencode function in your fo
| | producing xslt
you're right that's work great.
As I'm using saxon as xsl transformer iIve something like :
urle:encode(string($val), 'UTF-8') and
xmlns:urle=java:java.net.URLEncoder
instead.
But I don't know if this works
Le 16 nov. 05, à 11:18, Bertrand Delacretaz a écrit :
Looks like the encoreURL transformer is not encoding...
hmmm...cough...well...turns out that the EncodeURL transformer does
*not* encode URLs as its name seems to indicate, it adds sessionIDs to
them. I just checked the encodeurl
| I guess we'll have to change the name of
| the transformer at some point...
and keep this name for a transformer which really encodes (with a given
encoding) given patterns :-)
that would be great!
-
To unsubscribe, e
Hi,
I'm creating pdf files with something like :
map:generate type=xsp src=myfile.xsp/
map:transform src=myfile.xsl/
map:serialize type=fo2pdf /
the result is a pdf page with ISO-8859-1 encoding, and I need an UTF-8
encoding.
I've tried
xsl:output encoding=UTF-8/ in the xsl file
with something like :
map:generate type=xsp src=myfile.xsp/
map:transform src=myfile.xsl/
map:serialize type=fo2pdf /
the result is a pdf page with ISO-8859-1 encoding, and I need an UTF-8
encoding.
I've tried
xsl:output encoding=UTF-8/ in the xsl file,
map:serializer name=fo2pdf logger
Geert Josten wrote:
| | Isn't the PDF format written in low-ascii? So it shouldn't matter.
| | If you want unicode characters to be shown, use character
| | references or utf-8 in the FO document and reference to a Unicode
| | capable font supported by FOP.
in fact the characters are well
Le 16 nov. 05, à 08:30, Myriam Delperier a écrit :
...I'm creating pdf files with something like :
map:generate type=xsp src=myfile.xsp/
map:transform src=myfile.xsl/
map:serialize type=fo2pdf /
the result is a pdf page with ISO-8859-1 encoding, and I need an UTF-8
encoding
What do you
Safari ne transmettent pas l'entête Accept-Charset...
L'info n'est donc pas disponible aux mêmes endroits sur tous les browsers ou
terminaux.
La séquence de recherche du form-encoding serait plutôt un truc du genre alors ?
1. Paramètre cocoon-form-encoding : si null...
2. Analyse du Content-Type : si
Bonjour,
J'ai vu avec Cocoon que l'on peut positionner un form-encoding par défaut
(web.xml : param-nameform-encoding/param-name).
Ce paramètre sert à initialiser la request (cf. CocoonServlet.getEnvironment :
this.defaultFormEncoding).
Je rencontre des cas où cette définition par défaut n'est
Mikhial Usatchev wrote:
Hello,
I tried doing my best to understand a problem in the Cocoon framework
connected with non-English encoding, but all's in vain. (Cocoon 2.1.7
built under Windows 2000)
Whatever I wrote in the head of my origin XML document
?xml version=1.0 encoding=windows
Hello,I
tried doing my best to understand a problem in the Cocoon framework connected
with non-English encoding, but all's in vain. (Cocoon 2.1.7 built under Windows
2000)Whatever I wrote in the head of my origin XML
document
?xml
version="1.0" encoding="windows-1251&quo
Hi,
I got my application up and running nicely except one
small encoding-problem which is driving me nuts.
I load an Xml-Document, which contains German umlauts
If I print this to the console, everything is ok I load the Dom into
the form debug output widget.lookupWidget(xyz
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 like
Hi!
I'm using CForms on a UTF-8 page. Everything is fine, but when I enter
some non ASCII characters into the text fields, they are coming back as
ISO-8859-1 (two characters instead of one). What's going wrong?
Input: München
Output: München
Thanks in advance,
Alex
--
Alexander Nofftz,
Hi!
I set form-encoding to UTF-8 and container encoding to
ISO-8859-1 fornon english input in cform is ok.
Now I put my cform to portal with coplet type =
"Application",I Must changethe container encoding to UTF-8.
Is there I loss somthing when I use cformin portal for no eng
Hi!
Now I find it's a AJAX encoding problem,If the container
encoding is UTF-8,AJAX with UTF-8 reguest will good,But I need a ISO-8859-1
container-encoding.how to change it.
Best Regards
Johnson
- Original Message -
From:
Johnson
To: users@cocoon.apache.org
Sent
I mean,
map:serializer
encodingISO-8859-1/encoding
/map:serializer
And I had to modify container-encoding and form-encoding in web.xml
(UTF-8 - ISO-8859-1)
Otherwise, I had some UTF8Exception during my upload(streamgenerator).
Lionel
Geert Josten wrote:
Hi,
Now I need
If I set container encoding UTF-8 , It's ok.
Johnson
- Original Message -
From:
許議中
To: users@cocoon.apache.org
Sent: Wednesday, June 22, 2005 12:15
AM
Subject: AJAX encoding
Hi!
If I use AJAX to submit my request to save the form to
database
Hi all,
I'm experiencing something strange since I have upgraded my application
to work with Cocoon 2.1.7 (2.1.5 instead).
Now I need to change my encoding on the serializers. (UTF-8 -
ISO-8859-1).
Did I miss some changes from 2.1.5 to 2.1.7 ?
Thanks
Lionel
--
Lionel CRINE
Ingénieur
Hi,
Now I need to change my encoding on the serializers. (UTF-8 -
ISO-8859-1).
What do you mean with 'need to change'?
Grtz,
Geert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Hi!
If I use AJAX to submit my request to save the form to
database,the chinese font in form will became ??,but showform ok.
If I do not use AJAX,OK.
How to avoid ??.
Best Regards
Johnson
Hi,
Do you know how should I configure Cocoon 2.1.7 to generate PDF files
with LATIN2 fonts ?
Thanks in advance.
AI
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've tried changing serializer encoding, container encoding, etc...but
until now a didn't find any solution to solve this problem.
Have you tried cocoon.request.getParameter('test') instead of
cocoon.request.test?
I don't think getParameter will make a difference.
Have you tried adding
Geert Josten wrote:
I've tried changing serializer encoding, container encoding, etc...but
until now a didn't find any solution to solve this problem.
Have you tried cocoon.request.getParameter('test') instead of
cocoon.request.test?
I don't think getParameter will make a difference
Have you tried cocoon.request.getParameter('test') instead of
cocoon.request.test?
I don't think getParameter will make a difference.
Citing http://wiki.apache.org/cocoon/RequestParameterEncoding
[...]
For Java-insiders: what Cocoon actually does internally is apply the
following trick to
Yes,
using ${request.getParameter('teste')} instead of ${request.teste} makes
the diference.
Thanks Reinhard for the help.
Rui
On Tue, 2005-06-07 at 09:17 +0200, Geert Josten wrote:
Have you tried cocoon.request.getParameter('test') instead of
cocoon.request.test?
I don't think
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 how to solve this problem?
Thanks to all..
Rui
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 how to solve this problem?
Have you tried
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:
map:match type=regexp pattern=page
Hi all,
I'm trying to produce excel files using HSSFSerializer, but I'm facing a
problem when trying to format a StyleRegion with a currency format:
ex:
StyleRegion ... Format=0.00 [$-1]
The HSSFSerializer is producing a wired character in place of euro
symbol!!
Does anyone has any idea how to
On Sun, 2005-03-06 at 20:46 +0100, stefan pickschneider wrote:
Bertrand Delacretaz wrote:
Le 5 mars 05, à 15:17, stefan pickschneider a écrit :
..we have a problem with the encoding, cforms and file uploads.
Did you look at http://wiki.apache.org/cocoon/RequestParameterEncoding
mentioned.
The patch replaces
this.defaultFormEncoding);
by
this.containerEncoding);
In our configuration the
defaultFormEncoding == containerEncoding == UTF-8 - so the patch
doesn't seem to have a influence on our problem :-(
Somewhere the encoding for the Parameters is set to ISO-8859-1 probably
on our problem :-(
then your configuration is wrong :-) The containerEncoding should be
ISO-8859-1, always.
Somewhere the encoding for the Parameters is set to ISO-8859-1 probably
because no encoding is set until the first call of getParameter*().
Cocoon doesn't rely on the setCharacterEncoding
:-(
then your configuration is wrong :-) The containerEncoding should be
ISO-8859-1, always.
Ok. So this option is for future use or if you really know, what
your webcontainer is doing.
Somewhere the encoding for the Parameters is set to ISO-8859-1 probably
because no encoding is set until the first
web containers, that don't follow the spec.
Somewhere the encoding for the Parameters is set to ISO-8859-1 probably
because no encoding is set until the first call of getParameter*().
Cocoon doesn't rely on the setCharacterEncoding support of the
webcontainer, basically because
It should work the same for both normal and multipart forms, without use
of the SetCharacterEncodingAction. You do need the fix though I pointed
to in a previous mail, since that one is not yet in Cocoon 2.1.6 IIRC.
Got it ;-) Should've tried that first. It just works.
Thanks a lot!
Stefan.
Bertrand Delacretaz wrote:
Le 5 mars 05, à 15:17, stefan pickschneider a écrit :
..we have a problem with the encoding, cforms and file uploads.
Did you look at http://wiki.apache.org/cocoon/RequestParameterEncoding ?
It might give some answers.
-Bertrand
Hello,
thanks for your suggestion
Le 6 mars 05, à 20:46, stefan pickschneider a écrit :
...It seems that the cocoon servlet initializes the container-encoding
for the request too late..
Could you create a bugzilla entry (http://issues.apache.org/bugzilla/)
for this, so that we don't forget to have a look at it?
-Bertrand
Hello,
we have a problem with the encoding, cforms and file uploads.
We have a form that allows to upload a file and on the same form an
input field to enter the corresponding title. The upload works but
if you enter special characters (like german umlauts) these are sent
as garbage
Hello,
we have a problem with the encoding, cforms and file uploads.
We have a form that allows to upload a file and on the same form an
input field to enter the corresponding title. The upload works but
if you enter special characters (like german umlauts) these are sent
as garbage
Le 5 mars 05, à 15:17, stefan pickschneider a écrit :
..we have a problem with the encoding, cforms and file uploads.
Did you look at http://wiki.apache.org/cocoon/RequestParameterEncoding ?
It might give some answers.
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
On 28.07.2004 12:03, Jan Hoskens wrote:
Hi,
I'm currently facing the following problem: I've set the encoding in my
serializers to ISO-8859-1 and checked the web.xml file (utf-8 is in
comment, defaults to the ISO-8859-1)
Everything is ok (special chars in cforms offer no problem, saving
I have carefully read the Wiki
http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlightvalue=container-encoding
http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlightvalue=container-encoding
but I have still a problem with parameter encoding
Pages are serialized
Dominique Galland wrote:
I have carefully read the Wiki
http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlightvalue=container-encoding
http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlightvalue=container-encoding
but I have still a problem with parameter
I recently responded to a question on this mailing list with a subject
of ESQL and utf-8 encoding.
The following is from that response:
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
-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
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 xsp:logic tag.
I've deployed
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
Saulius,
you can find an explanation here:
http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlightvalue=container-encoding
(with highlight of the section that might interest you most)
there is more in the mail archives of this list, since this has been
touched upon quite a lot
[ISO-8859-1] Aurlien DEHAY ():
Saulius Grigaliunas wrote:
Hello Aurlien,
Maybe you can look at the encoding of xsl file, or try with xalan. It
was the only thing I change to make my forms utf-8 aware.
Well thanks for your help, that didn't work, but I accidently found
solution myself
hat the string that gets printed
out to the file is good utf-8. My problem is that the output 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: Lo
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 characters
Hello.
Saulius Grigaliunas wrote:
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
Hello Aurélien,
Look at the cocoon's web.xml in WEB-INF and uncomment the following part:
init-param
param-nameform-encoding/param-name
param-valueutf-8/param-value
/init-param
and It should work.
Rgds.
Already done that, as I wrote in my first letter. Any
Saulius Grigaliunas wrote:
Hello Aurélien,
Look at the cocoon's web.xml in WEB-INF and uncomment the following part:
init-param
param-nameform-encoding/param-name
param-valueutf-8/param-value
/init-param
and It should work.
Rgds.
Already done that, as I wrote in my first
Hello Aurélien,
Maybe you can look at the encoding of xsl file, or try with xalan. It
was the only thing I change to make my forms utf-8 aware.
Well thanks for your help, that didn't work, but I accidently found
solution myself, in web.xml I've changed the configuration like this:
init-param
Saulius Grigaliunas wrote:
Hello Aurélien,
Maybe you can look at the encoding of xsl file, or try with xalan. It
was the only thing I change to make my forms utf-8 aware.
Well thanks for your help, that didn't work, but I accidently found
solution myself, in web.xml I've changed
Title: ESQL and utf-8 encoding
Hi,
Has anyone here used esql with data that is utf-8 encoded? I'm able to connect to my database and get the correct data but it appears that somewhere along the way the data is being interpreted as iso-8859-1 encoding. I'm not sure if I got all
[EMAIL PROTECTED] wrote:
hi people
i have notice that the set-encoding action is not delceared any more in
the root sitemap
map:action name=set-encoding
src=org.apache.cocoon.acting.SetCharacterEncodingAction/
btw the class exist and after declaration set-encoding action work fine.
is there any
Hi there,
I have a problem with the cfoms encoding. I`ve now managed to integrate cfoms
in lenya.
The form work well, but when I insert another characters than ASCII, I get them
in UTF-8 code. so far so god, but the main problem is the validation. If the
user insert something wrong, he
hi people
i have notice that the set-encoding action is not delceared any more in
the root sitemap
map:action name=set-encoding
src=org.apache.cocoon.acting.SetCharacterEncodingAction/
btw the class exist and after declaration set-encoding action work fine.
is there any specific reason
Does anyone have any ideas on this one? I'm still stumped.
Thanks.
Theresa
-Original Message-
From: Martinson, Theresa
Sent: Tuesday, December 07, 2004 12:43 PM
To: '[EMAIL PROTECTED]'
Subject: I18n Encoding Problems
Hello.
I am attempting to use UTF-8
Hello.
I am attempting to use UTF-8 for the internationalization of Asian
characters coming in as form request parameters. Unfortunately, they
are not being handled or displayed correctly in my Cocoon application
and show up as blank.
I have read the Cocoon Wiki on Request Parameter Encoding
.
the encoding was UTF-8
so my questions are:
-how can we (I) fix this problem in cocoon samples?
-is this an ant or xerces problem (i know that this is offtopic here)
-must cocoon community care about this?
Some of the ant replace tasks are not encoding aware and break UTF-8.
Joerg
charakters i have refer was broken in
those files. thats why those charakters are broken in cocoon samples.
the encoding was UTF-8
so my questions are:
-how can we (I) fix this problem in cocoon samples?
-is this an ant or xerces problem (i know that this is offtopic here)
-must cocoon
PROTECTED]
Subject: Re: Other URL encoding issue...
Hi:
Try to use UTF-8 every where:
in the xml files, in the web.xml and in the http.conf file.
Best Regards,
Antonio Gallardo
[EMAIL PROTECTED] dijo:
I spoke to soon :-(
This works OK if your requests go directly to the Servlet container
(Tomcat
for the suggestions but I'm sure that this problem is not in any
way related to Cocoon so I'll 'snip' this thread off now and go looking
else.
Unless anyone else knows different.
You should not touch container-encoding in web.xml you know that?
set form encoding to utf-8
leave container encoding at iso-8859-1
On 31.10.2004 18:16, Marc Portier wrote:
So assuming all this reasoning is ok, what could never work is this:
- change your form-encoding (and matching setting of serialization)
to anything else then UTF-8, cos then request-params in forms and
pre-built ones in url's get encoded differently
the problem comes back
again. I must therefore assume that there is some request encoding
configuration of Apache required.
Can anyone give me a prod in the right direction?
Regards
Phil Fennell
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 01 November
container-encoding in Cocoon's web.xml it all
worked happily :)
I just thought people should know this.
Should I add it to the afore mentioned wiki?
Regards
Phil Fennell
-Original Message-
From: Kees van Dieren [mailto:[EMAIL PROTECTED]
Sent: 29 October 2004 06:38
To: Fennell
I spoke to soon :-(
This works OK if your requests go directly to the Servlet container
(Tomcat) but when I go via Apache and mod_jk the problem comes back
again. I must therefore assume that there is some request encoding
configuration of Apache required.
Can anyone give me a prod in the right
setting the Servlet container-encoding in Cocoon's web.xml it all worked happily :)
This is quite strange for me as your anchor name contains only basic
ascii characters SL12345. Are you sure that was the cause for problem?
I just thought people should know this.
Should I add it to the afore
) and
mod_jk (1.2) the problem returned.
Now it so happens that there used to be a bug in IE 4 that Microsoft
claimed to have fixed in IE 5 that indicated there were problems with
links and UTF-8 encoding.
Firefox 0.9.3 doesn't have the same problem, and neither does IE 5.2 on
the Mac.
Another
201 - 300 of 565 matches
Mail list logo
