Thank you Peter!
It works perfect!
:-)Peter Velychko <[EMAIL PROTECTED]> wrote:
Hello Galia,Try to set the form encoding. It is in the "web.xml" file:form-encodingutf-8Simply incomment it for cocoon 2.1.GA> Hello,GA> I have a problem with Cirilic encoding when working with x
Hello Galia,
Try to set the form encoding. It is in the "web.xml" file:
form-encoding
utf-8
Simply incomment it for cocoon 2.1.
GA> Hello,
GA> I have a problem with Cirilic encoding when working with xmlforms. Everything is
ok exept when I submit a c
Hello,
I have a problem with Cirilic encoding when working with xmlforms. Everything is ok exept when I submit a cirilic text in a textbox:
I write: Ãàëÿ
and on the server it appears like: ÐалÑ
In select or labels the text appears as cirilic. But in textboxes and textareas - not.
Any
for *every* character. You only must use it
> > correctly - and that's not so easy :-)
> > By default giving a browser an UTF-8 document, it will send forms
> > encoded in UTF-8 too, but Cocoon expects ISO-8859-1. You can change
> > his by setting the form encoding cor
r an UTF-8 document, it will send forms
encoded in UTF-8 too, but Cocoon expects ISO-8859-1. You can change
his by setting the form encoding correctly.
Well, I have mentioned it, I am definitily no encoding expert, but my
practical know-how shows me with different tools(!) not only with
cocoon,
send forms
encoded in UTF-8 too, but Cocoon expects ISO-8859-1. You can change his
by setting the form encoding correctly.
http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding
Joerg
-
To unsubscribe, e-mail: [EMAIL
Alexander Schatten wrote:
(2) ISO-8850-1 works for Western-Europe AS WELL AS for english texts:
Hence this is no disadvantage for all english
this should have been ISO-8859-1, off course
-
To unsubscribe, e-mail: [EMAIL PROTECT
about all these people _not_ using a classical anglosaxonroman
language?
This is simple: they have to select another encoding.
Wasn't my argument clear? Again:
(1) UTF-8 practically only works for english texts, and does not work
with ae oe ue and so on
(2) ISO-8850-1 works for Western-E
I use Tomcat 4 and Cocoon 2 and SQLTransformer, mySQL.
Interestingly, everything works fine on Windows XP; German Umlauts are
entered correctly into the database, and displayed correctly when HTML
is created from the table.
The *same* sitemap file (with added tags in sql, xsl and html
transfo
On Fri, 2003-06-06 at 23:59, morten svanæs wrote:
> - Original Message -
> From: "morten svanæs" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 2:53 PM
> Subject: Re: Encoding problems in flowscript
>
>
> >
- Original Message -
From: "morten svanæs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 2:53 PM
Subject: Re: Encoding problems in flowscript
>
> - Original Message -
> From: "Bruno Dumon" <[EMAIL PROTECTE
- Original Message -
From: "Bruno Dumon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 5:37 AM
Subject: Re: Encoding problems in flowscript
> On Fri, 2003-06-06 at 22:56, morten svanæs wrote:
> > Hi,
> > I'm having
On 6/06/2003 11:55 Alexander Schatten wrote:
and moreover: I do not understand why this iso setting is not the
default setting: because it works with all characters english as well as
german... so why not use this one as default, would be less confusing
for all, no?
How about all these people _
ve UTF-8 enconding and headers, my serialzers in the
> > sitemap also have encoding parameters set to UTF-8.
> > My modeldata is correctly inserted into the forms, but as
> > soon as I submit the norwegian characters are misinte
sinterpreted. All my documents
> have UTF-8 enconding and headers, my serialzers in the
> sitemap also have encoding parameters set to UTF-8.
> My modeldata is correctly inserted into the forms, but as
> soon as I submit the norwegian characters are misinterpred.
Have you enabled th
rs in the
sitemap also have encoding parameters set to UTF-8.
My modeldata is correctly inserted into the forms, but as
soon as I submit the norwegian characters are misinterpred.
My language of choice in the flowscript is javascript.
I'm running the 2.1-m2 with tomcat 4.1.24 with
j2se 1.4.1
Matthias Brunner wrote:
That should really be documented somewhere. I believe, however, that
the approach itself (having to set an environment variable for the
JVM) is really flawed. I do not understand why this is necessary at
all, since there are XML headers which set the encoding of every
Le Vendredi, 6 juin 2003, à 11:20 Europe/Zurich, Matthias Brunner a
écrit :
...That should really be documented somewhere
I have put some information at
http://wiki.cocoondev.org/Wiki.jsp?page=SettingTheJvmLocale
...Maybe there is a parameter to
the JVM as well, which would be better to use
t;
> GREAT! thank you, that was the solution; it works on all systems
> now correctly.
>
> however, I believe one should add this encoding point into the
> documentation, because as far as I know neither the fact, that
> there is an tag nor your important fact about this
>
out.
GREAT! thank you, that was the solution; it works on all systems now
correctly.
however, I believe one should add this encoding point into the
documentation, because as far as I know neither the fact, that there is
an tag nor your important fact about this environment var
seems to
On Thursday 05 June 2003 23:46, Alexander Schatten wrote:
> I use Tomcat 4 and Cocoon 2 and SQLTransformer, mySQL.
>
> Interestingly, everything works fine on Windows XP; German Umlauts
> are entered correctly into the database, and displayed correctly
> when HTML is created from the table.
>
> The
Bertrand,
Thank you very much for your help!!! The html encoding was the problem!!! You are
the man!!! I'm just so happy that it works.
Charlene
-Original Message-
From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 3:25 AM
To: [EMAIL PROT
x27;s
StreamGenerator is used to read your XML from an HTML form field.
Your encoding problem is caused by the StreamGenerator using the wrong
encoding when *reading data* from the form's POST request. To use a
different encoding, you have to change the HTML code of the form,
replacing
bject: Re: jfor encoding problem
Le Lundi, 2 juin 2003, à 21:51 Europe/Zurich, Yan, Charlene a écrit :
> ...
> I'm trying to display accented characters correctly using jfor.
> However, when I try to run
> http://localhost:8080/cocoon/samples/jfor/minimal.rtf, it gives the
&g
bject: Re: jfor encoding problem
Le Lundi, 2 juin 2003, à 21:51 Europe/Zurich, Yan, Charlene a écrit :
> ...
> I'm trying to display accented characters correctly using jfor.
> However, when I try to run
> http://localhost:8080/cocoon/samples/jfor/minimal.rtf, it gives the
&g
Le Mardi, 3 juin 2003, à 07:40 Europe/Zurich, Bertrand Delacretaz a
écrit :
...Is the encoding declaration correct in your input XML?
Sorry, didn't notice that this was answered already (but I had two
other messages from the same person at my private address ;-)
-Ber
ch as "Gére" in
the xml file...
Is the encoding declaration correct in your input XML?
Can you parse it with another tool (XML editor or parser)?
If you can reduce your input to the smallest XML file that causes the
problem, you could post it here so that someone can test it.
Con,
Thanks for your reply. You are right that I should have encoding="ISO-8859-1" in the
prolog. My current xml string doesn't have any declaration in the front. That's
causing the problem.
Thanks again!
Charlene
-Original Message-
From: Conal Tuohy [mailto:[E
encoding declaration to the start of the
file. e.g.
Cheers
Con
> -Original Message-
> From: Yan, Charlene [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 3 June 2003 07:52
> To: [EMAIL PROTECTED]
> Subject: jfor encoding problem
>
>
> Hi everyone,
>
> I'm tr
Hi everyone,
I'm trying to display accented characters correctly using jfor. However, when I try
to run http://localhost:8080/cocoon/samples/jfor/minimal.rtf, it gives the following
exception. I have put some French words such as "Gére" in the xml file. Looks like
it is a parser issue. Anyo
originale-
Da: Bruno Dumon [mailto:[EMAIL PROTECTED]
Inviato: venerdì 23 maggio 2003 11.09
A: [EMAIL PROTECTED]
Oggetto: Re: R: R: encoding url for reader / better ways pass
strings to areader?
On Fri, 2003-05-23 at 09:43, Andrea Pierini wrote:
[...]
** begin action code
WHAT I WANT
serialize XHTML in ISO-8859-1
encoding
PROBLEM
Even if I tell the serializer to
use ISO-8859-1 encoding, it keeps generating UTF-8 encoding
WHAT I DID
1) Sitemap: Configured a XHTML
serializer
name="xhtml"
pool-grow="2" pool-
publishing system is on a Mac and using
Mac roman encoding if this is an issue?
no this should be no issue.
The input is:
Tim¹s ³good² day
The output is:
Tim”¥ús ”¥good”¥ÿ day
The only problem in the above is the <, so you must preprocess the
document and replace < with <. Same for & =>
Mac roman encoding if this is an issue?
The input is:
Tim¹s ³good² day
The output is:
Tim¥ús ¥good¥ÿ day
Any ideas?
Cheers
Tim Cavanagh
DMIT
South Australia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
THis error means that the eclaration of the sitemap is UTF-8 and you insert
ISO character in it maybe in comment)
.At 15:44 25/03/2003 +0100, you wrote:
hello,
any one ever have this problem with the Webserviceproxy mode ? :
org.apache.cocoon.ProcessingException : Failed to execute pipeline :
This method works well.
But for me it's more complicated.
In my case, The URL should go from the xsp (which have the good encoding)
through an xsl page in a element as "src" attribute. But at this
moment, characters are converted into UTF-8, which I don't want.
Does I rea
hello,
any one ever have this problem with the Webserviceproxy mode ? :
org.apache.cocoon.ProcessingException : Failed to execute pipeline :
java.io.UTFDataFormat Exception : Invalid byte 2 of 3 byte UTF-8 sequence
-
To unsub
to have the right caracter-set in sitamap.xmap write this :
iso-8859-1
iso-8859-1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:25 PM
To: [EMAIL PROTECTED]
Subject: RE: Encoding
What about the container-encoding?
Btw, I never had problems with encoding in i18n samples, cause I always use
UTF-8 everywhere. Use Unicode and you'll have much less problems. In
cocoon/samples/i18n/simple.xsp there is an explicit conversion for UTF-8 to
container-encoding and it works fo
In the doc it's written about setting this in web.xml :
form-encoding
utf-8
But it doesn't change anything with cocoon 2.0!
-Original Message-
From: Konstantin Piroumian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 2:55 PM
To: [EMAIL PROTECTED]
Subject: Re
You can set container-encoding and form-encoding initialization parameters
in web.xml . Take a look at the web.xml from Cocoon distribution, there's a
comment about it.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 25, 2003
: Encoding problems
On Tue, 25 Mar 2003 14:12:59 +0100
<[EMAIL PROTECTED]> wrote:
> Hi,
> I have xsp pages, and all my parameters with accents (И, Х, Т,...) changes into
> things like "ц╘",...
> I tried diferent encoding into my pages (like encoding="ISO-8859-1"?>
On Tue, 25 Mar 2003 14:12:59 +0100
<[EMAIL PROTECTED]> wrote:
> Hi,
> I have xsp pages, and all my parameters with accents (И, Х, Т,...) changes into
> things like "ц╘",...
> I tried diferent encoding into my pages (like encoding="ISO-8859-1"?>), but not
Hi,
I have xsp pages, and all my parameters with accents (é, è, ô,...) changes into things
like "é",...
I tried diferent encoding into my pages (like ), but nothing seems to work!
how can I keep the accents?
Thanks
--
Hello,
I'm having trouble with my xsp page and ISO-8859-1 encoding. I use
cocoon-2.0.4.
I have an xsp which get the request object of a form and create again a
link for an xsl page which redirect all to frame.
All generators, transfomers and serializer have to parameter.
the si
es an html page
and the .js file is then loaded as an included, also served by Cocoon. Any
tricks to using the resource reader? My map:read tag has two parameters,
type="resource" and src. Do I need to specify encoding or mime-type to
guarantee the accurate reading of text
pend(id);
That doesn't work...the is still have the header ISO-8859-1 encoding.
At 14:45 10/03/2003 +0100, you wrote:
Lionel Crine <[EMAIL PROTECTED]> writes:
> I'd like to change the default encoding in my custom transformer, how
> can I do that ?
How is a transforme
est.append(id);
That doesn't work...the is still have the header ISO-8859-1 encoding.
At 14:45 10/03/2003 +0100, you wrote:
Lionel Crine <[EMAIL PROTECTED]> writes:
> I'd like to change the default encoding in my custom transformer, how
> can I do that ?
How is a tr
Lionel Crine <[EMAIL PROTECTED]> writes:
> I'd like to change the default encoding in my custom transformer, how
> can I do that ?
How is a transformer related to encoding? It's a internal
component and is working on java strings only (unless it is
reading additional data
I'd like to change the default encoding in my custom transformer, how can I
do that ?
Lionel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Gallardo [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 7. März 2003 14:40
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: AW: encoding and xsp
>
>
> Hi:
>
> Take it easy! This is a standard problem when you start to using Cocoon.
> :-D
>
> What I am trying to said is th
Gallardo [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 7. März 2003 14:40
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: encoding and xsp
Hi:
Take it easy! This is a standard problem when you start to using Cocoon. :-D
What I am trying to said is that only putting the header is not enough. Just for
you jEdit.
(http://www.jEdit.org) to write XML stuff.
In jEdit you have "buffer options" that allow you to define the character
encoding for your saved files. That means How the file will be encoded
BEFORE is saved into the hard disk. Of course the headers are importants
too.
Please fe
I am not shure what you mean, but i added to the header of all xsp and xsl document
the same encoding sceme!
-Ursprüngliche Nachricht-
Von: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 7. März 2003 14:27
An: [EMAIL PROTECTED]
Betreff: Re: AW: encoding and xsp
Hi
Hi!
Please note that you must be sure that you are using the correct encoding
to save your files.
Antonio Gallardo.
> hi,
>
> thanks for your hints. i tried it, but it still does not work. i was not
> sure, if you mean to specifiy it within the , or
> i did it in both. i al
if i
read through the outputtet html, there is still a tag like:
-Ursprüngliche Nachricht-Von: Andres, Judith
[mailto:[EMAIL PROTECTED] Gesendet: Freitag, 7. März
2003 09:42An: [EMAIL PROTECTED]Betreff: AW:
encoding and xsp
Try specifying
an encoding inside
Judith is correct, you should put this encoding in the ,
but,
if you use or whatever, put it also in the transformer and generator.
Second thing, since you are German, so in the Euro zone, you may consider the
ISO-8859-15 encoding, which is the same as the -1 encoding, but includes the
Euro
Title: Nachricht
Try specifying an
encoding inside the serializer declaration in your sitemap:
ISO-8859-1
HTH Judith
-Ursprüngliche Nachricht-Von: boessem
[mailto:[EMAIL PROTECTED]Gesendet: Freitag, 7. März 2003
09:39An: Cocoon
Title: Nachricht
hi,
i do not understand
why the encoding works different for words i use wihtin the xsp document and
words i get via the url.
an
example:
I have got a form,
where students should be able to apply for a specific exame. wihtin this form (a
xsp document) there are some
Title: Nachricht
hi,
does anyone know why
when using xsp or espacially esql, all characters like ä,ö,ü etc. are turned
into funny characters like Ã(ö).
i am trying to
firgure out why that happens, and what unicode i have to use for languages using
those characters, like e.g. german.
th
Thanks Jens and the others that responded so promptly !
that works now - xalan does recognise
'disable-output-escaping'
I used
Regards,
Holger
[EMAIL PROTECTED] wrote:
>
>
> Hi,
>
> > I am using the standard Cocoon config (Xalan, Xerces
> ..)
> The default Transformer is XSLTC. It is conf
Hi,
> I am using the standard Cocoon config (Xalan, Xerces ..)
The default Transformer is XSLTC. It is configured
in the sitemap.xmap in your cocoon folder.
Just search for map:transformers. You will
find there a transformer named 'xalan' and one
named 'xsltc' (and course many other transformers)
Hi Jens,
thanks for your ultra-fast reply.
I am using the standard Cocoon config (Xalan, Xerces ..)
Here is a fragment of the (trivial) sitemap:
What is xsltc ???
-Holger
Jens Maukisch wrote:
>
> Hi,
>
> >
[EMAIL PROTECTED] wrote:
entity encoding error within an inline java script
Dear all,
I have a stylesheet with inline javascript.
I use CDATA and as follows to avoid coding
entities:
...
Hi,
>
entity encoding error within an inline java script
Dear all,
I have a stylesheet with inline javascript.
I use CDATA and as follows to avoid coding
entities:
...
> > But it seems setting only charset attribute in html tag and not
> > infuencing
> > http header.
> >
> > Artur
>
> Use action org.apache.cocoon.acting.SetCharacterEncodingAction
>
Not helping either. The Content-Type header contain
On Fri, 28 Feb 2003 12:36:00 +0100, arturl <[EMAIL PROTECTED]> wrote:
But it seems setting only charset attribute in html tag and not
infuencing
http header.
Artur
Use action org.apache.cocoon.acting.SetCharacterEncodingAction
Regards
But it seems setting only charset attribute in html tag and not
infuencing
http header.
Artur
- Original Message -
From: "BOCEK Michal" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 12:15 PM
Subject: RE: encoding
> Hi
> this f
Hi
this feature set in sitema.xmap on serializers.
1024
-//W3C//DTD HTML 4.0 Transitional//EN
windows-1250
Michal
-Original Message-
From: arturl [mailto:[EMAIL PROTECTED]
Sent: Friday, February 28, 2003 12:22 PM
To: [EMAIL PROTECTED]
Subject: encoding
Hello,
What component
Hello,
What component (and what configuration is needed) is responsible for setting
the Content-Type http response header with charset specified?
Thx,
Artur
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Hello gurus of cocoon.
I have a problem with encoding. I use a simple input XML-file (2.xml)
with 4 internationalization characters (Russian).
http://apache.org/xsp";>
Ñ'Ð÷Ñ_Ñ'123
And two entries in the sitemap.xconf:
// Just generate and serialize
// Generate serv
Try using
after the xml declaration in the stylesheet
Oskar
I 'd like to change the encoding in the header of my file.
How can I do that.
For example with DOM I do :
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer();
java.util.Properties properties = transformer.getOutputPrope
it passes an
not-encoded URL String to tamino, which tamino refuses because it isn't
encoded (it has whitespaces and not %20's)
Or is the problem with the Matcher not encoding the parameter ??
Is this reported somehere ?
Any help please ?
Thanks !
[--] Rui Pedro Leal
[--] [EMAIL PR
--- Reçu de INFETUDE.G145193 02/250.96.71 17-01-03 10.59
--- Reçu de INFETUDE.G145193 02/250.96.71 17-01-03 08.26
Hi.
I have add de next line in web.xml of my application but whitout effect
container-encoding
ISO-8859-1
form
I think these kind of problem because of servlet container's illegal
encoding interpreation. Cocoon fix this by wrapping a real request
object obtained from container to
org.apache.cocoon.environment.HttpRequest as you now. But in you case a
JspGenerator invokes a real page using the unwr
Artur Bialecki wrote:
I looked at the javadoc for java.lang package (jdk1.3.1)
and java.nio.charset.Charset (jdk1.4.1) and it
looks like the UTF-8 is the correct name.
I have a feeling setting the container encoding to ISO-8859-1
is what fixed your problem.
Another word of caution is the
I looked at the javadoc for java.lang package (jdk1.3.1)
and java.nio.charset.Charset (jdk1.4.1) and it
looks like the UTF-8 is the correct name.
I have a feeling setting the container encoding to ISO-8859-1
is what fixed your problem.
Another word of caution is the java.net.URLEncoder class
prets them as ISO-8859-1. The problem can be seen e.g. with form
validator: if you enter a non-ASCII7 character, and there is something not
correct for the form validator within ANOTHER field, you get the first
field back changed.
I have enabled "container-encoding" and "form-encod
Hi Yury,
so we agree? The bug is in HTMLGenerator, but the expected encoding
isn't UTF-8 (reading from http://www.w3.org/ doesn't work for me
(NullPointerException)), but ISO-8859-1 or maybe the default encoding of
the JVM. Can you file a bug in bugzilla?
Regards,
Joerg
Yury Mikhi
Hello Martin,
we solved it simply by changing the output encoding of the files to
ISO-8859-1. The browsers send their requests in the document encoding.
Maybe this is a simple solution for you too.
Regards,
Joerg
Martin Koeppe wrote:
Hello,
I'm using a recent developer version of cocoo
Hi Joerg!
Thanx for your reply.
The pure Tidy works properly (output stream encoding is the same as the input stream
encoding).
The problem, from my point of view, is in transformer (or streamer [if xpath is null
value]) input stream encoding (HTMLGenerator),
because Tidy DOM parser returns
859-1. The problem can be seen e.g. with form
validator: if you enter a non-ASCII7 character, and there is something not
correct for the form validator within ANOTHER field, you get the first
field back changed.
I have enabled "container-encoding" and "form-encoding" in web.xm
ter, that's not directly available in this
encoding, must be expressed/referenced by such a reference.
I hope, I didn't say anything wrong ;-) Yuri, I think it's the best to
post a bug in bugzilla at http://nagoya.apache.org/bugzilla/.
Regards,
Joerg
Yury Mikhienko wrote:
Hi all
Hi all!
Can anyone help me with the following problem:
I have a KOI8-R encoded HTML document. After processing this document with
HTMLGenerator, in output I have ISO-8859-1 encoded document :((
for example
The source document:
(from URL: /test)
ðÒÉ×ÅÔ!
ðÒÉ×ÅÔ!
(in sitemap.xmap):
Hi all!
Can anyone help me with the following problem:
I have a KOI8-R encoded HTML document. After processing this document with
HTMLGenerator, in output I have ISO-8859-1 encoded document :((
for example (in sitemap.xmap):
1024
KOI8-R
http://localhost/cgi-bin
PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 20, 2002 11:10 AM
Subject: RE: URL Encoding
> Hi Ludovic,
>
> you can have problems because the URL encoder probably does encode the
> leading semicolon and the equals symbol of the URL if you use URL
rewriting.
> Mayb
Hi Ludovic,
you can have problems because the URL encoder probably does encode the
leading semicolon and the equals symbol of the URL if you use URL rewriting.
Maybe you have to write a short method which avoids encoding these leading
characters.
Best regards
- Volker -
-Original Message
Hi All,
In an Action i want to encode an URL on the HttpResponse to have the session
Id on this URL.
url =
((org.apache.cocoon.environment.http.HttpResponse)(ObjectModelHelper.getResp
onse(objectModel))).encodeURL(url);
But my URL is not encoded.
I don't find where to configure if encodi
>
>
>
>
>
>
>
> They suggest to use the SetCharacterEncodingAction, but it hasn't solved my problem.
>
> MySQL uses the default ISO-8859-1 encoding and I've added the ISO-8859-1 encoding to
>the html serializer:
>
>
> ISO-8859
amp;m=103701015026425&w=2
about a similar subject, but the author speak of a request generator and an XML
serializer, while I'm using an xsp generator and an html serializer:
They suggest to use the SetCharacterEncodingAction, but it hasn't solved my problem.
Yves Vindevogel wrote:
Hi All,
My problem is solved thanks to your help (all of you)
Therefore, I'd like to post what I did because I had some mails from people
from Italy and Zwitserland with the same problem. This is kind of my help
towards them.
Good thinking!
Now please go and add it to
Hi All,
My problem is solved thanks to your help (all of you)
Therefore, I'd like to post what I did because I had some mails from people
from Italy and Zwitserland with the same problem. This is kind of my help
towards them.
I changed my sitemap:
nd Postgres 7 on Slackware 8, JDK 1.4.
My database and pages contain French characters (like é,à,ç, ...)
I use XSP to get the data from PG.
I can show all the data correctly when I set the encoding to ISO-8859-1.
I wrote some plsql procedures to store data. I call them from my XSP pages.
This is
I didn't have this ...
I recreated the database with this encoding in it
but it still doesn't work
> On Wednesday 11 December 2002 10:32, Yves Vindevogel wrote:
> > I'm using Cocoon 2 and Postgres 7 on Slackware 8, JDK 1.4.
> > My database and pages contain
line with the French
> characters works fine. It's only when I post the page and call
> the function that it goes wrong.
>
Is multibyte encoding enabled in the database (e.g. createdb -E
ISO-8859-1 mydb)?
Best regards!
--
Matthias Brunner <[EMAIL PROTECTED]>
PGP FP 7862 32B3 3B75 2
Hi,
I'm using Cocoon 2 and Postgres 7 on Slackware 8, JDK 1.4.
My database and pages contain French characters (like é,à,ç, ...)
I use XSP to get the data from PG.
I can show all the data correctly when I set the encoding to ISO-8859-1.
I wrote some plsql procedures to store data. I call
t;, the data is properly stored.
MYSQL use the default ISO-8859-1 encoding.
I've not changed the default cocoon encodings, except for:
ISO-8859-1
1024
Any suggestion?
-
Please check that your question
It seems that the only way to output request parameters
encoded with UTF-8 is to call request.setCharacterEncoding("utf-8");
on **every** request. Is there a better (simpler) way of achieving
end-to-end UTF-8 for the whole site?
Also, setting encoding will call the decode() method
on ev
1 - 100 of 341 matches
Mail list logo
