=mypool
dburljdbc:postgresql://myserver/mydatabase?charSet=iso-8859-1/dburl
/jdbc
all right; to complete the story, I tried this one too; encoding is
still not working.
meanwhile I think I have really set everything that is mentioned in the
documentation, the wiki or the mailinglist:
-- LANG
Le Mardi, 9 mars 2004, à 10:31 Europe/Zurich, Alexander Schatten a
écrit :
...I think I have really set everything that is mentioned in the
documentation, the wiki or the mailinglist:
-- LANG system variable
-- JAVA_OPTIONS on startup
-- this encoding in the driver
still the öäüÄÖÜ
I really believe now, this is a VM bug, but I am curious, that there
seem to be no other OS X user, that have upgraded the Java VM and did
not recognize this problem. (again: the application works fine and
without problems on Linux).
YV: I have the opposite. Running an old VM on my Mac (Jaguar
Yves Vindevogel wrote:
Yes, could be I use 1.4.2_03
What I also noticed ...
I use swaret to keep my system up-to-date. Swaret wanted me to install
XFree86 4.xx to run J2Sdk.
I think this is no longer needed (since 1.4), so I did not install it.
Could there be a problem there ?
really, I
btw.: what do you mean with
mydatabase?charSet=iso-8859-1 dburl.
In your configuration of the datasources:
I use this to force Postgresql to send my everything in ISO-8859-1.
This works under Tomcat / Cocoon 2.0.x on Mac OSX 10.2 (no panther yet on
that machine)
jdbc name=mypool
server, with the same datasource settings.
-Original Message-
From: Alexander Schatten [mailto:[EMAIL PROTECTED]
Sent: zondag 7 maart 2004 2:29
To: [EMAIL PROTECTED]
Subject: Re: [OS-X] Serious Encoding Problems (VM Bug?)
Yves Vindevogel wrote:
My problem (see: Bug in ServerPages Generator
Yves Vindevogel wrote:
jdbc name=mypool
dburljdbc:postgresql://myserver/mydatabase?charSet=iso-8859-1/dburl
/jdbc
hm, thank you; did not know this one; looks like a specific postgresql
feature, no? will this work on mysql too?
thanks
alex
I have no idea at all
but, I do think this is jdbc related and not postgres
-Original Message-
From: Alexander Schatten [mailto:[EMAIL PROTECTED]
Sent: zondag 7 maart 2004 17:03
To: [EMAIL PROTECTED]
Subject: Re: [OS-X] Serious Encoding Problems (VM Bug?)
Yves Vindevogel wrote
='-Dfile.encoding=iso-8859-1'
I read the Sun documentation now, and extended this to:
-Dfile.encoding=iso-8859-1 -Duser.language=de -Duser.country=DE
-Duser.variant=MAC
additionally,
-- the LANG=de_DE.iso-8859-1
-- the two encoding init params in web.xml are iso-8859-1
It still does not work
: [OS-X] Serious Encoding Problems (VM Bug?)
I had a similar problem storing German text in a Postgresql database
under
Mac OS X. I discovered that
1) Java stored data in the database in UTF-8;
2) Java does not necessarily read Strings in the format you would
expect.
I populated the database from
Yves Vindevogel wrote:
My problem (see: Bug in ServerPages Generator ??) could be related to this.
If I declare some string in Java within XSP, I have to use unicode for (in
my case) french characters. I now experience the same problems with data
coming from my database.
I think it could also
I develop certain Cocoon webapps on a Powerbook with recent cocoon
version; up to now with same config like on Redhat Linux and no problems
also iso-8859-1 (german) encoding worked fine: environment variable LANG
is set to de...
yesterday I worked on an application on the powerbook
Le Vendredi, 5 mars 2004, à 16:22 Europe/Zurich, Alexander Schatten a
écrit :
...Has anyone an idea, how I could fix this encoding problem on OS X ?
Most probably, you need to make sure the JVM is started with the
correct encoding definition, like -Dfile.encoding=iso-8859-1
-Bertrand
Bertrand Delacretaz wrote:
Le Vendredi, 5 mars 2004, à 16:22 Europe/Zurich, Alexander Schatten a
écrit :
...Has anyone an idea, how I could fix this encoding problem on OS X ?
Most probably, you need to make sure the JVM is started with the
correct encoding definition, like -Dfile.encoding
Alexander Schatten wrote:
JAVA_OPTIONS='-Dfile.encoding=iso-8859-1'
I read the Sun documentation now, and extended this to:
-Dfile.encoding=iso-8859-1 -Duser.language=de -Duser.country=DE
-Duser.variant=MAC
additionally,
-- the LANG=de_DE.iso-8859-1
-- the two encoding init params in web.xml
the Sun documentation now, and extended this to:
-Dfile.encoding=iso-8859-1 -Duser.language=de -Duser.country=DE
-Duser.variant=MAC
additionally,
-- the LANG=de_DE.iso-8859-1
-- the two encoding init params in web.xml are iso-8859-1
It still does not work to send and retrieve german umlauts from
saving the document, you convert the document from ASCII to UTF-8
using File - Conversions - ASCII to UTF-8
In java for example,you can do the similar thing like that : new
String(str.getBytes(ISO-8859-1), UTF-8);
And now it's working.
So no need to change the encoding of the serializer.
Lionel
Hi,
I build a webpage
with default charset=ISO-8859-1"
encoding.
I need to include another .xml file built in utf-16
encoding:
xi:include
href="" parse="text"
encoding="UTF-16"
xi:fallback
pExample currently
unavailable/p
/xi:fallback
/xi:include
I use Jetty.
java -Xmx256M -Xms128M -Xss128K -Dfile.encoding=UTF-8 -jar start.jar
etc/jetty.xml
Then it works fine.
teru
- Original Message -
From: Jorg Heymans [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 06, 2004 2:34 AM
Subject: Re: [OS-X] Serious Encoding Problems (VM
Hi all!
I'm trying to get result from databse over cocoon-xsp - esql:taglib.
strings in databse have cp1251 encoding but result have other encoding
What should i do to get result of SELECT request in cp1251 encoding?
thx.
Sorry my english
Hi,
there is an action which change the http-header encoding in Cocoon 2.1 -
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/acting/HttpHeaderAction.html
In the serializer, you can specify the output encoding of the flow.
See the main sitemap of Cocoon to have an example.
If you want two
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:
map:serializer
logger="sitemap.serializer.html" name="html"
mime-type="text/html&qu
On 23.02.2004 21:34, Carlos Dias wrote:
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:
map:serializer logger=sitemap.serializer.html name=html mime-type=text/html
I use JEdit to change file encodings. It allows you to read a file in a
certain encoding, change the buffer to a different encodig, make corrections
where necessary and write out in the new encodig.
I thought I'd mention for those not knowing JEdit.
Bert
- Original Message -
From
Let me see if I understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a different
encoding, right?!
CD
- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 23, 2004 8
On 23.02.2004 21:53, Carlos Dias wrote:
Let me see if I understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a different
encoding, right?!
Yes. This happens if you use an encoding-unaware editor or the editor
can not handle
understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a
different
encoding, right?!
Yes. This happens if you use an encoding-unaware editor or the editor
can not handle the specific encoding. jEdit is a good suggestion
The XML file is generated by a process that create a file with UTF encoding.
So I have to change the encoding from the base file, or use the UTF. But I
think doesn't work for the character set of my country (Portugal)?!
Thanks for the support,
CDias
- Original Message -
From: Joerg
Jan Uyttenhove wrote:
i wonder that cocoons serializer just writes a meta-tag with the
encoding in the html-page. it doesn't do this in the http-header.
therefore apache set the http-header to his standard-encoding and
destroys the correct encoding of the response, because most browsers
ignore
allright
If I find the time I'll provide a patch to this, because it is a very
serious problem atm. I was investigating problem and solution already
myself when you posted it to the maillist, because I can't work with the
Apache directive, I will explain why.
The default encoding
header encoding
|
--|
allright
If I find the time I'll provide a patch to this, because it is a very
serious problem atm. I was investigating
that makes sense
The Tomcat changes/fixes related to this problem are released since
Tomcat 5.0.15, and also ready for Tomcat 4.1.30 (not released yet, cvs
version).
This is however a rather tricky situation, and I think we should at
least have the possibility to add the serializer encoding
Yes, I agree, the http header should be set, particularly when already
providing the content type meta tag. The header is much easier for
downstream filters to read and change, if necessary, anyway. And the
encoding info is very necessary when displaying text using extended
character sets
[SORRY, ONCE AGAIN MY QUESTION, BECAUSE THERE WAS NO ANSWER]
hi there
i wonder that cocoons serializer just writes a meta-tag with the
encoding in the html-page. it doesn't do this in the http-header.
therefore apache set the http-header to his standard-encoding and
destroys the correct
=http://apache.org/xsp
xmlns:action="">http://apache.org/cocoon/action/1.0
page
xsp:logic
response.setHeader(Content-Type, text/html; charset=UTF-8);
/xsp:logic
/page
/xsp:page
sitemap entry (put in the pipeline for each matcher you want to set
On Mon, 2004-02-16 at 23:20, Stefan Burkard wrote:
[SORRY, ONCE AGAIN MY QUESTION, BECAUSE THERE WAS NO ANSWER]
hi there
i wonder that cocoons serializer just writes a meta-tag with the
encoding in the html-page.
The actual serializer implementation is provided by Xalan, who does
i wonder that cocoons serializer just writes a meta-tag with the
encoding in the html-page. it doesn't do this in the http-header.
therefore apache set the http-header to his standard-encoding and
destroys the correct encoding of the response, because most browsers
ignore the meta-tag
with cyrillic characters to display russian
language!
in effect, if i connect directly to tomcat on port 8080 everything runs
ok, because tomcat and cocoon both don't set any encoding in the
http-header. therefore the meta-tag in the html-page (set by
cocoon-serializer) is used by the browser (ie/mozilla
.xml" , the html did
generatedin IE , butno Chinese shown. Any advise , please ?
OS : Redhat 8.0 , locale="en_US.iso88591"
JDK 1.4.2_02-b03
Cocoon 2.1.3
web.xml :
init-param param-namecontainer-encoding/param-name param-valueiso-8859-1/param-value /init-param init-param param-
hi
i'm not sure, but i think if your test-generator reads the file with the
cat-command, it is not unicode-aware. your redhat-locale is iso8859-1
and i think the unix-commands use this encoding to read and write files.
if this is true, your gb2312-characters get corrupted when cat reads
we have to setup the default encoding in our web server (apache)
to be set the encoding of ie automaticly
i dont know if this is the only somlution,but it's work
--stavros
On Wed, 11 Feb 2004, [gb2312] wrote:
Hi,all:
I want to use Chinese chacter in the page and don't want
Hi,all:
I want to use Chinese chacter in the page and don't want it to be
encoded as someting like #8983;.
So I change configurations in web.xml:
init-param
param-namecontainer-encoding/param-name
param-valueutf-8/param-value
/init-param
init-param
param-nameform-encoding/param
configurations in web.xml:
init-param
param-namecontainer-encoding/param-name
param-valueutf-8/param-value
/init-param
init-param
param-nameform-encoding/param-name
param-valueutf-8/param-value
/init-param and I also change HTMLSerializer config in root sitemap
On Thu, 2004-02-12 at 09:26, [EMAIL PROTECTED] wrote:
we have to setup the default encoding in our web server (apache)
to be set the encoding of ie automaticly
i dont know if this is the only somlution,but it's work
--stavros
On Wed, 11 Feb 2004, [gb2312] wrote:
Hi,all
init-param
param-namecontainer-encoding/param-name
param-valueutf-8/param-value
Do NOT change this parameter - leave the default value. Only form-encoding
should be set to utf-8
--
Leszek Gawron
-
To unsubscribe, e
hi roy
i had the same effect with cyrillic characters to display russian language!
in effect, if i connect directly to tomcat on port 8080 everything runs
ok, because tomcat and cocoon both don't set any encoding in the
http-header. therefore the meta-tag in the html-page (set by
cocoon
Hi,all: I want to use Chinese chacter in the page and don't want it to be encoded as someting like #8983.So I change configurations in web.xml: init-param param-namecontainer-encoding/param-name param-valueutf-8/param-value /init-param
init-param param-nameform-encoding/param-name param-valueutf
legal URI (as defined in
[RFC1738], section 2.2 or [RFC2141], section 2) that is independent of
the character encoding to which the HTML document carrying the URI may
have been transcoded.
Now my problem is that this is not happening. What i'm getting is :
( I use a simple xml and apply
.
And i was very careful in the encoding because i'm using ISO-8859-1
everywere.
Now my answer is:
- Am i doing something wrong? Or this is something that we
can't do dynamically.
I'm using Cocoon 2.1.3 and running under Jetty
Thank you
to 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: Encoding Params
:[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 it doesn't seem to work as it should
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
.
And i was very careful in the encoding because i'm using ISO-8859-1
everywere.
Now my answer is:
- Am i doing something wrong? Or this is something that we
can't do dynamically.
I'm using Cocoon 2.1.3 and running under Jetty and i attached
the
sessionid
as was written in the documents.
Right. That's what encodeURL does... it's an URL rewriter, has nothing
to do with character encodings...
And i was very careful in the encoding because i'm using ISO-8859-1
everywere.
Do you have a live page we can look at?
~ml
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 %20
back into the GET it
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
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 that's the key.
Thanks!
- Brent
]
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? I'm trying to use a request parameter in the
HTMLGenerator
as part
"David Leangen" [EMAIL PROTECTED] at 2004/1/25 11:29:09
$B(B---"HTML Generator and UTF-8"
(B I am having a bit of a problem when trying to output UTF-8 encoded
(B (Japanese) html directly through. Everything works fine when I use the
(B default File generator. The problem only occurs when
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
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
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
OK, but now I suffer from other problem - forms that are sent with
default method (ie. enctype=application/x-www-form-urlencoded) has
encoding problems. Previously, when there was only form-encoding to
UTF-8 set, and container-encoding was left unchanged, everything was
fine. Now, no matter
/01/2004 +0100, you wrote:
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 setting accept
Hi,
Does anyone can tell me, what the container-encoding in web.xml really
means?
I had problems with encoding of text fields, when the form was
enctype=multipart/form-data (for uploading files). The form-encoding
didn't help, so I tried with container-encoding and it helped :-) But
in fact I
I found that setting container-encoding in web.xml to utf-8 solves the
problem. But I don't know if it will influce the system also in other way.
Regards,
Marcin Okraszewski
Hi,
I have a big problem!! I have changed enctype to multipart/form-data
in form definition and this caused problems
You modified the container-encoding only in the case you chose.
The container-encoding parameter is used to say to cocoon to encodethe
request String as UTF-8.
See the web.xml for more information.
At 16:46 22/01/2004 +0100, you wrote:
I found that setting container-encoding in web.xml
Hi,
If I'm using UTF-8 encoding with a French file special characters as é or à
makes an error...
I don't understand why... Isn't UTF-8 supposed to integrate this characters or
did I miss something?
Nicolas
actualités.
So basically, this is an encoding problem... I'm wondering of this come from
the http protocol...
Can you help please ;=)?
Nicolas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
On 20.01.2004 11:14, Nicolas Toper wrote:
Hi,
If I'm using UTF-8 encoding with a French file special characters as é or à
makes an error...
I don't understand why... Isn't UTF-8 supposed to integrate this characters or
did I miss something?
Is it this one: http://nagoya.apache.org/bugzilla
There is a form encoding parameter in the web.xml:
init-param
param-nameform-encoding/param-name
param-valueUTF-8/param-value
/init-param
set there the encoding you are using (by default ISO-8859-1 is taken).
Regards,
Marcin Okraszewski
Hi,
I'm trying to get the following
No
Le Mardi 20 Janvier 2004 12:05, Joerg Heinicke a écrit :
On 20.01.2004 11:14, Nicolas Toper wrote:
Hi,
If I'm using UTF-8 encoding with a French file special characters as é
or à makes an error...
I don't understand why... Isn't UTF-8 supposed to integrate this
characters or did
to UTF-8. This character will be encoded on
two octets.
So yes, UTF-8 includes ISO-8859-1 but in a certain way.
Lionel
At 12:05 20/01/2004 +0100, you wrote:
On 20.01.2004 11:14, Nicolas Toper wrote:
Hi,
If I'm using UTF-8 encoding with a French file special characters as é
or à makes an error...
I
encoded text anywhere else. My
coocoon i properly configured for this encoding. My XSL file is
?xml version=1.0 encoding=iso-8859-2?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xsl:output encoding=iso-8859-2/
xsl:template name=xxx match=/
input
xsl:attribute name
Hello list,
I want to make a query front end to the IMDB movie database.
To do this, I have a cocoon matcher that receives a query parameter and
pass it along to the IMDB query url.
Very simple. But how do I URL encode the query parameterin the sitemap?
This is not done automatically.
joakim verona wrote:
Hello list,
I want to make a query front end to the IMDB movie database.
To do this, I have a cocoon matcher that receives a query parameter and
pass it along to the IMDB query url.
Very simple. But how do I URL encode the query parameterin the sitemap?
This is not done
Thanks Tony,
So at least this wasn't totally easy.
I'm not familiar enough with the modules to write one yet, so I'll
experiment with the jxpath option.
Another workaround I thought about, but didn't want to test if there was
a simple way to solve it,
is to use the jx transformer, the
I have a data consumer who is pulling XML from our Cocoon webapp. They
couldn't handle UTF-8 on their end, so I gave them the option to pull data
in US-ASCII encoding. However, when I did that, symbol characters such as
Greek and math symbols got sent over even though they aren't
:
|
| Subject: XML serializer; handling characters outside the encoding
|
--|
I have a data consumer who is pulling XML from
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
waiting for the 2.1x branch that is supposed to add parameters for
the SVG serializer. Maybe you can have a look how it's done and
generalize it to the 2.0.x branch for any serializer.
Hope this helps
Jorg
Christopher Painter-Wakefield wrote:
Is there any way to dynamically set the encoding
Thanks - that's a big help, although I may just take the path of least
resistance and hand-configure for now :)
-Christopher
The fact that serializers don't accept parameters and don't have access
to the objecmodel has come up before here and is indeed a pain.
Can you maybe add a node to
Hi,
I' have some real problems to with my encoding.
My application get some parameters from the form and create a document with
an xsp.
After that, I'm using DOM and SAX transformers, generators, etc ... to
manipulate the XML document.
I'm trying to figure out, what should I configure to get
I found some answers but not all.
I miss one thing.
When i create a document from an xsp (parameters comes from a post), the
flow is encoded twice is that normal ?
At 15:13 10/12/2003 +0100, you wrote:
Hi,
I' have some real problems to with my encoding.
My application get some parameters
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
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
to encode
on
by
assigning of InputStream data to the String (I tried InputStreamReader
with
correct encoding also) and following storing into database for this
reason
fails.
What have I to do differently? Thanx a lot!
osup
InputStream are going
out relative correct characters). It looks like, that problem comes on by
assigning of InputStream data to the String (I tried InputStreamReader with
correct encoding also) and following storing into database for this reason
fails.
What have I to do differently? Thanx a lot
encoding also) and following storing into database for this reason
fails.
What have I to do differently? Thanx a lot!
osup
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
, everything was ok (it means, that from InputStream are
going
out relative correct characters). It looks like, that problem comes on by
assigning of InputStream data to the String (I tried InputStreamReader
with
correct encoding also) and following storing into database for this
reason
fails
with
correct encoding also) and following storing into database for this
reason
fails.
What have I to do differently? Thanx a lot!
osup
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
[EMAIL PROTECTED] wrote:
Db supports BLOBs, but I never did anything with them in java, less so
cocoon :) Is it possible to use ESQL someways? Probably not, isn't it :)
ESQL and (modular) database actions support blob, clob types.
AFAIR ESQL can only get them while the actions can insert and
Christian Haul wrote:
[EMAIL PROTECTED] wrote:
Db supports BLOBs, but I never did anything with them in java, less so
cocoon :) Is it possible to use ESQL someways? Probably not, isn't it :)
ESQL and (modular) database actions support blob, clob types.
AFAIR ESQL can only get them while the
=org.apache.cocoon.serialization.HTMLSerializer
buffer-size1024/buffer-size
encodingUTF-8/encoding
/map:serializer
But that's not enough because I have many problem with the form.
When I reload it with some request parameter (using xsl:value-of).
The characters are not display good.
For example the é become é .
Any idea
Are you sure, the viewer is UTF8?
-Message d'origine-
De : Lionel Crine [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 27 novembre 2003 11:58
À : [EMAIL PROTECTED]
Objet : encoding, UTF-8
Hi,
I want to put the entire plateform into UTF-8. For now, cocoon is using
ISO-8859-1.
Here what I've
i'm allmost sure that the entire cocoon has UTF-8 as default encoding
corect me
--stavros
On Thu, 27 Nov 2003, Nicolas Toper wrote:
Are you sure, the viewer is UTF8?
-Message d'origine-
De : Lionel Crine [mailto:[EMAIL PROTECTED]
Envoy : jeudi 27 novembre 2003 11:58
From: Nicolas Toper [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Thu, 27 Nov 2003 12:16:11 +0100
To: [EMAIL PROTECTED]
Subject: RE: encoding, UTF-8
Are you sure, the viewer is UTF8?
-Message d'origine-
De : Lionel Crine [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 27
Did you set the form-encoding parameter in web.xml?
Guido
Lionel Crine wrote:
Hi,
I want to put the entire plateform into UTF-8. For now, cocoon is
using ISO-8859-1.
Here what I've already done :
map:serializer logger=sitemap.serializer.html
mime-type=text/html name=html pool
Hallo Lionel,
we had problems with this issues several
times.
Play arround with these two
initparams.
The strange thing was, that on different engines we
had to change the container-encoding to avoid encoding problems.
Now we do not have any problems with encoding
anymore and we don't
In fact :
The encoding parameter for the serializer modify the ?xml ...?
declaration according the the value.
Now I'm sure of that, my previous message was false.
Now, I'm using that :
map:serializer logger=sitemap.serializer.html
mime-type=text/html name=html pool-grow=4 pool-max=32
401 - 500 of 565 matches
Mail list logo
