Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

Alex,

I just copied my cocoon directory in a Tomcat 5 installation.  
The problem persists.  So, it's not Jetty related either

BUT ... 

looking into the stacktrace a bit better, i notice this

Original Exception: org.apache.avalon.framework.CascadingRuntimeException: Error getting ascii data for column region
at org.apache.cocoon.components.language.markup.xsp.EsqlHelper.getAscii(EsqlHelper.java:305)

I use XSP as generator, and obviously, ESQL is trying to fetch ASCII values.  There's no ASCII in my DB, it's French characters.
Thus, could this be the reason ?

How can I tell esql not to use the getAscii but to use another function that works correctly with unicode or whatever that can depict french chars (or german umlauts, right alex?)



On 28 Mar 2004, at 23:10, Alexander Schatten wrote:

Yves Vindevogel wrote:

I see  could you please tell me how to setup Tomcat 5 so that it works with Cocoon 2.1. Or a document on line ?
This way, I could set up that solution and test if my problem is Jetty related. Because ... all my previous installations were on Tomcat.
Might be Jetty related ...

If Alexander Schatten reads this: what do you think ?
Is your problem also only on installations with Jetty ?

this is a good question, I also thought about this recently; unfortunately I am completly full with work and had no time to transfer everything to tomcat (not only Cocoon, but also the JDBC driver, the applications.,..)


but as this is the only difference between my machines, it could be possible: on the Linux server I user tomcat, as I do not like jetty in the production environment;

I think I need to test tomcat/cocoon also on OS X...


Alex


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements

Mail: [EMAIL PROTECTED]  - Mobile: +32 (478) 80 82 91

Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Markt 18c  -  9700 Oudenaarde  -  Tel: +32 (55) 30 55 76

Web: http://www.implements.be

First they ignore you.  Then they laugh at you.  Then they fight you.  Then you win.
Mahatma Ghandi.

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Stephen Winnall]

I am not aware of having done anything special to install Tomcat under 
Mac OS X.
As far as I recall, I downloaded jakarta-tomcat-5.0.16.tar.gz from 
Apache,
expanded it and started Tomcat with the bin/startup.sh which it 
contains.

I built a WAR file from Cocoon with ant, copied it into the webapps 
directory and
built my application on top of that.

I start Tomcat automatically at startup from 
/System/Library/StartupItems on port
8080 (which is the Mac OS X equivalent of /etc/init.d), but this is 
convenience
rather than functionality.

Steve

On 28 Mar 2004, at 23:10, Alexander Schatten wrote:

Yves Vindevogel wrote:

I see  could you please tell me how to setup Tomcat 5 so that it 
works with Cocoon 2.1. Or a document on line ?
This way, I could set up that solution and test if my problem is 
Jetty related. Because ... all my previous installations were on 
Tomcat.
Might be Jetty related ...

If Alexander Schatten reads this: what do you think ?
Is your problem also only on installations with Jetty ?
this is a good question, I also thought about this recently; 
unfortunately I am completly full with work and had no time to 
transfer everything to tomcat (not only Cocoon, but also the JDBC 
driver, the applications.,..)

but as this is the only difference between my machines, it could be 
possible: on the Linux server I user tomcat, as I do not like jetty in 
the production environment;

I think I need to test tomcat/cocoon also on OS X...

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

Yves Vindevogel wrote:

I see  could you please tell me how to setup Tomcat 5 so that it 
works with Cocoon 2.1. Or a document on line ?
This way, I could set up that solution and test if my problem is Jetty 
related. Because ... all my previous installations were on Tomcat.
Might be Jetty related ...

If Alexander Schatten reads this: what do you think ?
Is your problem also only on installations with Jetty ?
this is a good question, I also thought about this recently; 
unfortunately I am completly full with work and had no time to transfer 
everything to tomcat (not only Cocoon, but also the JDBC driver, the 
applications.,..)

but as this is the only difference between my machines, it could be 
possible: on the Linux server I user tomcat, as I do not like jetty in 
the production environment;

I think I need to test tomcat/cocoon also on OS X...

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Jorg Heymans]

I downloaded Cocoon 2.0.4 (latest from 2.0 series) with VM 1.4
I dropped the cocoon.war in the webapps.  Tomcat unpacks it.
I try to open the :8080/cocoon folder and I get this error
Failed to generate program code (this may happen if you use Xalan in 
incremental processing mode). Please check log file and/or console for 
errors.
endorsed lib problem?

Okay, away went version 4 of Tomcat

I unpacked Tomcat 5, started it and there it was ...
Dropped the war again in the webapps.
Tomcat unpacked it, but I could not connect to :8080/cocoon
The requested resource (/cocoon/) is not available.
you might need to setup a context for it, not sure.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

I see  could you please tell me how to setup Tomcat 5 so that it works with Cocoon 2.1.  Or a document on line ?
This way, I could set up that solution and test if my problem is Jetty related.  Because ... all my previous installations were on Tomcat.
Might be Jetty related ...

If Alexander Schatten reads this: what do you think ?  
Is your problem also only on installations with Jetty ?

On 28 Mar 2004, at 13:20, Stephen Winnall wrote:

On 28 Mar 2004, at 12:39, Yves Vindevogel wrote:

But why do you need them ??
You can startup Cocoon 2.1 with Jetty (cocoon.sh servlet)
There's no need for Tomcat 

Ah...! No good reason really: I first used Tomcat when it was version
1.x and haven't had any reason to change. And since I am more interested
in Cocoon, content and multimodal presentation than Java and its
various containers, the question of Jetty or Tomcat has never been a
point of interest for me. I know lots of people prefer Jetty and I
respect that (the same applies to those who prefer Tomcat), but I am
neutral on this issue because my focus is elsewhere.

Steve


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements

Mail: [EMAIL PROTECTED]  - Mobile: +32 (478) 80 82 91

Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Markt 18c  -  9700 Oudenaarde  -  Tel: +32 (55) 30 55 76

Web: http://www.implements.be

First they ignore you.  Then they laugh at you.  Then they fight you.  Then you win.
Mahatma Ghandi.

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Stephen Winnall]

On 28 Mar 2004, at 12:39, Yves Vindevogel wrote:

But why do you need them ??
You can startup Cocoon 2.1 with Jetty (cocoon.sh servlet)
There's no need for Tomcat 
Ah...! No good reason really: I first used Tomcat when it was version
1.x and haven't had any reason to change. And since I am more interested
in Cocoon, content and multimodal presentation than Java and its
various containers, the question of Jetty or Tomcat has never been a
point of interest for me. I know lots of people prefer Jetty and I
respect that (the same applies to those who prefer Tomcat), but I am
neutral on this issue because my focus is elsewhere.
Steve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

But why do you need them ??
You can startup Cocoon 2.1 with Jetty (cocoon.sh servlet)
There's no need for Tomcat 

On 28 Mar 2004, at 00:46, Stephen Winnall wrote:

On 27 Mar 2004, at 12:57, Yves Vindevogel wrote:

Why do you use Tomcat 5 and Cocoon 2.1 together ?
Cocoon 2.1.x runs with Jetty here, on both machines.

I use them because they are the most recent versions, and I have no reason
not to use them (i.e. they work).


Are you sure you combine both ?

I use
- Cocoon 2.1.4
- Tomcat 5.0.16
on Mac OS X 10.3.3 with Java 1.4.2_03.

Steve


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements

Mail: [EMAIL PROTECTED]  - Mobile: +32 (478) 80 82 91

Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Markt 18c  -  9700 Oudenaarde  -  Tel: +32 (55) 30 55 76

Web: http://www.implements.be

First they ignore you.  Then they laugh at you.  Then they fight you.  Then you win.
Mahatma Ghandi.

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Stephen Winnall]

On 27 Mar 2004, at 12:57, Yves Vindevogel wrote:

Why do you use Tomcat 5 and Cocoon 2.1 together ?
Cocoon 2.1.x runs with Jetty here, on both machines.
I use them because they are the most recent versions, and I have no 
reason
not to use them (i.e. they work).


Are you sure you combine both ?
I use
- Cocoon 2.1.4
- Tomcat 5.0.16
on Mac OS X 10.3.3 with Java 1.4.2_03.
Steve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

Why do you use Tomcat 5 and Cocoon 2.1 together ?  
Cocoon 2.1.x runs with Jetty here, on both machines.

I think the "slow" startup is due to the way Tomcat works, I guess.
Anyway, the latest versions of both are not functioning, but maybe I should let it do its thing for 2 minutes.

Are you sure you combine both ?

On 27 Mar 2004, at 11:38, Stephen Winnall wrote:

I run Tomcat 5 under Mac OS X 10.3.3 (and 10.3.2 before that) with no problems.
What I have noticed is that it takes Cocoon a long time to start up when Tomcat
is (re)started, which might explain your error message. I am using Cocoon 2.1.4.

Steve

On 26 Mar 2004, at 20:51, Yves Vindevogel wrote:

Ok, I got my database going again on a different machine.  I now use Panther with the JVM that comes with it.
I use the driver compiled by postgresql, and have already tested the one from their site.  No solution.

When I use a basic XSP, with strange chars, it works.
So, it's only when I use the database connection from XSP.

I then used the transformer instead of the generator: same problem ...

Okay, so no much further.
I downloaded Tomcat 4 and 5
First I installed Tomcat 4.  It runs nicely.

I downloaded Cocoon 2.0.4 (latest from 2.0 series) with VM 1.4
I dropped the cocoon.war in the webapps.  Tomcat unpacks it.
I try to open the :8080/cocoon folder and I get this error

Failed to generate program code (this may happen if you use Xalan in incremental processing mode). Please check log file and/or console for errors.

Okay, away went version 4 of Tomcat

I unpacked Tomcat 5, started it and there it was ...
Dropped the war again in the webapps.
Tomcat unpacked it, but I could not connect to :8080/cocoon

The requested resource (/cocoon/) is not available.

Now that's strange to me  The directory is there.  I don't know why it's not found.
Do I need to "register" it first under Tomcat 5 ?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements

Mail: [EMAIL PROTECTED]  - Mobile: +32 (478) 80 82 91

Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Markt 18c  -  9700 Oudenaarde  -  Tel: +32 (55) 30 55 76

Web: http://www.implements.be

First they ignore you.  Then they laugh at you.  Then they fight you.  Then you win.
Mahatma Ghandi.

Re: Character encoding...

[Joerg Heinicke]

On 27.03.2004 11:26, beyaNet Consultancy wrote:
Hi Marc,
I am trying to achieve the following:
1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible.  
If it is, the XHTML 1.1 serializer is used, which when view sourced in  
the browser you see:


http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>

Now, as part of the XHTML 1.1 specification you also need to say the  
following in the  tag:

http://www.w3.org/1999/xhtml";>

I have not found a way in the serialization process of writing the  
xmlns line into the  tag if the browser viewing the site is XHTML  
1.1 compatible, so I thought maybe if I specify UTF-8 as the encoding  
type for XHTML 1.1 browsers and a different encoding type for non 1.1  
browsers, I could then dynamically write the xmlns line into the tag if  
the browser was XHTML 1.1 compatible.

Do you know of a more efficient way I could probably do this?

Peter
This is only possible by operating on the XML stream, for example using 
an additional stylesheet that puts all your HTML elements into XHTML 
namespace. But wouldn't it be possible to put them always in that 
namespace, i.e. does not the HTMLSerializer remove this namespace?

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Stephen Winnall]

I run Tomcat 5 under Mac OS X 10.3.3 (and 10.3.2 before that) with no 
problems.
What I have noticed is that it takes Cocoon a long time to start up 
when Tomcat
is (re)started, which might explain your error message. I am using 
Cocoon 2.1.4.

Steve

On 26 Mar 2004, at 20:51, Yves Vindevogel wrote:

Ok, I got my database going again on a different machine.  I now use 
Panther with the JVM that comes with it.
I use the driver compiled by postgresql, and have already tested the 
one from their site.  No solution.

When I use a basic XSP, with strange chars, it works.
So, it's only when I use the database connection from XSP.
I then used the transformer instead of the generator: same problem ...

Okay, so no much further.
I downloaded Tomcat 4 and 5
First I installed Tomcat 4.  It runs nicely.
I downloaded Cocoon 2.0.4 (latest from 2.0 series) with VM 1.4
I dropped the cocoon.war in the webapps.  Tomcat unpacks it.
I try to open the :8080/cocoon folder and I get this error
Failed to generate program code (this may happen if you use Xalan in 
incremental processing mode). Please check log file and/or console for 
errors.

Okay, away went version 4 of Tomcat

I unpacked Tomcat 5, started it and there it was ...
Dropped the war again in the webapps.
Tomcat unpacked it, but I could not connect to :8080/cocoon
The requested resource (/cocoon/) is not available.

Now that's strange to me  The directory is there.  I don't know 
why it's not found.
Do I need to "register" it first under Tomcat 5 ?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Character encoding...

[beyaNet Consultancy]

Hi Marc,
I am trying to achieve the following:

1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible. If it is, the XHTML 1.1 serializer is used, which when view sourced in the browser you see:




Now, as part of the XHTML 1.1 specification you also need to say the following in the  tag:



I have not found a way in the serialization process of writing the xmlns line into the  tag if the browser viewing the site is XHTML 1.1 compatible, so I thought maybe if I specify UTF-8 as the encoding type for XHTML 1.1 browsers and a different encoding type for non 1.1 browsers, I could then dynamically write the xmlns line into the tag if the browser was XHTML 1.1 compatible.

Do you know of a more efficient way I could probably do this?

Peter

p.s.

sitemap snippet:

		

-//W3C//DTD XHTML 1.1 //EN










			



-//W3C//DTD XHTML 1.0 Transitional//EN




		










...

			




On 27 Mar 2004, at 07:30, Marc Portier wrote:

Peter,

sorry for the bad advice then, but you lost me,
pls elaborate on where you see what and how your setup is looking
and what you try to achieve

regards,
-marc=

beyaNet Consultancy wrote:

Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned, but nothing has really changed. If I now  and change the encoding in the page so that it now reads  i still only get what is specified in the web.xml document and not in the web-page. Any ideas?
Peter
On 26 Mar 2004, at 23:08, Marc Portier wrote:
beyaNet Consultancy wrote:
Hi,
I am trying to obtain the encoding type as specified in at the
top of my site page when you view source the page. At the moment
the encoding type is specified as:


"http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd">

I was under the impression that if i used
 that it would return UTF-8,
in this instance. At the moment it is returning ISO-8859-1 which
is the encoding type of the server. How do I get the encoding
type as specified within my page?
which version of cocoon are you using?
pre 2.1.3 there was a possible mismatch between the encoding used in
the html-generation (encoding) and the one used in the
request-parameter-processing (decoding)
this should be fixed per

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/serialization/AbstractTextSerializer.java?rev=1.6&view=markup

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/servlet/CocoonServlet.java?rev=1.20&view=markup
prior to this you can manually assure that both sides are in sync:
just make sure the encoding set-up in your  (see it's
config in sitemap.xmap) is matching the setting in the web.xml (see
init-param 'form-encoding' to the cocoon servlet)
HTH,
-marc=
many thanks in advance
Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED] [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED]  [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Character encoding...

[Marc Portier]

Peter,

sorry for the bad advice then, but you lost me,
pls elaborate on where you see what and how your setup is looking
and what you try to achieve
regards,
-marc=
beyaNet Consultancy wrote:

Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned, 
but nothing has really changed. If I now 
 and change the encoding in the page 
so that it now reads  i still 
only get what is specified in the web.xml document and not in the 
web-page. Any ideas?

Peter
On 26 Mar 2004, at 23:08, Marc Portier wrote:


beyaNet Consultancy wrote:

Hi,
I am trying to obtain the encoding type as specified in at the
top of my site page when you view source the page. At the moment
the encoding type is specified as:

http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>

I was under the impression that if i used
 that it would return UTF-8,
in this instance. At the moment it is returning ISO-8859-1 which
    is the encoding type of the server. How do I get the encoding
type as specified within my page?
which version of cocoon are you using?

pre 2.1.3 there was a possible mismatch between the encoding used in
the html-generation (encoding) and the one used in the
request-parameter-processing (decoding)
this should be fixed per

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/serialization/AbstractTextSerializer.java?rev=1.6&view=markup
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/servlet/CocoonServlet.java?rev=1.20&view=markup

prior to this you can manually assure that both sides are in sync:
just make sure the encoding set-up in your  (see it's
config in sitemap.xmap) is matching the setting in the web.xml (see
init-param 'form-encoding' to the cocoon servlet)
HTH,
-marc=
many thanks in advance
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED] [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Character encoding...

[beyaNet Consultancy]

Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned, but nothing has really changed. If I now  and change the encoding in the page so that it now reads ISO-8859-1"?> i still only get what is specified in the web.xml document and not in the web-page. Any ideas?

Peter
On 26 Mar 2004, at 23:08, Marc Portier wrote:

beyaNet Consultancy wrote:

Hi,
I am trying to obtain the encoding type as specified in at the top of my site page when you view source the page. At the moment the encoding type is specified as:



I was under the impression that if i used  that it would return UTF-8, in this instance. At the moment it is returning  ISO-8859-1 which is the encoding type of the server. How do I get the encoding type as specified within my page?

which version of cocoon are you using?

pre 2.1.3 there was a possible mismatch between the encoding used in the html-generation (encoding) and the one used in the request-parameter-processing (decoding)

this should be fixed per
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/serialization/AbstractTextSerializer.java?rev=1.6&view=markup 
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/servlet/CocoonServlet.java?rev=1.20&view=markup

prior to this you can manually assure that both sides are in sync:
just make sure the encoding set-up in your  (see it's config in sitemap.xmap) is matching the setting in the web.xml (see init-param 'form-encoding' to the cocoon servlet)

HTH,
-marc=

many thanks in advance
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED]  [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Character encoding...

[Marc Portier]

beyaNet Consultancy wrote:

Hi,
I am trying to obtain the encoding type as specified in at the top of my 
site page when you view source the page. At the moment the encoding type 
is specified as:


http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>


I was under the impression that if i used 
 that it would return UTF-8, in this 
instance. At the moment it is returning  ISO-8859-1 which is the 
encoding type of the server. How do I get the encoding type as specified 
within my page?

which version of cocoon are you using?

pre 2.1.3 there was a possible mismatch between the encoding used in the 
html-generation (encoding) and the one used in the 
request-parameter-processing (decoding)

this should be fixed per
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/serialization/AbstractTextSerializer.java?rev=1.6&view=markup 

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/servlet/CocoonServlet.java?rev=1.20&view=markup

prior to this you can manually assure that both sides are in sync:
just make sure the encoding set-up in your  (see it's config 
in sitemap.xmap) is matching the setting in the web.xml (see init-param 
'form-encoding' to the cocoon servlet)

HTH,
-marc=
many thanks in advance

Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/mpo/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

Ok, I got my database going again on a different machine.  I now use 
Panther with the JVM that comes with it.
I use the driver compiled by postgresql, and have already tested the 
one from their site.  No solution.

When I use a basic XSP, with strange chars, it works.
So, it's only when I use the database connection from XSP.
I then used the transformer instead of the generator: same problem ...

Okay, so no much further.
I downloaded Tomcat 4 and 5
First I installed Tomcat 4.  It runs nicely.
I downloaded Cocoon 2.0.4 (latest from 2.0 series) with VM 1.4
I dropped the cocoon.war in the webapps.  Tomcat unpacks it.
I try to open the :8080/cocoon folder and I get this error
Failed to generate program code (this may happen if you use Xalan in 
incremental processing mode). Please check log file and/or console for 
errors.

Okay, away went version 4 of Tomcat

I unpacked Tomcat 5, started it and there it was ...
Dropped the war again in the webapps.
Tomcat unpacked it, but I could not connect to :8080/cocoon
The requested resource (/cocoon/) is not available.

Now that's strange to me  The directory is there.  I don't know why 
it's not found.
Do I need to "register" it first under Tomcat 5 ?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Character encoding...

[beyaNet Consultancy]

Hi,
I am trying to obtain the encoding type as specified in at the top of 
my site page when you view source the page. At the moment the encoding 
type is specified as:


http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd";>


I was under the impression that if i used 
 that it would return UTF-8, in 
this instance. At the moment it is returning  ISO-8859-1 which is the 
encoding type of the server. How do I get the encoding type as 
specified within my page?

many thanks in advance

Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Encoding problem

[Jean-Luc Mathieu]

After a lot of tries, it seems that Cocoon authentication is not involved, nor
DOM model : it is the fact of transforming such characters in a xsl:comment
section that produce this kind of error.

If I remove the xsl:comment tags, my string appears without any error. Is
anybody knows the problem ?

> -Message d'origine-
> De : JLM [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 17 mars 2004 16:50
> À : [EMAIL PROTECTED]
> Objet : Encoding problem
> 
> Hello!
> 
> I have written a custom authenticator object that sends back to the user an
> error message if login fails. So I build a DOM structure and I pass it to the
> AuthenticationResult object, returning it from authenticate method. Because I
> use DOM, all error messages are in UTF8.
> I get session context from an XSP page (only interesting code is given here)
> :
> 
> 
> 
>   
>   …
>path="/data/throw"/>
>   
> 
> 
> … and I use session transformer on the result. After that, I transform
> resulting XML flow to HTML code using this kind of stylesheet:
> 
> 
> 
>xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
>   xmlns:i18n="http://apache.org/cocoon/i18n/2.1";>
> …
> 
>   …
>   login_internal-error : select="user-msg"/>
>   …
> 
> …
> 
> My application works fine until I put some extended characters (like é or ê)
> in
> my message in the DOM structure. I get back from Cocoon the following error:
> 
>Attempt to output character of integral value 234 that is not
> represented in specified output encoding of .
> 
> It seems that session transformer put in the XML flow some UTF-8 instead of
> converting them in ISO-8859-1. Is it a way to solve this problem?
> 
> Thanks!
> Jean-Luc
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Encoding problem

[JLM]

Hello!

I have written a custom authenticator object that sends back to the user an
error message if login fails. So I build a DOM structure and I pass it to the
AuthenticationResult object, returning it from authenticate method. Because I
use DOM, all error messages are in UTF8.
I get session context from an XSP page (only interesting code is given here) :




…




… and I use session transformer on the result. After that, I transform
resulting XML flow to HTML code using this kind of stylesheet:



http://www.w3.org/1999/XSL/Transform"; 
xmlns:i18n="http://apache.org/cocoon/i18n/2.1";>
…

…
login_internal-error :
…

…

My application works fine until I put some extended characters (like é or ê) in
my message in the DOM structure. I get back from Cocoon the following error:

   Attempt to output character of integral value 234 that is not
represented in specified output encoding of .

It seems that session transformer put in the XML flow some UTF-8 instead of
converting them in ISO-8859-1. Is it a way to solve this problem?

Thanks!
Jean-Luc



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

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 have no idea: I use the Apple Software Update mechanism... 
there was no suggestion for X;

alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

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 ?


-Original Message-
From: Alexander Schatten [mailto:[EMAIL PROTECTED]
Sent: dinsdag 9 maart 2004 12:59
To: [EMAIL PROTECTED]
Subject: Re: [OS-X] Serious Encoding Problems (VM Bug?)


Yves Vindevogel wrote:

>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 still there)
>with no problems.  Brand new Linux Slackware 9.1, with problem.
>
>
as I mentioned already: with the Old VM on OS X it worked! it seems to
be an issue of  the JVM upgrade!



alex


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

Yves Vindevogel wrote:

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 still there)
with no problems.  Brand new Linux Slackware 9.1, with problem.
 

as I mentioned already: with the Old VM on OS X it worked! it seems to 
be an issue of  the JVM upgrade!



alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

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 still there)
with no problems.  Brand new Linux Slackware 9.1, with problem.

My characters are coming back nicely on OSX, and even in Access when I use
postgresODBC to the database.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Bertrand Delacretaz]

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 öäüÄÖÜ are not transferred correctly from the database;
This might have been suggested already, but did you try from a small 
java program talking JDBC directly to your database? If it's not 
working at that level it will never work.

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

Yves Vindevogel wrote:

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:postgresql://myserver/mydatabase?charSet=iso-8859-1

 

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 system variable
-- JAVA_OPTIONS on startup
-- this encoding in the driver
still the öäüÄÖÜ are not transferred correctly from the database;

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).

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

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:

>
>  jdbc:postgresql://myserver/mydatabase?charSet=iso-8859-1
>
>  
>

hm, thank you; did not know this one; looks like a specific postgresql 
feature, no? will this work on mysql too?


thanks


alex


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

Yves Vindevogel wrote:


 jdbc:postgresql://myserver/mydatabase?charSet=iso-8859-1

 

hm, thank you; did not know this one; looks like a specific postgresql 
feature, no? will this work on mysql too?

thanks

alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

What JDK are you using, anyway ?

I need to track this down, so I'm gonna do this
1) Copy my Tomcat directory (on Osx) to my Slackware server.
This check allows me to see if it's only a problem in cocoon 2.1 since my
Tomcat uses 2.0
2) Then I will copy my postgresql-jdbc jar from 2.0 to 2.1.  Could also be a
problem in it.  I'm not sure whether I need to specify options, but the .jar
was build by me without options in Postgresql
3) Then I will downgrade my JDK to 1.4.x where x < 2.

I'm pretty sure it's not Postgresql, because both Cocoons are connecting to
the same database on the same 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 ??) 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 be VM related (I'm using 1.4.2_03 *i think*) or the
>JDBC driver.
>I do not have the problem on OSX, but I connect to the database using the
>mydatabase?charSet=iso-8859-1 dburl.
>
>
>
well, thanks for the comments, so it is probably not me beeing too
stupid, because I tried all tips, but no one worked so far: and to
mention it again: it already worked with the JDK version before the
update; so meanwhile I really assume, that this is a JDK bug!

btw.: what do you mean with

mydatabase?charSet=iso-8859-1 dburl.

?


thanks


alex



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

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:postgresql://myserver/mydatabase?charSet=iso-8859-1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

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 be VM related (I'm using 1.4.2_03 *i think*) or the
JDBC driver.
I do not have the problem on OSX, but I connect to the database using the
mydatabase?charSet=iso-8859-1 dburl.
 

well, thanks for the comments, so it is probably not me beeing too 
stupid, because I tried all tips, but no one worked so far: and to 
mention it again: it already worked with the JDK version before the 
update; so meanwhile I really assume, that this is a JDK bug!

btw.: what do you mean with

mydatabase?charSet=iso-8859-1 dburl.

?

thanks

alex



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [OS-X] Serious Encoding Problems (VM Bug?)

[Yves Vindevogel]

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 be VM related (I'm using 1.4.2_03 *i think*) or the
JDBC driver.
I do not have the problem on OSX, but I connect to the database using the
mydatabase?charSet=iso-8859-1 dburl.


-Original Message-
From: Stephen Winnall [mailto:[EMAIL PROTECTED]
Sent: zaterdag 6 maart 2004 23:15
To: [EMAIL PROTECTED]
Subject: Re: [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 a Microsoft Excel source using a Java
program and POI. I converted the strings from POI to whatever Java uses
internally using the following function:

   private static String toJava( String cp1252 ) {
 try {
   return new String( cp1252.getBytes(), "Cp1252" );
 } catch( Exception e ) {
   e.printStackTrace( System.err );
 }
 return cp1252; //dummy value to keep the compiler happy: we never
get here
   }

The Postgresql JDBC put the stuff into the database in UTF-8 format.
Perhaps
the MySQL JDBC does something similar.

The Mac seems to prefer something called Mac OS Roman to ISO 8859-1. I
have
decided to use UTF-8 as "lingua franca" and hope that Deli or something
similar will allow me to generate whatever the client actually wants.

I didn't have to fiddle with the JVM parameters.

Perhaps this helps you...

Cheers
Steve


On 5 Mar 2004, at 17:42, Alexander Schatten wrote:

> 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 are iso-8859-1
>
>
> It still does not work to send and retrieve german umlauts from Cocoon
> to mysql... (mentioned again: the same cocoon webapp works without
> problems on an english RedHat 9 server)
>
>
> now I really have no more ideas...
>
>
> please, any other comments?
>
>
> thanks
>
>
> Alex
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Stephen Winnall]

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 a Microsoft Excel source using a Java
program and POI. I converted the strings from POI to whatever Java uses
internally using the following function:
  private static String toJava( String cp1252 ) {
try {
  return new String( cp1252.getBytes(), "Cp1252" );
} catch( Exception e ) {
  e.printStackTrace( System.err );
}
return cp1252; //dummy value to keep the compiler happy: we never 
get here
  }

The Postgresql JDBC put the stuff into the database in UTF-8 format. 
Perhaps
the MySQL JDBC does something similar.

The Mac seems to prefer something called Mac OS Roman to ISO 8859-1. I 
have
decided to use UTF-8 as "lingua franca" and hope that Deli or something
similar will allow me to generate whatever the client actually wants.

I didn't have to fiddle with the JVM parameters.

Perhaps this helps you...

Cheers
Steve
On 5 Mar 2004, at 17:42, Alexander Schatten wrote:

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 are iso-8859-1
It still does not work to send and retrieve german umlauts from Cocoon 
to mysql... (mentioned again: the same cocoon webapp works without 
problems on an english RedHat 9 server)

now I really have no more ideas...

please, any other comments?

thanks

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[teru kohama]

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 Bug?)


> are you sure these java options are actually used when your servlet
> container starts up? Do an echo $JAVA_OPTIONS just before the statement
> you think gets exec'ed to start the container.
>
> Alexander Schatten wrote:
>
> > 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 are iso-8859-1
> >
> >
> > It still does not work to send and retrieve german umlauts from Cocoon
> > to mysql... (mentioned again: the same cocoon webapp works without
> > problems on an english RedHat 9 server)
> >
> >
> > now I really have no more ideas...
> >
> >
> > please, any other comments?
> >
> >
> > thanks
> >
> >
> > Alex
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

XInclude and UTF-16 encoding

[Stefan Geelen]

Hi,
 
I build a webpage 
with  default charset=ISO-8859-1" 
encoding.
 
I need to include another .xml file built in utf-16 
encoding:
 
      
  
Example currently 
unavailable    
  

 
The result is :
...
 ÿþ<�?�x�m�l� �v�e�r�s�i�o�n�=�"�1�.�0�"�  �e�n�c�o�d�i�n�g�=�"�U�T�F�-�1�6�"�?�>�
� 
�<�m�l�:�d�o�c�u�m�e�n�t�s� �x�m�l�n�s�:�m�l�=�"�h�t�t�p�:�/�/&#
...
 
Appareantly the file is not 
recognized as UTF-16. 
 
Note: UTF-8 seems to 
work.
 
Stefan

Re: Change encoding to ISO-8859-1

[Lionel Crine]

This error means that the document is written in ASCII mode with some 
characters which are not contain in the ASCII table of UTF-8.

Which means :
if you write "" in a new document with ultraedit and you save it as is.
Cocoon will load the document and serialize it with this error.
BUT :
Before 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



At 20:34 23/02/2004 +, you 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:
   
   pool-grow="4" pool-max="32" pool-min="4"
   src="org.apache.cocoon.serialization.HTMLSerializer">
ISO-8859-1
true
   

   
ISO-8859-1
   
After that I keep getting the same error:
"org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 
of 3-byte UTF-8 sequence"

Thanks in advance,
Carlos Dias
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Jorg Heymans]

are you sure these java options are actually used when your servlet 
container starts up? Do an echo $JAVA_OPTIONS just before the statement 
you think gets exec'ed to start the container.

Alexander Schatten wrote:

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 are iso-8859-1
It still does not work to send and retrieve german umlauts from Cocoon 
to mysql... (mentioned again: the same cocoon webapp works without 
problems on an english RedHat 9 server)

now I really have no more ideas...

please, any other comments?

thanks

Alex


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

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 are iso-8859-1
It still does not work to send and retrieve german umlauts from Cocoon 
to mysql... (mentioned again: the same cocoon webapp works without 
problems on an english RedHat 9 server)

now I really have no more ideas...

please, any other comments?

thanks

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

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=iso-8859-1"


thank you, but how do I set this one?

I just tried to edit the cocoon.sh file and made the following entry on top:

JAVA_OPTIONS='-Dfile.encoding=iso-8859-1'

but this does not have any effect either.

thank you!

Alex

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OS-X] Serious Encoding Problems (VM Bug?)

[Bertrand Delacretaz]

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[OS-X] Serious Encoding Problems (VM Bug?)

[Alexander Schatten]

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 and suddenly the 
german umlauts did not work proberly (database, ESQL, mysql); I tried to 
fix this for hours, then gave up; copied the app to linux (same mysql, 
same cocoon version) and there it works fine without problems and 
without any changes.

The only thing I remember I had changed on the Powerbook was a JDK 
update some weeks ago.

Has anyone an idea, how I could fix this encoding problem on OS X ?

thank you very much.

Alex

p.s.: I set LANG to de..., I set the two init-params in web.xml to 
iso-88591-1; I see no further "tuning" possibilities?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

encoding of result from database

[Vlad Ali]

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Carlos Dias]

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 Heinicke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 23, 2004 8:51 PM
Subject: Re: Change encoding to ISO-8859-1


> Another good hint might be to use a browser like IE or Mozilla to view
> the XML file because they tell you if something is wrong with the file
> and no editor/application/cocoon is involved.
>
> Joerg
>
> On 23.02.2004 21:50, Joerg Heinicke wrote:
>
> > 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 the specific encoding. jEdit is a good suggestion by
> > Bert, btw. You can get it at jedit.org.
> >
> > Joerg
> >
> >> - Original Message -
> >> From: "Joerg Heinicke" <[EMAIL PROTECTED]>
> >>
> >> org.xml.sax.SAXException: Original Exception IOException : Invalid
> >> byte 2 of
> >> 3-byte UTF-8 sequence"
> >>
> >>> I think the problem is not the encoding setting of Cocoon, but in the
> >>> file you are accessing in this pipeline. The encoding *specified* in
> >>> this file (or default UTF-8) does not seem to match the encoding *of*
> >>> the file.
> >>>
> >>> Joerg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Joerg Heinicke]

Another good hint might be to use a browser like IE or Mozilla to view 
the XML file because they tell you if something is wrong with the file 
and no editor/application/cocoon is involved.

Joerg

On 23.02.2004 21:50, Joerg Heinicke wrote:

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 the specific encoding. jEdit is a good suggestion by 
Bert, btw. You can get it at jedit.org.

Joerg

- Original Message -
From: "Joerg Heinicke" <[EMAIL PROTECTED]>
org.xml.sax.SAXException: Original Exception IOException : Invalid 
byte 2 of
3-byte UTF-8 sequence"

I think the problem is not the encoding setting of Cocoon, but in the
file you are accessing in this pipeline. The encoding *specified* in
this file (or default UTF-8) does not seem to match the encoding *of*
the file.
Joerg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Joerg Heinicke]

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 the specific encoding. jEdit is a good suggestion by 
Bert, btw. You can get it at jedit.org.

Joerg

- Original Message -
From: "Joerg Heinicke" <[EMAIL PROTECTED]>
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence"
I think the problem is not the encoding setting of Cocoon, but in the
file you are accessing in this pipeline. The encoding *specified* in
this file (or default UTF-8) does not seem to match the encoding *of*
the file.
Joerg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Carlos Dias]

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:39 PM
Subject: Re: Change encoding to ISO-8859-1


> 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:
> > >pool-grow="4" pool-max="32" pool-min="4"
> >src="org.apache.cocoon.serialization.HTMLSerializer">
> > ISO-8859-1
> > true
> >
> >
> > >src="org.apache.cocoon.serialization.XMLSerializer"
> >mime-type="text/xml" pool-max="32" pool-min="16" pool-grow="4">
> > ISO-8859-1
> >
> >
> > After that I keep getting the same error:
> > "org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence"
>
> I think the problem is not the encoding setting of Cocoon, but in the
> file you are accessing in this pipeline. The encoding *specified* in
> this file (or default UTF-8) does not seem to match the encoding *of*
> the file.
>
> Joerg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Bert Van Kets]

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: "Joerg Heinicke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 23, 2004 9:39 PM
Subject: Re: Change encoding to ISO-8859-1


> 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:
> > >pool-grow="4" pool-max="32" pool-min="4"
> >src="org.apache.cocoon.serialization.HTMLSerializer">
> > ISO-8859-1
> > true
> >
> >
> > >src="org.apache.cocoon.serialization.XMLSerializer"
> >mime-type="text/xml" pool-max="32" pool-min="16" pool-grow="4">
> > ISO-8859-1
> >
> >
> > After that I keep getting the same error:
> > "org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence"
>
> I think the problem is not the encoding setting of Cocoon, but in the
> file you are accessing in this pipeline. The encoding *specified* in
> this file (or default UTF-8) does not seem to match the encoding *of*
> the file.
>
> Joerg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Change encoding to ISO-8859-1

[Joerg Heinicke]

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:
   
   pool-grow="4" pool-max="32" pool-min="4" 
   src="org.apache.cocoon.serialization.HTMLSerializer">
ISO-8859-1
true
   
   
   
   mime-type="text/xml" pool-max="32" pool-min="16" pool-grow="4">
ISO-8859-1
   

After that I keep getting the same error:
"org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of 3-byte UTF-8 
sequence"
I think the problem is not the encoding setting of Cocoon, but in the 
file you are accessing in this pipeline. The encoding *specified* in 
this file (or default UTF-8) does not seem to match the encoding *of* 
the file.

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Change encoding to ISO-8859-1

[Carlos Dias]

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:
  pool-grow="4" 
pool-max="32" pool-min="4" 
   src="">ISO-8859-1truesrc=""   mime-type="text/xml" 
pool-max="32" pool-min="16" 
pool-grow="4">ISO-8859-1   
 
After that I keep getting the same 
error:
"org.apache.cocoon.ProcessingException: Failed to 
execute pipeline.: org.xml.sax.SAXException: Original Exception IOException : 
Invalid byte 2 of 3-byte UTF-8 sequence"
 
Thanks in advance,
Carlos Dias

Re: [once again] best way to set http header encoding

[Lionel Crine]

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 differents exit, then you should define two serializers but 
it's not a problem.

Lionel

At 23:20 16/02/2004 +0100, you 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. 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 if the http-header-encoding is set.

so i need to set the http-header-encoding with cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Christopher Painter-Wakefield]

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.

-Christopher



|-+>
| |   Jan Uyttenhove   |
| |   <[EMAIL PROTECTED]|
| |   ume.com> |
| ||
| |   02/17/2004 12:39 |
| |   PM   |
| |   Please respond to|
| |   users|
| ||
|-+>
  
>--|
  |
  |
  |   To:   [EMAIL PROTECTED]  
|
  |   cc:  
  |
  |   Subject:  Re: [once again] best way to set http header encoding  
  |
  
>--|




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 to the http
header also, and possibly even make it the default behaviour (via a
config option in web.xml?)

Jan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Jan Uyttenhove]

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 to the http 
header also, and possibly even make it the default behaviour (via a 
config option in web.xml?)

Jan

Jan Uyttenhove  [EMAIL PROTECTED]   
Java Software Engineer
> Xume < - http://www.xume.com
Christopher Painter-Wakefield wrote:



We also had a problem with Tomcat  4.1.29 and content-type.  We backed up
to 4.1.27, and are having no problems.  Also, we've just started testing
with Tomcat 5, and it looks like we don't have the problem with it.
-Christopher



|-+>
| |   Jan Uyttenhove   |
| |   <[EMAIL PROTECTED]|
| |   ume.com> |
| ||
| |   02/17/2004 05:00 |
| |   AM   |
| |   Please respond to|
| |   users|
| ||
|-+>
  
>--|
  |
  |
  |   To:   [EMAIL PROTECTED]  
|
  |   cc:  
  |
  |   Subject:  Re: [once again] best way to set http 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 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 in the header was added not 'that' long ago[1]. I'm
using Tomcat 4.1.29 now, and it *does* set a default encoding to
ISO-8859-1. So in a way you're lucky you're still using Tomcat 4.1.12,
because with 4.1.29, the apache directive has no effect when connecting
to Tomcat :-) This is why I'm looking for a good solution in Cocoon...
We see and will see this issue more and more, as Bruno mentioned, but
not only because of the browser implementation. In my opinion this is
caused by the changes in this default encoding behaviour when using
Tomcat. The very latest changes should change the behaviour again, so
the upcoming Tomcat 4.1.30 should behave different again. I don't know
what exactly the difference will be, this is wat the changelog for
4.1.30 says:
" Restore the ability to explicitly set the charset to iso-latin-1. Now,
you won't get the charset unless you ask for it (so no more
Content-Type: image/gif; charset=iso-8859-1).  However, if you call
response.setCharacterEncoding("iso-9959-1"), you now get it in the
response."
So conclusion:
Somewhere between Tomcat 4.1.12 en 4.1.27 the default encoding behaviour
has changed (my guess is 4.1.17), and there's currently no way in Cocoon
to set the http header encoding so it matches the encoding of the
serializer (and meta tag). Anyone upgrading an old Tomcat will have this
problem, unless using ISO-8859-1. The upcoming Tomcat 4.1.30 should
change the behaviour again, but I'm not sure in what way.
Jan

[1]
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







smime.p7s
Description: S/MIME Cryptographic Signature

Re: [once again] best way to set http header encoding

[Christopher Painter-Wakefield]

We also had a problem with Tomcat  4.1.29 and content-type.  We backed up
to 4.1.27, and are having no problems.  Also, we've just started testing
with Tomcat 5, and it looks like we don't have the problem with it.

-Christopher



|-+>
| |   Jan Uyttenhove   |
| |   <[EMAIL PROTECTED]|
| |   ume.com> |
| ||
| |   02/17/2004 05:00 |
| |   AM   |
| |   Please respond to|
| |   users|
| ||
|-+>
  
>--|
  |
  |
  |   To:   [EMAIL PROTECTED]  
|
  |   cc:  
  |
  |   Subject:  Re: [once again] best way to set http 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 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 in the header was added not 'that' long ago[1]. I'm
using Tomcat 4.1.29 now, and it *does* set a default encoding to
ISO-8859-1. So in a way you're lucky you're still using Tomcat 4.1.12,
because with 4.1.29, the apache directive has no effect when connecting
to Tomcat :-) This is why I'm looking for a good solution in Cocoon...

We see and will see this issue more and more, as Bruno mentioned, but
not only because of the browser implementation. In my opinion this is
caused by the changes in this default encoding behaviour when using
Tomcat. The very latest changes should change the behaviour again, so
the upcoming Tomcat 4.1.30 should behave different again. I don't know
what exactly the difference will be, this is wat the changelog for
4.1.30 says:
" Restore the ability to explicitly set the charset to iso-latin-1. Now,
you won't get the charset unless you ask for it (so no more
Content-Type: image/gif; charset=iso-8859-1).  However, if you call
response.setCharacterEncoding("iso-9959-1"), you now get it in the
response."

So conclusion:
Somewhere between Tomcat 4.1.12 en 4.1.27 the default encoding behaviour
has changed (my guess is 4.1.17), and there's currently no way in Cocoon
to set the http header encoding so it matches the encoding of the
serializer (and meta tag). Anyone upgrading an old Tomcat will have this
problem, unless using ISO-8859-1. The upcoming Tomcat 4.1.30 should
change the behaviour again, but I'm not sure in what way.


Jan

[1]
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Jan Uyttenhove]

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 in the header was added not 'that' long ago[1]. I'm 
using Tomcat 4.1.29 now, and it *does* set a default encoding to 
ISO-8859-1. So in a way you're lucky you're still using Tomcat 4.1.12, 
because with 4.1.29, the apache directive has no effect when connecting 
to Tomcat :-) This is why I'm looking for a good solution in Cocoon...

We see and will see this issue more and more, as Bruno mentioned, but 
not only because of the browser implementation. In my opinion this is 
caused by the changes in this default encoding behaviour when using 
Tomcat. The very latest changes should change the behaviour again, so 
the upcoming Tomcat 4.1.30 should behave different again. I don't know 
what exactly the difference will be, this is wat the changelog for 
4.1.30 says:
" Restore the ability to explicitly set the charset to iso-latin-1. Now, 
you won't get the charset unless you ask for it (so no more 
Content-Type: image/gif; charset=iso-8859-1).  However, if you call 
response.setCharacterEncoding("iso-9959-1"), you now get it in the 
response."

So conclusion:
Somewhere between Tomcat 4.1.12 en 4.1.27 the default encoding behaviour 
has changed (my guess is 4.1.17), and there's currently no way in Cocoon 
to set the http header encoding so it matches the encoding of the 
serializer (and meta tag). Anyone upgrading an old Tomcat will have this 
problem, unless using ISO-8859-1. The upcoming Tomcat 4.1.30 should 
change the behaviour again, but I'm not sure in what way.

Jan

[1] 
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java



Stefan Burkard wrote:
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 the meta-tag if the http-header-encoding is set.


Do you mean Apache or Tomcat?
Tomcat sets the http header encoding to the default ISO-8859-1, if 
none specified. You can also set the addDefaultCharset in Apache, but 
that won't make any difference I think, as there's already an encoding 
specified by Tomcat.


---> i mean apache.
if i connect to tomcat directly theres no encoding set in the header, 
just the mime-type (i use tomcat 4.1.12 and ieHTTPHeaders for inspecting 
the header-data).
therefore my page with russian characters displays correct, because the 
browser uses the meta-tag in the html.

BUT if i connect via apache/jk2, apache uses the directive you mention 
to set a default encoding - and the encoding is "destroyed". if tomcat 
would set the header-encoding - you're absolutely right - apache would 
do noting.


so i need to set the http-header-encoding with cocoon and ask you 
all, whats the best way to do this. are there any actions, 
logicsheets or something else?


ATM, Cocoon set the meta content-type tag with the mime-type and the 
encoding of the serializer. Furthermore, response.setContentType *is* 
called, which is one of the ways to set the http encoding header. But 
it is called with argument mime-type only, e.g. 
response.setContentType("text/html"), and we should be able to do 
response.setContentType("text/html; charset=utf-8").
Actually, you can, if you change the mime-type of the serializer in 
the sitemap from e.g. 'text/html' to 'text/html; charset=utf-8', 
you'll see that the http header encoding has changed to utf-8. Just an 
illustration of the problem, not a very nice solution :-)


at the moment i'm happy by setting the apache-directive to utf-8 for my 
virtual-host, but this is another good way for a temporary solution :-)

We should be able to set the full content-type (with charset) in 
HttpEnvironment or in AbstractProcessingPipeline. I guess that 
involves changing at least the setSerializer(...) in 
AbstractProcessingPipeline and passing the encoding.


i will try to open a bugzilla issue for this like bruno dumon wrote, but 
first i need to search on the cocoon-page where i can do this :-)

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Jan Uyttenhove  [EMAIL PROTECTED]   
> Xume < - http://www.xume.com


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [once again] best way to set http header encoding

[Stefan Burkard]

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 the meta-tag if the http-header-encoding is set.


Do you mean Apache or Tomcat?
Tomcat sets the http header encoding to the default ISO-8859-1, if none 
specified. You can also set the addDefaultCharset in Apache, but that 
won't make any difference I think, as there's already an encoding 
specified by Tomcat.
---> i mean apache.
if i connect to tomcat directly theres no encoding set in the header, 
just the mime-type (i use tomcat 4.1.12 and ieHTTPHeaders for inspecting 
the header-data).
therefore my page with russian characters displays correct, because the 
browser uses the meta-tag in the html.

BUT if i connect via apache/jk2, apache uses the directive you mention 
to set a default encoding - and the encoding is "destroyed". if tomcat 
would set the header-encoding - you're absolutely right - apache would 
do noting.


so i need to set the http-header-encoding with cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?


ATM, Cocoon set the meta content-type tag with the mime-type and the 
encoding of the serializer. Furthermore, response.setContentType *is* 
called, which is one of the ways to set the http encoding header. But it 
is called with argument mime-type only, e.g. 
response.setContentType("text/html"), and we should be able to do 
response.setContentType("text/html; charset=utf-8").
Actually, you can, if you change the mime-type of the serializer in the 
sitemap from e.g. 'text/html' to 'text/html; charset=utf-8', you'll see 
that the http header encoding has changed to utf-8. Just an illustration 
of the problem, not a very nice solution :-)
at the moment i'm happy by setting the apache-directive to utf-8 for my 
virtual-host, but this is another good way for a temporary solution :-)

We should be able to set the full content-type (with charset) in 
HttpEnvironment or in AbstractProcessingPipeline. I guess that involves 
changing at least the setSerializer(...) in AbstractProcessingPipeline 
and passing the encoding.
i will try to open a bugzilla issue for this like bruno dumon wrote, but 
first i need to search on the cocoon-page where i can do this :-)

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Jan Uyttenhove]

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 if the http-header-encoding is set.
Do you mean Apache or Tomcat?
Tomcat sets the http header encoding to the default ISO-8859-1, if none 
specified. You can also set the addDefaultCharset in Apache, but that 
won't make any difference I think, as there's already an encoding 
specified by Tomcat.

so i need to set the http-header-encoding with cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?
ATM, Cocoon set the meta content-type tag with the mime-type and the 
encoding of the serializer. Furthermore, response.setContentType *is* 
called, which is one of the ways to set the http encoding header. But it 
is called with argument mime-type only, e.g. 
response.setContentType("text/html"), and we should be able to do 
response.setContentType("text/html; charset=utf-8").
Actually, you can, if you change the mime-type of the serializer in the 
sitemap from e.g. 'text/html' to 'text/html; charset=utf-8', you'll see 
that the http header encoding has changed to utf-8. Just an illustration 
of the problem, not a very nice solution :-)

We should be able to set the full content-type (with charset) in 
HttpEnvironment or in AbstractProcessingPipeline. I guess that involves 
changing at least the setSerializer(...) in AbstractProcessingPipeline 
and passing the encoding.

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Jan Uyttenhove  [EMAIL PROTECTED]   
> Xume < - http://www.xume.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Bruno Dumon]

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
this.

>  it doesn't do this in the http-header.

But indeed it's a good question why our serializer doesn't put in in the
http header also.

I can't think of any reason not to do it. You might want to try to patch
the serializer to do this, and in any case, open a bugzilla issue for
this.

I remember reading something about how it's only the latest IE's which
will actually take the header in preference over what's in the HTML
page, so that's maybe why more people haven't complained about this yet.

> 
> 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 if the http-header-encoding is set.
> 
> so i need to set the http-header-encoding with cocoon and ask you all, 
> whats the best way to do this. are there any actions, logicsheets or 
> something else?


-- 
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EMAIL PROTECTED]  [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [once again] best way to set http header encoding

[Christopher Painter-Wakefield]

there may be no "best way".  You can probably fix this issue at several different levels; Cocoon; Tomcat; Apache (if using it), etc.  In Cocoon, the easiest would probably be an Action.  It can be dirt simple.  If you want to use an xsp-action, it could be something like this:

         xmlns:xsp="http://apache.org/xsp"
                xmlns:action="">"http://apache.org/cocoon/action/1.0">
        
                
                        response.setHeader("Content-Type", "text/html; charset=UTF-8");
                
        


sitemap entry (put in the pipeline for each matcher you want to set the encoding for):
         type="serverpages" src="">"path-to-action.xml">

It could work.

-Christopher







Stefan Burkard <[EMAIL PROTECTED]>
Sent by: news <[EMAIL PROTECTED]>
02/16/2004 05:20 PM
Please respond to users

        
        To:        [EMAIL PROTECTED]
        cc:        
        Subject:        [once again] best way to set http header encoding


[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 encoding of the response, because most browsers 
ignore the meta-tag if the http-header-encoding is set.

so i need to set the http-header-encoding with cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?

thanks and greetings
stefan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[once again] best way to set http header encoding

[Stefan Burkard]

[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 encoding of the response, because most browsers 
ignore the meta-tag if the http-header-encoding is set.

so i need to set the http-header-encoding with cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Testing generator encoding problem

[Stefan Burkard]

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 in
the file, because it reads with iso8859-1

greetings
stefan

zheng jianjun wrote:
> Hi ,
>  
> When testing cocoon 2.1.3 , I had the following  problem . It's OK when 
> read-in the static XML file pages/16.xml in codepage "gb2312" by 
> generator "file" , but not work by the testing generator "test", which 
> actually call Linux command "cat  /./pages/16.xml" , the html did
> generated in IE , but no 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 :
> 
> 
>   container-encoding
>   iso-8859-1
> 
>   
> 
>   form-encoding
>   iso-8859-1
> 
> 
>  
> sitemap.xmap :
>  
> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
> My static 16.xml is something like:
>  
> 
> 
> 
>
>   40.13 生产效率统计日报表(B)
>
>
>MFG
>
>
>   01/13/04 13:04:13
>
> 
> .
> 
>  
> report.xsl is something as the following:
>  
> 
>  
> ]>
>  xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
>  version="4.01"
>  doctype-public="-//W3C//DTD HTML 4.01//EN"
>  doctype-system="http://www.w3.org/TR/html4/strict.dtd";
>  encoding="gb2312"
>  indent="yes"/>
> 
> 
> WIP Reports
> .
> It's OK to input URL  http://localhost:8080/cocoon/result/16.html in IE ,
> but http://localhost:8080/cocoon/result/test.test won't work .
>  
> Thanks in advance.
> Jianjun Zheng.
> 
> 
> 
> *Do You Yahoo!?*
> 完全免费的雅虎电邮，马上注册获赠额外60兆网络存储空间 
> <http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.mail.yahoo.com>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Testing generator encoding problem

[zheng jianjun]

Hi ,
 
When testing cocoon 2.1.3 , I had the following  problem . It's OK when read-in the static XML file pages/16.xml in codepage "gb2312" by generator "file" , but not work by the testing generator "test", which actually call Linux command "cat  /./pages/16.xml" , the html did
generated in IE , but no 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 :

      container-encoding  iso-8859-1        form-encoding  iso-8859-1    

 
sitemap.xmap :
 

 
   
 
   
My static 16.xml is something like:
 
         40.13 生产效率统计日报表(B)         MFG        01/13/04 13:04:13       .

 
report.xsl is something as the following:
 
 ]>http://www.w3.org/1999/XSL/Transform">
    version="4.01"  doctype-public="-//W3C//DTD HTML 4.01//EN"  doctype-system="http://www.w3.org/TR/html4/strict.dtd" encoding="gb2312"  indent="yes"/>
        WIP Reports.
It's OK to input URL  http://localhost:8080/cocoon/result/16.html in IE ,
but http://localhost:8080/cocoon/result/test.test won't work .
 
Thanks in advance.
Jianjun Zheng.Do You Yahoo!?
完全免费的雅虎电邮，马上注册获赠额外60兆网络存储空间

re:How can I make IE display html in auto encoding utf-8?Sorry last mail use htm

[黄 海冬]

 Thank you! I belive you solve my problem,I did set apache/jk2 for lotus 
domino last month in apache 4.1.29.My workmate advised me change cocoon 
servlet source code to solve the problem but I don't think it's a good 
idea.I will try your method right now!
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-serializer) is used by the browser (ie/mozilla/safari on mac/win) 
to determine the encoding.

BUT if i connect to the site via apache/jk2, the browser is using 
iso-8859-1. this is because the http-header has no encoding set - apache 
sets then his standard-encoding of iso-8859-1.

to solve this problem quickly i set the apache-directive 
"AddDefaultCharset" in the apache-virtual-host to "UTF-8". this way 
apache adds the utf-8-encoding to the encoding-less http-headers of tomcat

the correct solution would be to tell cocoon to write the correct 
encoding in the http-header! but i have no idea how to do this - and i 
wonder that cocoon doesn't do it "out of the box"

greetings
stefan
_
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

best way to set http header encoding?

[Stefan Burkard]

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 encoding of the response, because most browsers 
ignore the meta-tag if the http-header-encoding is set.

so i need to set the http-header-encoding out of cocoon and ask you all, 
whats the best way to do this. are there any actions, logicsheets or 
something else?

thanks and greetings
stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I make IE display html in auto encoding utf-8?Sorry last mail use html

[Stefan Burkard]

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-serializer) is used by the browser (ie/mozilla/safari on mac/win) 
to determine the encoding.

BUT if i connect to the site via apache/jk2, the browser is using 
iso-8859-1. this is because the http-header has no encoding set - apache 
sets then his standard-encoding of iso-8859-1.

to solve this problem quickly i set the apache-directive 
"AddDefaultCharset" in the apache-virtual-host to "UTF-8". this way 
apache adds the utf-8-encoding to the encoding-less http-headers of tomcat

the correct solution would be to tell cocoon to write the correct 
encoding in the http-header! but i have no idea how to do this - and i 
wonder that cocoon doesn't do it "out of the box"

greetings
stefan
? ?? wrote:
Hi,all:
   I want to use Chinese chacter in the page and don't want it to be 
encoded as someting like ⌗.
So I change configurations in web.xml:
  
  container-encoding
  utf-8
  
  
  form-encoding
  utf-8
   and I also change HTMLSerializer config in root sitemap.
   
utf-8
   
Now I can see Chinese in the page,but IE still auto encode it with 
iso-8859-1,
I must change the encoding to "unicode" manully.How can I make IE auto 
select encoding in "unicode"?
the html generated list here:



Thanks in advance.

roy huang
guangzhou guangdong China.
[EMAIL PROTECTED] or [EMAIL PROTECTED]
_
??— MSN Hotmail?  http://www.hotmail.com 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: How can I make IE display html in auto encoding utf-8?

[Leszek Gawron]

>   
>   container-encoding
>   utf-8
Do NOT change this parameter - leave the default value. Only form-encoding
should be set to utf-8

-- 
Leszek Gawron


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I make IE display html in auto encoding utf-8?

[Eduard Drenth]

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:
> > I want to use Chinese chacter in the page and don't want it to be encoded as 
> > someting like ⌗.
> > So I change configurations in web.xml:
> >
> >container-encoding
> >utf-8
> >
> >
> >form-encoding
> >utf-8
> >
> > and I also change HTMLSerializer config in root sitemap.
> >  > name="html" pool-grow="4" pool-max="32" pool-min="4"
> > src="org.apache.cocoon.serialization.HTMLSerializer"> 
> >     utf-8
> > 
> > Now I can see Chinese in the page,but IE still auto encode it with iso-8859-1,
> > I must change the encoding to "unicode" manully.How can I make IE auto select
> > encoding in "unicode"?

For a version of mozilla and as far as I can remember also for IE adding
the meta-tag to the HTML isn't enough. I posted a not on this in wiki a
few months ago. The solution for me was:

response.setHeader("Content-Type", "text/html; charset=UTF-8");

Hope this helps!

Eduard

> > the html generated list here:
> > 
> > 
> > 
> > Thanks in advance.
> >  
> > roy huang
> > guangzhou guangdong China.
> > [EMAIL PROTECTED] or [EMAIL PROTECTED]  
> > 
> > __
> >  MSN Messenger ÎÎÎÂÏÎÎÎÏÎÎÂÏÎÎÂÂÎÏ 
> > - To 
> > unsubscribe, e-mail:
> > [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Eduard Drenth <[EMAIL PROTECTED]>
home sweet home


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I make IE display html in auto encoding utf-8?Sorry last mail use html

[Jaroslav Kuruc]

Make sure your servlet container doesn't add charset=ISO-8859-1 in HTTP
header. Charset in meta tag only matters if no (or the same) charset is
in HTTP header.

黄 海冬 wrote:

> Hi,all:
>I want to use Chinese chacter in the page and don't want it to be 
> encoded as someting like ⌗.
> So I change configurations in web.xml:
>   
>   container-encoding
>   utf-8
>   
>   
>   form-encoding
>   utf-8
>and I also change HTMLSerializer config in root sitemap.
> mime-type="text/html" name="html" pool-grow="4" pool-max="32" 
> pool-min="4" src="org.apache.cocoon.serialization.HTMLSerializer">
> utf-8
>
> Now I can see Chinese in the page,but IE still auto encode it with 
> iso-8859-1,
> I must change the encoding to "unicode" manully.How can I make IE auto 
> select encoding in "unicode"?
> the html generated list here:
> 
> 
> 
> Thanks in advance.
> 
> roy huang
> guangzhou guangdong China.
> [EMAIL PROTECTED] or [EMAIL PROTECTED]
> 
> _
> 享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Jaroslav Kuruc
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How can I make IE display html in auto encoding utf-8?Sorry last mail use html

[黄 海冬]

Hi,all:
   I want to use Chinese chacter in the page and don't want it to be 
encoded as someting like ⌗.
So I change configurations in web.xml:
  
  container-encoding
  utf-8
  
  
  form-encoding
  utf-8
   
and I also change HTMLSerializer config in root sitemap.

   utf-8
   
Now I can see Chinese in the page,but IE still auto encode it with 
iso-8859-1,
I must change the encoding to "unicode" manully.How can I make IE auto 
select 
encoding in "unicode"?
the html generated list here:



Thanks in advance.

roy huang
guangzhou guangdong China.
[EMAIL PROTECTED] or [EMAIL PROTECTED]
_
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How can I make IE display html in auto encoding utf-8?

[gounis]

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 it to be encoded as 
> someting like ⌗.
> So I change configurations in web.xml:
>    
>container-encoding
>    utf-8
>
>
>form-encoding
>utf-8
>
> and I also change HTMLSerializer config in root sitemap.
>  name="html" pool-grow="4" pool-max="32" pool-min="4"
> src="org.apache.cocoon.serialization.HTMLSerializer"> 
> utf-8
> 
> Now I can see Chinese in the page,but IE still auto encode it with iso-8859-1,
> I must change the encoding to "unicode" manully.How can I make IE auto select
> encoding in "unicode"?
> the html generated list here:
> 
> 
> 
> Thanks in advance.
>  
> roy huang
> guangzhou guangdong China.
> [EMAIL PROTECTED] or [EMAIL PROTECTED]  
> 
> __
> ΚΉΣΓ MSN Messenger ΣλΑ?»ϊ΅ΔΕσΣΡ½ψΠΠ½»Αχ 
> - To 
> unsubscribe, e-mail:
> [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How can I make IE display html in auto encoding utf-8?

[黄 海冬]

Hi,all:    I want to use Chinese chacter in the page and don't want it to be encoded as someting like ⌗.So I change configurations in web.xml:      container-encoding   utf-8   
      form-encoding   utf-8    and I also change HTMLSerializer config in root sitemap.     
    utf-8    
Now I can see Chinese in the page,but IE still auto encode it with iso-8859-1,I must change the encoding to "unicode" manully.How can I make IE auto select encoding in "unicode"?the html generated list here:
Thanks in advance.
 
roy huangguangzhou guangdong China.
[EMAIL PROTECTED] or [EMAIL PROTECTED]   使用  MSN Messenger  与联机的朋友进行交流 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

FW: Hugo Marcelino: Encoding links

[Hugo Marcelino]

>   Hi Users of cocoon:
> 
>   My name is Hugo Marcelino and a new problem came to me. 
>   
>   Imagine this situation:
> 
>   -You want to define a link that has a reference like: 
>   
>offcourse this is impossible  to get but
> if you encode your url you will get something like
> 
>   (1)  wich is the same. Only this one is
> encoded.
> 
>   Now my problem is that this is not happening. What i'm getting is :
> ( I  use a simple xml and apply a xsltc transfomation.)
> 
>   . wich you can see is not the same as (1).
>   
>   and as you can see the transformation was made incorrectly.
> 
>   After this  i try to use the transformer type=encodeURL, after my
> xsltc transformer, but the error was the same and the url had the
> sessionid as was written in the documents.
>   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 in Advance.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Hugo Marcelino: Encoding links

[Eduard Drenth]

On Mon, 2004-02-09 at 19:22, Hugo Marcelino wrote:
>   Hi Users of cocoon:
> 
>   My name is Hugo Marcelino and a new problem came to me. 
>   
>   Imagine this situation:
> 
>   -You want to define a link that has a reference like: 
>   
>offcourse this is impossible  to get but
> if you encode your url you will get something like
> 
>   (1)  wich is the same. Only this one is
> encoded.
> 

Dear Hugo,

First of all a quote from W3C:


Although URIs do not contain non-ASCII values (see [URI], section 2.1)
authors sometimes specify them in attribute values expecting URIs (i.e.,
defined with %URI; in the DTD). For instance, the following href value
is illegal:

http://foo.org/Håkon";>...

We recommend that user agents adopt the following convention for
handling non-ASCII characters in such cases:

 1. Represent each character in UTF-8 (see [RFC2279]) as one or more
bytes.
 2. Escape these bytes with the URI escaping mechanism (i.e., by
converting each byte to %HH, where HH is the hexadecimal
notation of the byte value).
This procedure results in a syntactically 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 a xsltc transfomation.)
> 
>   . wich you can see is not the same as (1).
>   

If you do an xslt transformation and add no  to your stylesheet, your xml will be UTF-8
encoded after transformation

Hope this helps

Eduard

>   and as you can see the transformation was made incorrectly.
> 
>   After this  i try to use the transformer type=encodeURL, after my
> xsltc transformer, but the error was the same and the url had the sessionid
> as was written in the documents.
>   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 an
> example in this mail.
> 
>   Thank you in Advance. <> 
> 
> __
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Eduard Drenth <[EMAIL PROTECTED]>
home sweet home


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Hugo Marcelino: Encoding links

[Mark Lundquist]

On Feb 9, 2004, at 10:22 AM, Hugo Marcelino wrote:

	Hi Users of cocoon:

My name is Hugo Marcelino and a new problem came to me.

Imagine this situation:
-You want to define a link that has a reference like:

 offcourse this is impossible  to get but
if you encode your url you will get something like
<..snip...>
and as you can see the transformation was made incorrectly.
	After this  i try to use the transformer type=encodeURL, after my
xsltc transformer, but the error was the same and the url had 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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Hugo Marcelino: Encoding links

[Hugo Marcelino]

Hi Users of cocoon:

My name is Hugo Marcelino and a new problem came to me. 

Imagine this situation:

-You want to define a link that has a reference like: 

 offcourse this is impossible  to get but
if you encode your url you will get something like

(1)  wich is the same. Only this one is
encoded.

Now my problem is that this is not happening. What i'm getting is :
( I  use a simple xml and apply a xsltc transfomation.)

. wich you can see is not the same as (1).

and as you can see the transformation was made incorrectly.

After this  i try to use the transformer type=encodeURL, after my
xsltc transformer, but the error was the same and the url had the sessionid
as was written in the documents.
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 an
example in this mail.

Thank you in Advance. <> 


test-iso.rar
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Encoding Params in the Sitemap

[Jorg Heymans]

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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Encoding Params in the Sitemap

[Brent L Johnson]

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...

- Brent

> -Original Message-
> From: Slappy Tang [mailto:[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.  The 
> parameter returned is still not the encoded version.
> 
> I then talked with Joakim Verona and found
> that he emailed a patch 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 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 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 gets decoded back into an
> > > actual space character.
> > 
> > Check the archives for this one - I know its been discussed several
> > times but don't remember the solution.  An input module is 
> > the likely cure.
> > 
> > Geoff
> > 
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Encoding Params in the Sitemap

[Slappy Tang]

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.  The parameter
returned is still not the encoded version.

I then talked with Joakim Verona and found
that he emailed a patch 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 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 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 gets decoded back into an
> > actual space character.
> 
> Check the archives for this one - I know its been discussed several 
> times but don't remember the solution.  An input module is 
> the likely cure.
> 
> Geoff
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Encoding Params in the Sitemap

[Brent L Johnson]

Wow that took about 15 seconds.. yes when including
"input parameters" in my search I found another
thread that's exactly what I was looking for here...

http://marc.theaimsgroup.com/?t=10667384183&r=1&w=2

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 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 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 gets decoded back into an
> > actual space character.
> 
> Check the archives for this one - I know its been discussed several 
> times but don't remember the solution.  An input module is 
> the likely cure.
> 
> Geoff
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Encoding Params in the Sitemap

[Brent L Johnson]

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

> -Original Message-
> From: Geoff Howard [mailto:[EMAIL PROTECTED] 
> 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 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 gets decoded back into an
> > actual space character.
> 
> Check the archives for this one - I know its been discussed several 
> times but don't remember the solution.  An input module is 
> the likely cure.
> 
> Geoff
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Encoding Params in the Sitemap

[Geoff Howard]

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 %20
back into the GET it gets decoded back into an
actual space character.
Check the archives for this one - I know its been discussed several 
times but don't remember the solution.  An input module is the likely cure.

Geoff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Encoding Params in the Sitemap

[Brent L Johnson]

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 gets decoded back into an
actual space character.

Thanks,

- Brent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

HTML Generator and UTF-8 encoding

[David Leangen]

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 simple example.

source file - japanese.html (UTF-8 encoded):


  
日本語のテスト
  
  
日本語
  


sitemap.xmap snippet:

   
 
 
   





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

HTML Generator and UTF-8 encoding

[David Leangen]

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 simple example.

source file - japanese.html (UTF-8 encoded):


  
日本語のテスト
  
  
日本語
  


sitemap.xmap snippet:

   
 
 
   




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re-HTML Generator and UTF-8 encoding

[$B?75o2m9T(B]

"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 using the HTML
(B> generator.
(B> 
(B> Am I doing something wrong, or is this a bug?
(B
(BI'm constructing Japanese site now by Cocoon 2.1.3. Cocoon uses JTidy for converting 
(Bthe html source file. But JTidy maybe can't process Japanese html files correctly, 
(BShift_JIS or UTF-8 and so on.
(B
(BTidy can convert the Japanese html files to XHTML files. So, I decided to convert 
(Bthe all site files to XHTML, and realized by Tidy binary. File Generator in 
(BCocoon is work fine for XHTML. And serializing is desirable xhtml rather than 
(Bhtml.
(B
(BThe following is the part of my sitemap.xmap.
(B
(B
(B  
(B  
(B  
(B  
(B
(B
(B> 
(B> PS - If this message goes through more than once, sorry about that! :-(
(B
(BSorry, I sent only to you, and re-send to ml.
(B___
(BMasayuki Nii <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>:iChat Ready
(B  Web Site  / OME :Emailer
(B  Home Page for MAC USERS :for Browser home
(B
(B
(B-
(BTo unsubscribe, e-mail: [EMAIL PROTECTED]
(BFor additional commands, e-mail: [EMAIL PROTECTED]

HTML Generator and UTF-8 encoding

[David Leangen]

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 simple example.

source file - japanese.html (UTF-8 encoded):


  
日本語のテスト
  
  
日本語
  


sitemap.xmap snippet:

   
 
 
   


PS - If this message goes through more than once, sorry about that! :-(




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: "multipart/form-data" and encoding problem !!

[Marcin Okraszewski]

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 how I have the "form-encoding" set, there are 
encoding problems. I have to send every form with "multipart/form-data" :-(

Regards,
Marcin Okraszewski
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: "multipart/form-data" and encoding problem !!

[Lionel Crine]

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 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 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-charset="UTF-8", but it didn't help.
How can I fix it? Of course I need "multipart/form-data" to post files to 
the server.
Regards,
Marcin Okraszewski


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: "multipart/form-data" and encoding problem !!

[Marcin Okraszewski]

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 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-charset="UTF-8", but it didn't help.

How can I fix it? Of course I need "multipart/form-data" to post files 
to the server.

Regards,
Marcin Okraszewski


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

"container-encoding" init param - what is it?

[Marcin Okraszewski]

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 don't know what I did and if it will influence the system in 
some other way - a part from helping with my encoding problem.

Regards,
Marcin Okraszewski
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: "multipart/form-data" and encoding problem !!

[Marcin Okraszewski]

But I don't mean the file (it is an image any way), but other text fields.

I don't use any custom generators.

Regards,
Marcin Okraszeszki
The file you're sending by the browser as ISO-8859-1 by default.

You have to get the stream, parse it as UTF-8.

Do you use a custom generator ?

At 01:55 22/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-charset="UTF-8", but it didn't help.

How can I fix it? Of course I need "multipart/form-data" to post files 
to the server.

Regards,
Marcin Okraszewski
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: "multipart/form-data" and encoding problem !!

[Lionel Crine]

The file you're sending by the browser as ISO-8859-1 by default.

You have to get the stream, parse it as UTF-8.

Do you use a custom generator ?

At 01:55 22/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-charset="UTF-8", but it didn't help.

How can I fix it? Of course I need "multipart/form-data" to post files to 
the server.

Regards,
Marcin Okraszewski
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

"multipart/form-data" and encoding problem !!

[Marcin Okraszewski]

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-charset="UTF-8", but it didn't help.

How can I fix it? Of course I need "multipart/form-data" to post files 
to the server.

Regards,
Marcin Okraszewski
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Encoding Problem (slightly OT)

[Lionel Crine]

Hi,
be carefull.
ISO-8859-1 ASCII goes from 0 to 255
UTF-8 ASCII goes from 0 to 127
For example,

A "é" is the 233 character in the ISO-8859-1 ASCII table. It will be 
encoded on one octet.
But with UTF-8 this character is not included in the ASCII table so it will 
be converted from ISO-8859-1 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 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/show_bug.cgi?id=24457

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Encoding Problem (slightly OT)

[Nicolas Toper]

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 I miss something?
>
> Is it this one: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24457
>
> Joerg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cocoon parameters encoding problem

[Marcin Okraszewski]

There is a form encoding parameter in the web.xml:


  form-encoding
  UTF-8

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 parameter working through the same file.

Here is my sitemap snippet where the generator src is a sitemap working on the 
same principle as Forrest (it does contain much more informations however: 
basically the map.xml contains the high level semantics and the sitemap 
contains the definition of pages).
	http://{body: /param_page/param_pipeline/bo_url}/map"/>
			

			
			
		
	

With the site2arbo.xsl when I do  (with 
$sousrub as a level 2 heading taken from the linkmap) , I receive Liste des 
actualités instead of Liste des 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 PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Encoding Problem (slightly OT)

[Joerg Heinicke]

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/show_bug.cgi?id=24457

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Cocoon parameters encoding problem

[Nicolas Toper]

Hi,

I'm trying to get the following parameter working through the same file.


Here is my sitemap snippet where the generator src is a sitemap working on the 
same principle as Forrest (it does contain much more informations however: 
basically the map.xml contains the high level semantics and the sitemap 
contains the definition of pages).
http://{body: /param_page/param_pipeline/bo_url}/map"/>







With the site2arbo.xsl when I do  (with 
$sousrub as a level 2 heading taken from the linkmap) , I receive Liste des 
actualités instead of Liste des 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 PROTECTED]

Encoding Problem (slightly OT)

[Nicolas Toper]

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



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with attributes encoding

[Joerg Heinicke]

On 05.12.2003 14:26, Jakub Kaniewski wrote:
I have a problem with adding attribute value   to the input tag. 
I can't insert encoded with ISO-8859-2 text into this tag attributes 
(value attribute). I always receive Xalan error (inproper integral value 
 etc.). There is no problem to insert encoded text anywhere else. My 
coocoon i properly configured for this encoding. My XSL file is


http://www.w3.org/1999/XSL/Transform";>








and XML



żółta ćma

Any sugestions?
It's a bug in the Xalan we currently use. You can either switch to XSLTC 
(until you come across other bugs there) or downgrade Xalan.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24457

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: URL encoding in sitemap?

[joakim verona]

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 urlencode transformer and the xinclude 
transformer.

- there would be a template file containing a xinclude statement built 
with jx path expressions
- the jx transformer would build a proper xinclude statement with my 
parameters substituted
- the urlencode transformer would urlencode the href
- the xinclude transformer would read and include the html from the 
remote site

This would be kind of clumsy, but ought to work. A sitemap solution 
would be preferable.

/Joakim

Tony Collen wrote:

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 automatically.


Yep, I originally thought the RawRequestParamInputModule would do 
this, but apparently, it won't.  There are threads in the archives 
about the raw-request-param module.  The solution is to write a 
metamodule that will URLEncode (or decode) a given string... this has 
been on my plate for a while, and may actually get done within the 
next couple weeks.



It seems the {} tags can contain jxpath expressions, can this be used 
to call the URLEncode funtion?


I'm not too familliar with all the inner workings of jxpath, or 
calling functions from it, so I would guess that you'd just have to 
experiment.  IMO the cleanest solution is a URLEncodingMetaModule...

/Joakim


Regards,

Tony

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: URL encoding in sitemap?

[Tony Collen]

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 automatically.
Yep, I originally thought the RawRequestParamInputModule would do this, 
but apparently, it won't.  There are threads in the archives about the 
raw-request-param module.  The solution is to write a metamodule that 
will URLEncode (or decode) a given string... this has been on my plate 
for a while, and may actually get done within the next couple weeks.



It seems the {} tags can contain jxpath expressions, can this be used to 
call the URLEncode funtion?
I'm not too familliar with all the inner workings of jxpath, or calling 
functions from it, so I would guess that you'd just have to experiment. 
 IMO the cleanest solution is a URLEncodingMetaModule...

/Joakim
Regards,

Tony

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]