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.
|
| cc:
|
| Subject: XML serializer; handling characters outside the encoding
|
>--|
I have a data
I have a data consumer who is pulling XML from our Cocoon webapp. They
couldn't handle UTF-8 on their end, so I gave them the option to pull data
in US-ASCII encoding. However, when I did that, symbol characters such as
Greek and math symbols got sent over even though they aren
Thanks - that's a big help, although I may just take the path of least
resistance and hand-configure for now :)
-Christopher
The fact that serializers don't accept parameters and don't have access
to the objecmodel has come up before here and is indeed a pain.
Can you maybe add a node to
ere is a
patch waiting for the 2.1x branch that is supposed to add parameters for
the SVG serializer. Maybe you can have a look how it's done and
generalize it to the 2.0.x branch for any serializer.
Hope this helps
Jorg
Christopher Painter-Wakefield wrote:
Is there any way to dynamically
Is there any way to dynamically set the encoding of output on a serializer,
specifically the XML serializer? I have a customer who is having trouble
handing UTF-8 output from my application (he is using Lotus Notes), and
would like me to supply a different encoding. I can just create a
I found some answers but not all.
I miss one thing.
When i create a document from an xsp (parameters comes from a post), the
flow is encoded twice is that normal ?
At 15:13 10/12/2003 +0100, you wrote:
Hi,
I' have some real problems to with my encoding.
My application get some param
Hi,
I' have some real problems to with my encoding.
My application get some parameters from the form and create a document with
an xsp.
After that, I'm using DOM and SAX transformers, generators, etc ... to
manipulate the XML document.
I'm trying to figure out, what should I c
perly configured for this encoding. My XSL file is
http://www.w3.org/1999/XSL/Transform";>
and XML
żółta ćma
Any sugestions?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, Dec 02, 2003 at 03:10:51PM +0100, Jakub Kaniewski wrote:
> I have problem with character encoding, when using standart Cocoon
> database actions (like explained in tutorial action-set, that use class
> org.apache.cocoon.acting.DatabaseAddAction). All my Cocoon engine i set
&g
I have problem with character encoding, when using standart Cocoon
database actions (like explained in tutorial action-set, that use class
org.apache.cocoon.acting.DatabaseAddAction). All my Cocoon engine i set
to encode in iso-8859-2 charset, I have no problem in fetching good
encoded record
> >> > data of
> >> > uploaded file, many of characters are replaced by '?'. When I tried to
> >> > store
> >> > data to the file, everything was ok (it means, that from InputStream
> >> are
> >> > going
> >> > out rel
Christian Haul wrote:
[EMAIL PROTECTED] wrote:
Db supports BLOBs, but I never did anything with them in java, less so
cocoon :) Is it possible to use ESQL someways? Probably not, isn't it :)
ESQL and (modular) database actions support blob, clob types.
AFAIR ESQL can only get them while the a
[EMAIL PROTECTED] wrote:
Db supports BLOBs, but I never did anything with them in java, less so
cocoon :) Is it possible to use ESQL someways? Probably not, isn't it :)
ESQL and (modular) database actions support blob, clob types.
AFAIR ESQL can only get them while the actions can insert and
upda
eans, that from InputStream
>> are
>> > going
>> > out relative correct characters). It looks like, that problem comes on
>> by
>> > assigning of InputStream data to the String (I tried InputSt
s are replaced by '?'. When I tried to
> > store
> > data to the file, everything was ok (it means, that from InputStream are
> > going
> > out relative correct characters). It looks like, that problem comes on by
> > assigning of InputStream data to the Strin
ream data to the String (I tried InputStreamReader
> with
> correct encoding also) and following storing into database for this reason
> fails.
>
> What have I to do differently? Thanx a lot!
>
> osup
>
> -
eans, that from InputStream are going
out relative correct characters). It looks like, that problem comes on by
assigning of InputStream data to the String (I tried InputStreamReader with
correct encoding also) and following storing into database for this reason
fails.
What have I to do different
d to change the
container-encoding to avoid encoding problems.
> Now we do not have any problems with encoding anymore and we don't need
entries in the sitemaps.
>
>
> form-encoding
Thu, 27 Nov 2003, Boris Althaus wrote:
> Hallo Lionel,
>
> we had problems with this issues several times.
> Play arround with these two initparams.
> The strange thing was, that on different engines we had to change the
> container-encoding to avoid
In fact :
The "encoding" parameter for the serializer modify the
declaration according the the value.
Now I'm sure of that, my previous message was false.
Now, I'm using that :
1024
UTF-8
This lines above allow me not to set the form-encoding parame
Hallo Lionel,
we had problems with this issues several
times.
Play arround with these two
initparams.
The strange thing was, that on different engines we
had to change the container-encoding to avoid encoding problems.
Now we do not have any problems with encoding
anymore and we don&#
Did you set the form-encoding parameter in web.xml?
Guido
Lionel Crine wrote:
> Hi,
>
> I want to put the entire plateform into UTF-8. For now, cocoon is
> using ISO-8859-1.
>
> Here what I've already done :
>
> mime-type="text/html" name="htm
> From: "Nicolas Toper" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Thu, 27 Nov 2003 12:16:11 +0100
> To: <[EMAIL PROTECTED]>
> Subject: RE: encoding, UTF-8
>
> Are you sure, the viewer is UTF8?
>
> -Message d'ori
i'm allmost sure that the entire cocoon has UTF-8 as default encoding
corect me
--stavros
On Thu, 27 Nov 2003, Nicolas Toper wrote:
> Are you sure, the viewer is UTF8?
>
> -Message d'origine-
> De : Lionel Crine [mailto:[EMAIL PROTECTED]
> Envoyι : jeu
Are you sure, the viewer is UTF8?
-Message d'origine-
De : Lionel Crine [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 27 novembre 2003 11:58
À : [EMAIL PROTECTED]
Objet : encoding, UTF-8
Hi,
I want to put the entire plateform into UTF-8. For now, cocoon is using
ISO-8859-1.
Here what
Hi,
I want to put the entire plateform into UTF-8. For now, cocoon is using
ISO-8859-1.
Here what I've already done :
1024
UTF-8
But that's not enough because I have many problem with the form.
When I reload it with some request parameter (using xsl:value-of).
The characters a
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 a
rs. When I manually toggle 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
===
pool-grow="2" pool-max="64" pool-min="2"
src="org.apache.cocoon.
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 it is displayed correctly. I'm also checking both
copies using the same brows
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 r
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.
cocoon:/soldoc?url=
e 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 the UTF-8 everything is fine. Can any one suggest how I can
co
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&#
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 e
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 it is displayed correctly. I'm also checking both
copies using the same br
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) 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'
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 addit
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Å&quo
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:
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?
Re
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: [
Hallo Jelle,
My serializers map is like this:
ISO-8859-1
And using the following pipeline the xml output
encoding is correct!
Thank you for your help.
I still have problems with encoding because i have
to write xml to file system:
I'm
Sorry,
al little too quick perhaps. You should also define the encoding in the
components section, for example:
UTF-8
ISO-8859-1
-Oorspronkelijk bericht-Van: Alten, Jelle Paul
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
The xml encoding in the input.xml is ISO-8859-1,
The xml encoding of the simple.xsl s ISO-8859-1,
The simple.xsl file contains a
use
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 correctly the encoding of my
xml output files
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
The xml encoding in the input.xml is
ISO-8859-1,
The xml encoding of the simple.xsl s
ISO-8859-1,
The simple.xsl file contains a line like
this
m not sure the extra char will appear in this email, however viewing
the page in a browser displays an additional A with a caret in front of
the half symbol.
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,
On Mon, 2003-11-03 at 16:14, Gianluca Morello wrote:
> Hallo,
>
> i'm using woody binding for editing some xml files.
>
> I notice that the saved xml don't have the CDATA tag anymore.
> Is there a way to mantain the CDATA tag in the output xml?
If the CDATA-containing nodes are being modified b
d that the encoding of my xml files was changed to UTF-8 from
ISO-8859-1.
Thank you for your help
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
; Sent: Friday, 24 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-gen
you have a similar problem? 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 alwa
"/>
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 f
match. One 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-
-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 the decoding is okay. It gives the request
params in their string representation in a
sform 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:
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%9Fharz&searchMLFB=&searc
h=result...
(%C3%9F is the german "ss")
In the matcher i call a request generator and a xml-seriali
ill be like this ? :
>
>
> jdbc:mysql://localhost/databaseName?useUnicode=true&characterEncoding=UTF-8
>
>
>
> On Fri, 17 Oct 2003, Mark H wrote:
>
> > Came across a similar problem a while back. The solution was to add
> > parameters to the database url, setting the chara
character encoding to the one
> that java uses.
>
> in WEB-INF/cocoon.xconf:
>
>
>
>
>
> jdbc:mysql://localhost/databaseName?useUnicode=true&characterEnco
> ding=Cp1252
> username
> password
>
>
>
> Mar
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:
jdbc:mysql://localhost/databaseName?useUnicode=true&characterEnco
ding=Cp1252
user
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 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
in
No.
What you need for the wsproxy is simply a re-encoding of the decoded
parameters.
What he needs for the JSPGenerator/Reader is simply an encoding
configuration issue. In what encoding are the pages? In what encoding do
you read the requests? Have a look at Cocoon&#
Thanks Tony,
I'll try to take a look at it...
Jeff
> -Original Message-
> From: Tony Collen [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 19, 2003 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: Re: JSPGen. RequestParameter Encoding
>
>
> Jeff Ramsd
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.
Jeff,
It seems the WSPG is getting decoded parameters, but is
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 f
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
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 "
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 g
Yury Mikhienko <[EMAIL PROTECTED]> writes:
> in serializers section I have:
> name="UTF_16_text" src="org.apache.cocoon.serialization.TextSerializer">
> UTF-16
>
>
>
> in pipeline section:
>
>
>
>
>
>
>
>
> my test.xml file:
>
>
> тест test
>
e: 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).
&g
coded 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 "
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?
Or
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 are only for a specific group
I produce a webpage with links with German letters in the href
attribute.
The German letters are not encoded when cocoon sends the request.
What shall I do to get this encoding, which is done for the normal text
in the HTML-Page
It seems that by default JSP reader encoding is UTF-8.
How it can be changed to other encoding. I have tried like:
Shift_JIS
But it seems does not working. Any idea?
Regards,
Abolhassani
-
To unsubscribe
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 u
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
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 addi
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. Th
Is there any problem with ISO-8859-1 or do you think switching to UTF-8
would be good in general?
Joerg
Antonio Gallardo wrote:
Hi:
Why the web.xml of cocoon is still having:
I already changed it to
and it works.
Best Regards,
Antonio Gallardo
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:
>
>
>
> I already changed it to
>
>
>
> and it works.
Of course it works, UTF-8 is superset of ISO-8859-1.
Regards, Rufio
--
Hi:
Why the web.xml of cocoon is still having:
I already changed it to
and it works.
Best Regards,
Antonio Gallardo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Was the issue already solved (I read so many mails yesterday)?
web.xml:
form-encoding
iso-8859-2
Joerg
Mariusz Sieraczkiewicz wrote:
Hello,
I used to use
in XSP code in order to get properly encoded string in Polish.
How can I (if I can, of course) achieve similar effect
using one of
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:
>
>
> form-encoding
> iso-8859-2
>
Or if you do not want to override default form encoding for whol
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 meth
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 ;-
On Mon, 2003-08-04 at 15:13, Mariusz Sieraczkiewicz wrote:
>
> (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-885
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]
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 co
Hello,
I used to use
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 implemente
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 implement
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 impleme
ly: you must declare the
> encoding in the definition of your serializer in the map:components
> section of the sitemap. This configuration is read during configure().
>
>
> ...
>
> src="org.apache.cocoon.serialization.XMLSerializer" ...>
> encoding1
>
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
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 it
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
>
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
501 - 600 of 622 matches
Mail list logo
