we have solve the same problem using action
map:actions
map:action name=set-encoding
src=org.apache.cocoon.acting.SetCharacterEncodingAction/
...
...
...
!-- === order form === --
map:pipeline
Thx.
At 16:03 27/11/2003 +0200, you wrote:
we have solve the same problem using action
map:actions
map:action name=set-encoding
src=org.apache.cocoon.acting.SetCharacterEncodingAction/
...
...
...
!-- === order form
Hi,
I am very new to coccon so please excuse any glaring errors in my
question.
I have written a transformer whose job in part is to extrat a uri
from a knowledge article returned from our knowledgebase.
swsolution
cinclude:include select=*|text()
Simon Hutchinson wrote:
This solution works until I try to generate a uri with an illegal
character ie a space.
It appears that the request-param is (correctly) decoding the
parameter I am passing it but unfortunately this is not the behaviour I
require.
Is there any way that I can
copied my Cocoon based WebApp from one Tomcat to another. On
the new copy, the page is displayed incorrectly - browser takes
encoding as ISO-8859-1 instead of UTF-8. When I change encoding
manually to UTF-8 it is displayed correctly. I'm also checking both
copies using the same browser. I have
the browser's
text encoding the UTF-8 everything is fine. Can any one suggest how I
can configure Cocoon 2.1.3 to output UTF-8?
sitemap.xmap
===
map:serializers default=xhtml
map:serializer logger=sitemap.serializer.xhtml
mime-type=text/html name=xhtml
pool-grow=2 pool-max=64 pool-min
Tony Collen wrote:
Simon Hutchinson wrote:
This solution works until I try to generate a uri with an illegal
character ie a space.
It appears that the request-param is (correctly) decoding the
parameter I am passing it but unfortunately this is not the behaviour
I require.
Is there
On Tue, Nov 18, 2003 at 11:10:38AM +0100, [EMAIL PROTECTED] wrote:
Hi,
I have copied my Cocoon based WebApp from one Tomcat to another. On
the new copy, the page is displayed incorrectly - browser takes
encoding as ISO-8859-1 instead of UTF-8. When I change encoding
manually to UTF-8
I'm having problems with character encodings. I've specified in every
place I could think of that I want all XHTML pages to be rendered as
UTF-8. However, when I view them in a browser I get garbage for all of
the special characters. When I manually toggle the browser's text
encoding
Hello,
I would like to use accents (for french) and I'm looking for a solution to set the
encoding in ISO-8859-1.
Is someone has an experience?
Thanks
Sylvain
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I would like to use accents (for french) and I'm looking for a solution to set the encoding in ISO-8859-1.
I don't know, if I undestand you correctly, but if you have form
encoding problems, this may help (I received when asking for woody, but
I think it doesn't matter):
It's a problem
Hello,
Yes it was my problem and it WORKS!
Thanks
Sylvain
-Message d'origine-
De: Marcin Okraszewski [mailto:[EMAIL PROTECTED]
Date: lundi, 17. novembre 2003 11:05
À: [EMAIL PROTECTED]
Objet: Re: [JXForm/XMLForm] how to set encoding
I would like to use accents (for french
Hi.
I have problem with encoding of Woody webforms. I tried registration
sample and when I write non-us characters the form comes refilled with
two strange singns instead of one I've inputed (co is converted to
co).
How to manage with this?
Regards,
Marcin Okraszewski
This is an encoding problem. It seems UTF-8 interpreted as the Western encoding
(sorry I don't remember its name)
David
-Mensaje original-
De: Marcin Okraszewski [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 07 de noviembre de 2003 14:21
Para: [EMAIL PROTECTED]
Asunto: Woody
On Fri, 2003-11-07 at 14:20, Marcin Okraszewski wrote:
Hi.
I have problem with encoding of Woody webforms. I tried registration
sample and when I write non-us characters the form comes refilled with
two strange singns instead of one I've inputed (co is converted to
co).
How to manage
Hallo,
i need to set correctlythe encoding of my xml
output files in apipeline.
For example:
if I use a simplepipeline like
this
map:generate src=""/map:transform
src=""/map:serialize/
The xml encoding in the input.xml is
ISO-8859-1,
The xml encoding ofthe sim
use
serialize type="xml" /
Jelle
-Oorspronkelijk bericht-Van: Gianluca Morello
[mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003
17:21Aan: [EMAIL PROTECTED]Onderwerp: [HELP]: How
to set xml encoding?
Hallo,
i need to set correctlythe enco
Gianluca Morello wrote:
Hallo,
i need to set correctly the encoding of my xml output files in apipeline.
For example:
if I use a simple pipeline like this
map:generate src=input.xml/
map:transform src=simple.xsl/
map:serialize/
The xml encoding in the input.xml is ISO-8859-1,
The xml
Sorry,
al little too quick perhaps. You should also define the encoding in the
components section, for example:
map:serializers
default="html"
label="result"
map:serializer name="xml" mime-type="text/xml"
src=""
encodingUTF-8/encoding
Hallo Jelle,
My serializers map is like this:
map:serializers
default="html" map:serializer name="xml-iso"
mime-type="text/xml"
src=""
encodingISO-8859-1/encoding
/map:serializer /map:serializers
And using the following pipeline the xml output
Sorry,
I don't know enough
about the SourceWritingTransformer to tell you how to set the encoding for the
SourceWritingTransformer.
Anybody
else?
-Oorspronkelijk
bericht-Van: Gianluca Morello
[mailto:[EMAIL PROTECTED]Verzonden: donderdag 6 november 2003
18:07Aan: [EMAIL
.
I would like to output as xhtml but would prefer the output using the
text encoding as in the html example.
Is this possible?
Many thanks,
John.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
with URL encoded
searchString everything works.
What is my error?
Thanks
-Original Message-
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 23. Oktober 2003 01:19
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
Hello Roman,
for the request generator
of them is the search result HTML (Your search for
GieEUR?harz has no hits.). I guess you have to debug around a bit
where the string is Gießharz and where not. It should always be in
this representation internally. What about encoding (ISO-8859-1 vs.
UTF-8)? How does your searchPageResult pipeline
}/
When I use UTF-8 encoding for form-encoding and ISO-8859-1 for
container-encoding Gießharz is sending to the servlet. If both are UTF-8
something like Gie~A#harz is sent to the servlet.
I ask the developer of the servlet, what kind of format he needs. He needs
the format Gie%C3%9Fharz
? How have you fix it (if)?
When I use UTF-8 encoding for form-encoding and ISO-8859-1 for
container-encoding Gießharz is sending to the servlet. If both are UTF-8
something like Gie~A#harz is sent to the servlet.
Container encoding should always be ISO-8859-1, independent on the form
handling
October 2003 10:55
To: [EMAIL PROTECTED]
Subject: Re: URL encoding for request
On 23.10.2003 13:35, Fleischer Roman wrote:
I think it is a problem for the used searcheDatabase
Servlet. For the
result I use a file-generator, but in reality it is a service like:
map:generate
src=http
the output
of the request generator back into a HTML page with links, the @href
will be URL encoded again - at least that should be done by the XML
serializer.
Joerg
On 21.10.2003 14:10, Fleischer Roman wrote:
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http
Hello,
i have some problems with URL encoding.
I call a matcher in this form:
http://127.0.0.1/cocoon/OCIprod?searchString=Gie%C3%9FharzsearchMLFB=searc
h=result...
(%C3%9F is the german ss)
In the matcher i call a request generator and a xml-serializer.
The result is:
...
h:requestParameters
hi people
i have (as many other people here) encoding problems with greek language
i have a mysql dadabase runing on winXP with greek content
i try a very simple query using cocoon 2.1 using two different connection
methods
1. using MySQLConnector/j (3.0)
2. using ODBC connection
What encoding do you use in your DB? I solved all my encoding problems
when I changed the encoding of my DB to UNICODE. (But I don't know if
this possible in MySQL now. I migrated to PostgreSQL for this reason, a
long time ago)
/leo
On Oct 17, 2003, at 4:02 PM, [EMAIL PROTECTED] wrote:
hi
Came across a similar problem a while back. The solution was to add
parameters to the database url, setting the character encoding to the one
that java uses.
in WEB-INF/cocoon.xconf:
datasources
jdbc name=databaseName logger=core.datasources.databaseName
pool-controller min=5 max=10
the character encoding to the one
that java uses.
in WEB-INF/cocoon.xconf:
datasources
jdbc name=databaseName logger=core.datasources.databaseName
pool-controller min=5 max=10/
dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEnco
ding=Cp1252/dburl
userusername
thnx to all of you
finaly i have try to insert greek content in MySQL using connect/j
i write down all the step i have to do
cocoon.xconf
dburljdbc:mysql://localhost/databaseName?useUnicode=trueamp;characterEncoding=ISO-8859-7/dburl
sitemap.xmap
in actions:
map:action name=set-encoding
src
Hello again,
special characters in the request parameter in my JSP are somehow
encrypted and even using java.net.URLDecoder.decode() doesn't change
that. I tried to set the encoding to ISO-8859-1 but it didn't work at
all. Has anyone had a similar problem yet?
I am grateful for any hint
On Fri, 19 Sep 2003 09:00:44 +0200
Christoph Strehl [EMAIL PROTECTED] wrote:
Hello again,
special characters in the request parameter in my JSP are somehow
encrypted and even using java.net.URLDecoder.decode() doesn't change
that. I tried to set the encoding to ISO-8859-1 but it didn't work
Tony ( others),
Is this the same problem we talked about last week on wsproxy parameter
encoding?
http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h
tml
That thread was left hanging.
Jeff
-Original Message-
From: Christoph Strehl [mailto:[EMAIL PROTECTED
Jeff Ramsdale wrote:
Tony ( others),
Is this the same problem we talked about last week on wsproxy parameter
encoding?
http://archives.real-time.com/pipermail/cocoon-users/2003-September/038837.h
tml
That thread was left hanging.
Hrm.. it seems similar, but I'm not too sure. As far
Yury Mikhienko [EMAIL PROTECTED] writes:
in serializers section I have:
map:serializer logger=sitemap.serializer.text mime-type=text/plain
name=UTF_16_text src=org.apache.cocoon.serialization.TextSerializer
encodingUTF-16/encoding
/map:serializer
in pipeline section
Hi all!
I use: cocoon2.0.4 + Tomcat 4.1.24
In first two octets document text body (first 2 bytes) I get the %FF%FE bytes when I
try get UTF-16 encoded document (html, text, xml).
Why? If I try get the document in other encoding I do not get that bytes (so ok).
How I can solve this problem
document (html, text, xml).
Why? If I try get the document in other encoding I do not get that bytes
(so ok).
How I can solve this problem?
Or I'm wrong?
Many thanks for help!
--
Best regards,
Yury Mikhienko.
IT engineer, ZAO Mobicom-Kavkaz
possibilities:
1. Replace the pure links by a form, the request params are now encoded with
ISO-8859-1 too.
2. Change the serializer configuration to UTF-8 and set the form encoding
either in the web.xml or using the SetCharacterEncodingAction to UTF-8 (now
everything is handled as UTF-8).
3. The links
It seems that by default JSP reader encoding is UTF-8.
How it can be changed to other encoding. I have tried like:
map:reader name=jsp src=org.apache.cocoon.reading.JSPReader
encodingShift_JIS/encoding
/map:reader
But it seems does not working. Any idea?
Regards,
Abolhassani
on Tue, 19 Aug 2003 23:51:20 -0600 (CST) Antonio Gallardo
[EMAIL PROTECTED] wrote:
Hi:
Why the web.xml of cocoon is still having:
?xml version=1.0 encoding=ISO-8859-1?
I already changed it to
?xml version=1.0 encoding=UTF-8?
and it works.
Of course it works, UTF-8 is superset
Joerg Heinicke dijo:
Is there any problem with ISO-8859-1 or do you think switching to UTF-8
would be good in general?
I think switching all to UTF-8 would be good in general. It is a step
ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a
deprecated encoding. The IETF
rufio dijo:
Of course it works, UTF-8 is superset of ISO-8859-1.
Yep. But the correct would be have all in UTF-8 and not using the
deprecated ISO-8859-1
Antonio Gallardo.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
to UTF-8
would be good in general?
I think switching all to UTF-8 would be good in general. It is a step
ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a
deprecated encoding. The IETF recommend UTF-8 instead of any other flavor
of ISO-885x-x. Windows changed to UNICODE
Joerg Heinicke dijo:
Wow, what a /hymn/ on UTF-8 :-) I know the advantages of UTF-8 and even
if there is currently no need for switching I did it. The conversion was
done hopefully correctly by jEdit.
Thanks, I know this is a little change (and maybe meaningless), but I hope
it would help us
Hi:
Why the web.xml of cocoon is still having:
?xml version=1.0 encoding=ISO-8859-1?
I already changed it to
?xml version=1.0 encoding=UTF-8?
and it works.
Best Regards,
Antonio Gallardo
-
To unsubscribe, e-mail: [EMAIL
On Sun, Aug 10, 2003 at 11:25:24AM +0200, Joerg Heinicke wrote:
Was the issue already solved (I read so many mails yesterday)?
web.xml:
init-param
param-nameform-encoding/param-name
param-valueiso-8859-2/param-value
/init-param
Or if you do not want to override default form encoding
Hi all,
I'm having some trouble with character encoding on
cocoon. Basically, i'm using Jboss-Net to access webservices via SOAP. The Soap
Response has the encoding correct but the presentation (with cocoon) is showing
some characters all garbled.
Here's a simple method i've used to test
I'm really fond of using ISO-8859-2 encoding.
I've set both xml i html serializer to this encoding.
That's ok. Every generated paged is displayed properly
(also data from database). But I can't get through
proper encoding request parameters. The only way
I was able to do it correctly was xsp page
Hi:
please check this:
http://wiki.cocoondev.org/Wiki.jsp?page=RequestParameterEncoding
Best Regards,
Antonio Gallardo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, 2003-08-04 at 15:13, Mariusz Sieraczkiewicz wrote:
snip/
(Additional info: web.xml (of COcoon) form-encoding and container-encoding
set to utf-8 !! - the only good working setting with the others I've
described earlier.)
container-encoding must be set to ISO-8859-1
form-encoding
Hello,
container-encoding must be set to ISO-8859-1
form-encoding should be set to ISO-8859-2
Yes, that really helped!!!
thank you so much, I'm your deptor. This is
what I've been looking for. I may go on holiday
now ;-)
Best regards
Yury Mikhienko wrote:
On Thu, 17 Jul 2003 10:25:56 -0400
Geoff Howard [EMAIL PROTECTED] wrote:
Yury Mikhienko wrote:
On Thu, 17 Jul 2003 09:43:27 -0400
Geoff Howard [EMAIL PROTECTED] wrote:
Sometime ago this question was already asked on cocoon-dev list,
but setup() method is not implemented
Sometime ago this question was already asked on cocoon-dev list,
but setup() method is not implemented in serializers at this time ((
You declare the encoding as part of the serializer config in the
sitemap. if you need the same serializer to use different encodings in
different pipelines
Title: native encoding for xsp page output
Hi
I have posted a question on setting up html serializer with native encoding and I think I kind of understand that part.
Within the xsp page, do I need to do something special to ensure such encoding or will the serializer can handle
Yury Mikhienko wrote:
Sometime ago this question was already asked on cocoon-dev list,
but setup() method is not implemented in serializers at this time ((
Sorry, I must not be coming across clearly: you must declare the
encoding in the definition of your serializer in the map:components
Yury Mikhienko wrote:
On Thu, 17 Jul 2003 09:43:27 -0400
Geoff Howard [EMAIL PROTECTED] wrote:
Sometime ago this question was already asked on cocoon-dev list,
but setup() method is not implemented in serializers at this time ((
...
Hope that clears it up,
Geoff
Yes, you are right, but
On Thu, 17 Jul 2003 10:25:56 -0400
Geoff Howard [EMAIL PROTECTED] wrote:
Yury Mikhienko wrote:
On Thu, 17 Jul 2003 09:43:27 -0400
Geoff Howard [EMAIL PROTECTED] wrote:
Sometime ago this question was already asked on cocoon-dev list,
but setup() method is not implemented in serializers
Title: xsp to generate html page with different encoding?
hi
I want to have a xsp to render a html page containing a form. The character encoding of the page (presumably this will affect the form as well) is determined by a external parameter, e.g. a request param saying something like en
Title: RE: dynamic encoding for html serialiser?
So you are saying I could do something like:
map:match pattern=*/test
map:act type=characterencoding
map:parameter name=form-encoding value=utf-8/
/map:act
map:act type=sethtmlencparam/ !-- set up pipeline param html_enc
actually, the encoding I think has to get passed as a parameter to
map:serializer (that is in the component definition) not where you call
it in the sitemap. I don't know the exact param name or I'd give you an
example. There should be some in the docs, though.
Geoff
Tsui, Alban wrote:
So
Hello Charlene,
this is configured in the sitemap in the map:serializers/. Simply add an
encodingISO-8859-1/encoding.
Example:
map:serializer name=html src=org.apache.cocoon
encodingISO-8859-1/encoding
/map:serializer
This has the same effect as the xsl:output encoding=/ declaration
501 - 565 of 565 matches
Mail list logo
