]
Subject: Fwd: jfor encoding problem (POST encoding problem, indeed)
Hi Charlene,
using the Orderpage example at
http://localhost:8080/cocoon/samples/stream/order. If you add ?xml
version=1.0 encoding=ISO-8859-1? at the top of the default xml
and change Order Id to be Gérer, the next html
To: [EMAIL PROTECTED]
Cc: Yan, Charlene
Subject: Re: jfor encoding problem
Le Lundi, 2 juin 2003, à 21:51 Europe/Zurich, Yan, Charlene a écrit :
...
I'm trying to display accented characters correctly using jfor.
However, when I try to run
http://localhost:8080/cocoon/samples/jfor/minimal.rtf
To: [EMAIL PROTECTED]
Cc: Yan, Charlene
Subject: Re: jfor encoding problem
Le Lundi, 2 juin 2003, à 21:51 Europe/Zurich, Yan, Charlene a écrit :
...
I'm trying to display accented characters correctly using jfor.
However, when I try to run
http://localhost:8080/cocoon/samples/jfor/minimal.rtf
nothing to do with jfor - in your scenario, Cocoon's
StreamGenerator is used to read your XML from an HTML form field.
Your encoding problem is caused by the StreamGenerator using the wrong
encoding when *reading data* from the form's POST request. To use a
different encoding, you have to change
Hi everyone,
I'm trying to display accented characters correctly using jfor. However, when I try
to run http://localhost:8080/cocoon/samples/jfor/minimal.rtf, it gives the following
exception. I have put some French words such as Gére in the xml file. Looks like
it is a parser issue.
an encoding declaration to the start of the
file. e.g. ?xml version=1.0 encoding=ISO-8859-1?
Cheers
Con
-Original Message-
From: Yan, Charlene [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 3 June 2003 07:52
To: [EMAIL PROTECTED]
Subject: jfor encoding problem
Hi everyone,
I'm trying
: Monday, June 02, 2003 5:05 PM
To: [EMAIL PROTECTED]
Subject: RE: jfor encoding problem
Charlene, it looks to me like your problem is not with jfor, but merely with parsing
the XML source file.
The parser thinks the French text is encoded as UTF-8, but my guess is that it
actually uses ISO-8859
Le Lundi, 2 juin 2003, à 21:51 Europe/Zurich, Yan, Charlene a écrit :
...
I'm trying to display accented characters correctly using jfor.
However, when I try to run
http://localhost:8080/cocoon/samples/jfor/minimal.rtf, it gives the
following exception. I have put some French words such as
Le Mardi, 3 juin 2003, à 07:40 Europe/Zurich, Bertrand Delacretaz a
écrit :
...Is the encoding declaration correct in your input XML?
Sorry, didn't notice that this was answered already (but I had two
other messages from the same person at my private address ;-)
-Bertrand
Hello,
I'm having trouble with my xsp page and ISO-8859-1 encoding. I use
cocoon-2.0.4.
I have an xsp which get the request object of a form and create again a
link for an xsl page which redirect all to frame.
All generators, transfomers and serializer have to encoding parameter.
the sitemap
I'm encountering a problem where this à character in a javascript file
causes illegal character exceptions when read with the resource reader, but
not when I open the file up directly from the filesystem. The character
occurs inside a javascript character array [Ã]. Cocoon serves an html page
and
Title: Nachricht
hi,
does anyone know why
when using xsp or espacially esql, all characters like ä,ö,ü etc. are turned
into funny characters like Ã(ö).
i am trying to
firgure out why that happens, and what unicode i have to use for languages using
those characters, like e.g. german.
SORRY I'VE POSTED THIS YET BUT I FORGOT THE SUBJECT
I'm using ESQL to read and write data from a MYSQL database.
When I fill a field with non US characters, I see strange characters instead of the
ones I expected.
For example, when I write the string òàù, this is written like =a?, even if
On 18.Dec.2002 -- 05:33 PM, [EMAIL PROTECTED] wrote:
SORRY I'VE POSTED THIS YET BUT I FORGOT THE SUBJECT
I'm using ESQL to read and write data from a MYSQL database.
When I fill a field with non US characters, I see strange characters instead of the
ones I expected.
For example, when I
Hi all,
I have a mySQL database with varchar fields containing foreign characters
(ex. ë) Queries in the mySQL client yield correct results.
When I do a query using the SQLTransfomer or esql the non ASCII characters
are not presented properly. The ë is converted to ë
Here's the pipeline:
ottobre 2002 13.39
A: [EMAIL PROTECTED]
Oggetto: encoding problem
Hi all,
I have a mySQL database with varchar fields containing foreign characters
(ex. ë) Queries in the mySQL client yield correct results.
When I do a query using the SQLTransfomer or esql the non ASCII
characters
-
Da: Bert Van Kets [mailto:bert;vankets.com]
Inviato: venerdì 25 ottobre 2002 16.33
A: [EMAIL PROTECTED]
Oggetto: Re: R: encoding problem
Of course I checked the mail logs before bugging the list. I could not
find a solution though. I did find that I need to use UTF-8 and not
iso-8859-1
="form-encoding"
value="UTF-8"//map:act
That should work.
Boris
- Original Message -
From:
Bert Van Kets
To: [EMAIL PROTECTED]
Sent: Friday, October 25, 2002 1:39
PM
Subject: encoding problem
Hi all,I have a mySQL database with varchar field
: mailto:bert;vankets.comBert Van Kets
To: mailto:cocoon-users;xml.apache.org[EMAIL PROTECTED]
Sent: Friday, October 25, 2002 1:39 PM
Subject: encoding problem
Hi all,
I have a mySQL database with varchar fields containing foreign characters
(ex. ë) Queries in the mySQL client yield correct results
: encoding problem
Of course I checked the mail logs before bugging the list. I could not
find a solution though. I did find that I need to use UTF-8 and not
iso-8859-1 (the Cocoon default)
Searching through the source I found that a LOT of classes and XSLTs set
the encoding to iso-8859-1
pe="upd-mitarbeiter"//map:action-set/map:action-sets
I don't know if there are other
possibilities.
Boris
- Original Message -
From:
Bert Van Kets
To: [EMAIL PROTECTED]
Sent: Friday, October 25, 2002 4:58
PM
Subject: Re: encoding problem
I'm using a build
On Fri, 2002-10-25 at 16:33, Bert Van Kets wrote:
Of course I checked the mail logs before bugging the list. I could not
find a solution though. I did find that I need to use UTF-8 and not
iso-8859-1 (the Cocoon default)
Searching through the source I found that a LOT of classes and
Hello,
doing the following I do not get the expected results. The german umlaut
with ISO-8859-1 converts magically to UTF-8. All encodings
(html-/xml-serializers, xml-files, xsl-files) are set to ISO-8859-1
src.xml:
html
head
...
a href=dest?selection=öö/ (ö = german umlaut for oe)
Try this in your sitemap:
map:action name=set-character-encoding
src=org.apache.cocoon.acting.SetCharacterEncodingAction/
and
map:act type=set-character-encoding
map:parameter name=form-encoding
value=your-encoding/
/map:act
--- Stefan Riegel [EMAIL PROTECTED] wrote:
Hello,
PROTECTED]
Subject: RE: SunShine-InsertTransformer: encoding problem
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
This is currently hard coded into the
transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
This is currently hard coded into the
transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged with the
SourceWritingTransformer
in 2.1-dev - the
Sorry for the re-post, but there have been some mail
problems on Friday when I posted it and I haven't
heard from anyone since then. I'm still struggling
with both problems, so any help would be greatly
appreciated.
Alex
--- Alex Romayev [EMAIL PROTECTED] wrote:
Sorry the C is supposed to read
Alex Romayev wrote:
Hi,
I'm trying my way around SunShine and running into
2
problems:
1) I have an existing XML file with UTF-8
encoding.
I
use InsertTransformer to add a new record. It
does
so
correctly, but changes the file encoding to
ISO-8859-1
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
Hi,
I'm trying my way around SunShine and running
into
2
problems:
1) I have an existing XML file with UTF-8
encoding.
I
use InsertTransformer to add a new record. It
does
so
Alex Romayev wrote:
This is currently hard coded into the transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged with the
SourceWritingTransformer
in 2.1-dev - the SourceWritingTransformer can be
configured
to what encoding should be
Hi,
I'm trying my way around SunShine and running into 2
problems:
1) I have an existing XML file with UTF-8 encoding. I
use InsertTransformer to add a new record. It does so
correctly, but changes the file encoding to ISO-8859-1
and replaces all non-English text with #1057;s and
alike.
2) I
Sorry the C is supposed to read as (I'm separating
with spaces) # 1 0 5 7 ;, the browser displays it
as a letter C.
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hi,
I'm trying my way around SunShine and running into 2
problems:
1) I have an existing XML file with UTF-8 encoding.
I
use
=$cityxsl:value-of
select=$city//a
After transformation I get:
a
href=city-detail=%D0%94%D0%B5%D0%BB%D0%B8Äåëè/a
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hello,
I'm having what seems to be an encoding problem --
not
sure it's related to Cocoon, but... ;)
xsl:for-each select=//city-name
maybe :
a href=city-detail={$city}xsl:value-of
select=$city//a
try to use Russian-compatible output encoding rather than utf-8 ?
- Original Message -
From: Alex Romayev [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 12:53 PM
Subject: Re: Encoding problem
- Original Message -
From: Alex Romayev [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 12:53 PM
Subject: Re: Encoding problem
Let me be more specific and also simplify the
example:
Works:
xsl:param name=city select='Delhi'/
...
a href
transformation I get:
a
href=city-detail=%D0%94%D0%B5%D0%BB%D0%B8Äåëè/a
What's serializer configuration? Does it have proper encoding set?
Vadim
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hello,
I'm having what seems to be an encoding problem --
not
sure it's related to Cocoon
proper
encoding set?
I'm using the default, i.e., I haven't changed
anything since installation.
Vadim
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hello,
I'm having what seems to be an encoding problem --
not
sure it's related to Cocoon, but... ;)
xsl:for-each select
PROTECTED] wrote:
Hello,
I'm having what seems to be an encoding problem --
not
sure it's related to Cocoon, but... ;)
xsl:for-each select=//city-name
a href=city-detail?city-name={.}xsl:value-of
select=.//abr/
/xsl:for-each
All my xml is UTF-8, it work in English
encoding set?
I'm using the default, i.e., I haven't changed
anything since installation.
Vadim
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hello,
I'm having what seems to be an encoding problem
--
not
sure it's related to Cocoon
Alex Romayev wrote:
--- Vadim Gritsenko [EMAIL PROTECTED]
wrote:
Alex Romayev wrote:
--- Vadim Gritsenko [EMAIL PROTECTED]
wrote:
...
Good point, I may have a problem in another stylesheet
(part of the pipeline that responds to the url in
question):
This parameter is set by the
--- Vadim Gritsenko [EMAIL PROTECTED]
wrote:
Alex Romayev wrote:
--- Vadim Gritsenko [EMAIL PROTECTED]
wrote:
Alex Romayev wrote:
--- Vadim Gritsenko [EMAIL PROTECTED]
wrote:
...
Good point, I may have a problem in another
stylesheet
(part of the pipeline that
Hello,
I'm having what seems to be an encoding problem -- not
sure it's related to Cocoon, but... ;)
xsl:for-each select=//city-name
a href=city-detail?city-name={.}xsl:value-of
select=.//abr/
/xsl:for-each
All my xml is UTF-8, it work in English, but not in
Russian. Any ideas?
Thanks
Hello Thorsten,
there was a bug in Xalan with URL encoding more than a half year ago, but I
don't know what's the current status.
xsl:template match='c[@color=blue]'
xsl:element name=a
xsl:attribute name=href
frameset.xsp?filename=xsl:value-of
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
desired output:
a
href=frameset.xsp?filename=foo.xmlsearchstring=Integrations
auml;mter
Integrationsauml;mter
/a .
Manos Batsis wrote:
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
desired output:
a
href=frameset.xsp?filename=foo.xmlsearchstring=Integrations
auml;mter
Integrationsauml;mter
/a .
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
Still no. Of course you can write this in your XML input, but in the
serialized output a valid URL has to be written. And auml;
is not valid,
the is reserved for concatenating request parameters.
My apologies, I should have read the
If anyone has some more ideas on this topic (non-ISO-8859-1 characters
within URIs), I would greatly appreciate some more input.
Conclusion for me is to avoid such characters in URIs. But this does
not get easily into the heads of our customers and users. (e.g. file
names)
According to the
- Original Message -
From: Vadim Gritsenko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 4:36 PM
Subject: RE: encoding problem with xslt
From: Jens Lorenz [mailto:[EMAIL PROTECTED]]
...
If anyone has some more ideas on this topic (non-ISO-8859-1 characters
- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 4:45 PM
Subject: Re: encoding problem with xslt
If anyone has some more ideas on this topic (non-ISO-8859-1 characters
within URIs), I would greatly appreciate some more
From: Jens Lorenz [mailto:[EMAIL PROTECTED]]
- Original Message -
From: Vadim Gritsenko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 4:36 PM
Subject: RE: encoding problem with xslt
From: Jens Lorenz [mailto:[EMAIL PROTECTED]]
...
If anyone has
Subject: Re: encoding problem with xslt
If anyone has some more ideas on this topic (non-ISO-8859-1 characters
within URIs), I would greatly appreciate some more input.
Conclusion for me is to avoid such characters in URIs. But this does
not get easily into the heads of our customers and users
- Original Message -
From: Vadim Gritsenko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 5:05 PM
Subject: RE: encoding problem with xslt
snip/
Thanks for you input Vadim. But do not only think of web sites. But
also of web applications. Think of a web cms
- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 5:23 PM
Subject: Re: encoding problem with xslt
Hmm, I didn't test it a long time and didn't find a correlating bug by a
short view on Xalan bug list. It was a bug in our
Hi all,
I have a small encoding problem in cocoon 2.0.2. I have a utf-8 encoded
text that is transformed to html with an xsl stylesheet. After the
processing the unicode characters aren't displayed properly. When I
looked at the page source my characters were hardcoded in html entities
like
it ;-( *searching* thanx anywaymike
- Original Message -
From: Jan Uyttenhove
To: [EMAIL PROTECTED]
Sent: Friday, June 07, 2002 5:30 PM
Subject: RE: Tomcat/cocoon encoding problem
Try to start the jvm (tomcat startup) with property
-Dfile.encoding
10, 2002 9:17 AM
Subject: Re: Tomcat/cocoon encoding problem
Hi Michael,
Did you set the proper encoding for used cocoon's components
(generator, transformer and so on)? I imagine that serializer has it
because you wrote that the result XML encoding is ok. What about other
?
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
greetings
mike
- Original Message -
From: KOZLOV Roman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 10, 2002 9:17 AM
Subject: Re: Tomcat/cocoon encoding problem
Hi Michael,
Did you set the proper encoding
From: Michael Mangeng [mailto:[EMAIL PROTECTED]]
Hi
thanx for your help but i´ve already solved the problem with the help
of Jan
Uyttenhove.
My locale settings on the linux box had to be changed too.
I´ve written this points together: (hope they help if sombody get the
same
probs):
: Michael Mangeng
[mailto:[EMAIL PROTECTED]]Sent: vrijdag 7 juni 2002
16:47To: [EMAIL PROTECTED]Subject:
Tomcat/cocoon encoding problem
Hi
I´ve set the encoding of both the xsp and the xml
serializer correctly. Afteri requestthe xml i get the right
encoding - ISO-8859-1
That didn´t do it ;-(
*searching*
thanx anyway
mike
- Original Message -
From:
Jan
Uyttenhove
To: [EMAIL PROTECTED]
Sent: Friday, June 07, 2002 5:30 PM
Subject: RE: Tomcat/cocoon encoding
problem
Try
to start the jvm (tomcat startup) with property
Hi
I´ve set the encoding of both the xsp and the xml
serializer correctly. Afteri requestthe xml i get the right encoding
- ISO-8859-1 in the ?xml ... ? tag but german umlaut´s like äöü are
replacedby '?'.
I´ve noticed the same problem when i use beans on
my JSP Pages (without cocoon;
Hi all!
My JSPGenerator or jasper-compiler don't supported KOI8-R charset
encoding. What is me do?
Instructions llike
?xml version=1.0 encoding=KOI8-R? in header jsp page
or
map:generator name=jsp
src=org.apache.cocoon.generation.JspGenerator
logger=sitemap.generator.jsp label=content,data
From: yuryx [mailto:[EMAIL PROTECTED]]
Thanx for ideas ,Vadim.
But I can't undestand how declare JSP encoding.
Try to read JSP specification.
Vadim
instead of %out.println(?xml version='1.0' encoding='koi8-r'?);%
I try
?xml version='1.0' encoding='KOI8-R'? in sample.jsp
but again it
From: yuryx [mailto:[EMAIL PROTECTED]]
Thanx for ideas ,Vadim.
But I can't undestand how declare JSP encoding.
Try to read JSP specification.
The correct declaration is:
%@ page language=java import=java.text.SimpleDateFormat,java.util.*
pageEncoding=KOI8-R%?xml version='1.0'
From: yuryx [mailto:[EMAIL PROTECTED]]
Hi all!
My JSPGenerator or jasper-compiler don't supported KOI8-R charset
encoding. What is me do?
Use UTF-8 or Win-1251 which are (IIRC) supported.
Vadim
Instructions llike
?xml version=1.0 encoding=KOI8-R? in header jsp page
or
map:generator
From: yuryx [mailto:[EMAIL PROTECTED]]
Hi all!
My JSPGenerator or jasper-compiler don't supported KOI8-R charset
encoding. What is me do?
Use UTF-8 or Win-1251 which are (IIRC) supported.
KOI8-R is supported too. I've just checked.
Vadim
Instructions llike
?xml
Shes live!!! :)
Thanx for Piroumian, Konstantin and Vadim Gritsenko
Also thanx for all
I try
%@ page language=java import=java.text.SimpleDateFormat,java.util.*
_/*pageEncoding=KOI8-R*/_%
in my jsp page and this solve problem.
following line in sitemap
map:serialize type=html
Hello all!
I have following problem.
JSPGenerator doesn't normally encoding non english characters.
Simple sample:
sample.jsp:
%out.println(?xml version='1.0' encoding='koi8-r'?);%
%@ page language=java
import=java.text.SimpleDateFormat,java.util.*,java.sql.*%
page
content
Piroumian
- Original Message -
From: yuryx [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 07, 2002 7:50 PM
Subject: JSPGenerator encoding problem
Hello all!
I have following problem.
JSPGenerator doesn't normally encoding non english characters.
Simple sample:
sample.jsp
, February 07, 2002 7:50 PM
Subject: JSPGenerator encoding problem
Hello all!
I have following problem.
JSPGenerator doesn't normally encoding non english characters.
Simple sample:
sample.jsp:
%out.println(?xml version='1.0' encoding='koi8-r'?);%
%@ page language=java
import
: JSPGenerator encoding problem
Without transformation I have
page
content
paraETH;Ograve;Eacute;times;Aring;Ocirc;!/para
/content
/page
Problem with generation, I know...
Piroumian, Konstantin wrote:
Is it the problem of JSPGenerator or maybe this happens during
not declares JSP encoding as it should.
Obviously JSP runtime is unable to read characters correctly.
Regards,
Vadim
-Original Message-
From: yuryx [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 1:06 PM
To: [EMAIL PROTECTED]
Subject: Re: JSPGenerator encoding problem
Without
]
Sent: Friday, February 08, 2002 9:46 AM
Subject: Re: JSPGenerator encoding problem
Thanx for ideas ,Vadim.
But I can't undestand how declare JSP encoding.
instead of %out.println(?xml version='1.0' encoding='koi8-r'?);% I try
?xml version='1.0' encoding='KOI8-R'? in sample.jsp
but again
Hi Peter!
I try your recomendation
but it don't solved my problem :(
Encoding problem in Generator , or, maybe, in jasper compiller...
Yury
Peter Schwenke wrote:
Hi Yury,
Have you tried
map:serializers default=html
map:serializer name=links
src
);
%
/content
/page
- Original Message -
From: yuryx [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 08, 2002 9:46 AM
Subject: Re: JSPGenerator encoding problem
Thanx for ideas ,Vadim.
But I can't undestand how declare JSP encoding.
instead of %out.println(?xml version='1.0
Hello,
In order to try to understand cocoon, I am currentlyplayingwith the
"SamplesForms"examples :
When I add a new employee with the name "André
Testeur" , the
database packagesend it with the wrong
char encoding to the db
In order to correct this I patched
, December 12, 2001 6:33
PM
Subject: RE: urgent encoding
problem...
erm... that code snipple was from the XMLSerializer,
not the HTMLSerializer as i wrote, but the approach should be the same..
sorry!
mvh
karl øie
-Original Message-From: Karl Øie
[mailto
Hello from a new XSP user.
I ask advice and suggestions on how to get dynamic
content in UTF-8 encoding correctly through XSP. I am using Cocoon 1.8.2 with
Tomcat 3.2.3 and Apache 1.3.14, running on Suse Linux 7.1.
I have made an xsp:pagesearch
pagethat retrieves data from the dbXML
To: [EMAIL PROTECTED]
Sent: Tuesday, December 11, 2001 1:31
PM
Subject: urgent encoding problem...
Hi all,
I
have some problems with the xsp pages and encoding. When i try to display
Shift_JIS encoded characters it is not displaying properly.
when i hard code
sember 2001
12:48To: [EMAIL PROTECTED]Subject: Re: urgent
encoding problem...
Hi all,
First of all i thank everybody for not
bothering to reply. I corrected the second and the third problem. If the list
is still alive and anyone cares to give me solution for thefirst
proble
] ; Arun.N
Sent: Wednesday, December 12, 2001 5:44
PM
Subject: RE: urgent encoding
problem...
it's
not that people don't bother to answer you but a lot of people here don't have
any experience with shift-jis encoding. as a Norwegian I have the same
problem, non Scandinavians can
: urgent encoding
problem...
the
increasing page size does not concern me (:-) because the serializer should
write directly to the response.getPrintWriter(). Then again, the serializer
does not flush before the end of the page, so users must wait till the page is
finished.
when
Hi all,
I have
some problems with the xsp pages and encoding. When i try to display Shift_JIS
encoded characters it is not displaying properly.
when i hard code the japnese
characters it is working properly. for example in this xsp page
?xml version="1.0"
encoding="Shift_JIS"?
83 matches
Mail list logo
