On Fri, 2003-06-06 at 23:59, morten svanæs wrote:
> - Original Message -
> From: "morten svanæs" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 2:53 PM
> Subject: Re: Encoding problems in flowscript
>
>
> >
- Original Message -
From: "morten svanæs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 2:53 PM
Subject: Re: Encoding problems in flowscript
>
> - Original Message -
> From: "Bruno Dumon" <[EMAIL PROTECTE
- Original Message -
From: "Bruno Dumon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 5:37 AM
Subject: Re: Encoding problems in flowscript
> On Fri, 2003-06-06 at 22:56, morten svanæs wrote:
> > Hi,
> > I'm having
i have the same problem posting data from a form to .xsp
there is a thread about this
http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=105396439703871&w=2
--stavros
On 6 Jun 2003, Bruno Dumon wrote:
> On Fri, 2003-06-06 at 22:56, morten svanζs wrote:
> > Hi,
> > I'm having trouble with th
On Fri, 2003-06-06 at 22:56, morten svanæs wrote:
> Hi,
> I'm having trouble with the enconding in a flowscript, when
> I submit data in a form it gets escaped internaly in the flow
> script, so if I try to get back data that has some norwegian
> characters in them they get misinterpreted. All my d
Hello Tim,
Tim Cavanagh wrote:
Hi,
I am putting in some text from MS word through our publishing system that
includes MS curly quotes (8-bit) when it gets to cocoon to be parsed via
XSLT I get an error. The error is caused by the the thorn element being
placed in the text (unclosed). Our publishi
r all the locales used there.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 25, 2003 17:24
Subject: RE: Encoding problems
In the doc it's written about setting this in web.xml :
form-encoding
utf-8
But it doesn't
In the doc it's written about setting this in web.xml :
form-encoding
utf-8
But it doesn't change anything with cocoon 2.0!
-Original Message-
From: Konstantin Piroumian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 2:55 PM
To: [EMAIL PROTECTED]
Subject: Re
[EMAIL PROTECTED]
Subject: Re: Encoding problems
On Tue, 25 Mar 2003 14:12:59 +0100
<[EMAIL PROTECTED]> wrote:
> Hi,
> I have xsp pages, and all my parameters with accents (И, Х, Т,...) changes
into things like "ц╘",...
> I tried diferent encoding into my pages (like ), but n
Is there no other way to keep my french caracter set from page to page (because I have
to many pages and some request are xsp-request)
Tanks
-Original Message-
From: Yury Mikhienko [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 2:20 PM
To: [EMAIL PROTECTED]
Subject: Re
On Tue, 25 Mar 2003 14:12:59 +0100
<[EMAIL PROTECTED]> wrote:
> Hi,
> I have xsp pages, and all my parameters with accents (И, Х, Т,...) changes into
> things like "ц╘",...
> I tried diferent encoding into my pages (like encoding="ISO-8859-1"?>), but nothing seems to work!
> how can I keep the
> > But it seems setting only charset attribute in html tag and not
> > infuencing
> > http header.
> >
> > Artur
>
> Use action org.apache.cocoon.acting.SetCharacterEncodingAction
>
Not helping either. The Content-Type header contains no information about
encoding.
Artur
On Fri, 28 Feb 2003 12:36:00 +0100, arturl <[EMAIL PROTECTED]> wrote:
But it seems setting only charset attribute in html tag and not
infuencing
http header.
Artur
Use action org.apache.cocoon.acting.SetCharacterEncodingAction
Regards
But it seems setting only charset attribute in html tag and not
infuencing
http header.
Artur
- Original Message -
From: "BOCEK Michal" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 12:15 PM
Subject: RE: encoding
> Hi
> this f
Hi
this feature set in sitema.xmap on serializers.
1024
-//W3C//DTD HTML 4.0 Transitional//EN
windows-1250
Michal
-Original Message-
From: arturl [mailto:[EMAIL PROTECTED]
Sent: Friday, February 28, 2003 12:22 PM
To: [EMAIL PROTECTED]
Subject: encoding
Hello,
What component (
ginal 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 from 14 May 2002. This doesn't have
this action yet. I'll check a recent build and try that.Do you
mea
I'm using a build from 14 May 2002. This doesn't have this action
yet. I'll check a recent build and try that.
Do you mean that I need to add this action at the beginning of EVERY pipeline?
Bert
At 16:55 25/10/2002 +0200, you wrote:
hy Bert,
we had this problem too.
look, if the map:actions s
hy Bert,
we had this problem too.
look, if the map:actions section contains
following:
and at the beginning of a pipeline
That should work.
Boris
- Original Message -
From:
Bert Van Kets
To: [EMAIL PROTECTED]
Sent: Friday, October 25, 2002 1:39
P
Try this in your sitemap:
and
--- Stefan Riegel <[EMAIL PROTECTED]> wrote:
> 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-file
--- 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 anothe
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
>>>questio
--- Vadim Gritsenko <[EMAIL PROTECTED]>
wrote:
> Alex Romayev wrote:
>
> >--- Vadim Gritsenko <[EMAIL PROTECTED]>
> >wrote:
> >
> >
> >>Alex Romayev wrote:
> >>
> >>
> >>
> >>>--- Vadim Gritsenko <[EMAIL PROTECTED]>
> >>>wrote:
> >>>
> >>>
> >>>
> >>>
> Alex Romayev wrote:
> >>>
Alex Romayev wrote:
>--- Vadim Gritsenko <[EMAIL PROTECTED]>
>wrote:
>
>
>>Alex Romayev wrote:
>>
>>
>>
>>>--- Vadim Gritsenko <[EMAIL PROTECTED]>
>>>wrote:
>>>
>>>
>>>
>>>
Alex Romayev wrote:
>Let me be more specific and also simplify the
--- Vadim Gritsenko <[EMAIL PROTECTED]>
wrote:
> Alex Romayev wrote:
>
> >--- Vadim Gritsenko <[EMAIL PROTECTED]>
> >wrote:
> >
> >
> >>Alex Romayev wrote:
> >>
> >>
> >>
> >>>Let me be more specific and also simplify the
> >>>
> >>>
> >>example:
> >>
> >>
> >>...
> >>
> >>
>
Alex Romayev wrote:
>--- Vadim Gritsenko <[EMAIL PROTECTED]>
>wrote:
>
>
>>Alex Romayev wrote:
>>
>>
>>
>>>Let me be more specific and also simplify the
>>>
>>>
>>example:
>>
>>
>>...
>>
>>
>>
>>>Does not work:
>>>
>>>
>>>
>>>
>>>
>>Are these funny characters above in UT
On Wednesday 18 September 2002 13:53, Alex Romayev wrote:
> Let me be more specific and also simplify the example:
>
> Works:
>
>
>
> ...
>
> select="$city"/>
>
> After transformation I get:
> Delhi
>
> Does not work:
>
>
>
> ...
>
> select="$city"/>
>
> After transformation I get:
> href="ci
--- Vadim Gritsenko <[EMAIL PROTECTED]>
wrote:
> Alex Romayev wrote:
>
> >Let me be more specific and also simplify the
> example:
> >
> ...
>
> >Does not work:
> >
> >
> >
>
> Are these funny characters above in UTF-8? Does your
> XSL has
> encoding="UTF-8" on the top?
Yes. Also, note that
Alex Romayev wrote:
>Let me be more specific and also simplify the example:
>
...
>Does not work:
>
>
>
Are these funny characters above in UTF-8? Does your XSL has
encoding="UTF-8" on the top?
>...
>
>select="$city"/>
>
>After transformation I get:
>href="city-detail=%D0%94%D0%B5%D0%BB%D0%B
utf-8
>
> - 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
&g
maybe :
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
> Let me be more speci
Let me be more specific and also simplify the example:
Works:
...
After transformation I get:
Delhi
Does not work:
...
After transformation I get:
Äåëè
--- Alex Romayev <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm having what seems to be an encoding problem --
> not
> sure it's rel
Hiloliddin Karimov wrote:
> Hi All,
>
>
>
> I try retrieve column that have cyrillic letters by ESQL:
>
>
>
>
>
>
> ...
>
>
>
> SELECT username FROM users
>
> WHERE fname LIKE %name="fname"/>%
>
>
>
> ...
>
try
or
String param=new
String(request.getParameter("text1").getByte
- 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 v
- Original Message -
From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 12, 2002 5:05 PM
Subject: RE: encoding problem with xslt
> > Thanks for you input Vadim. But do not only think of web sites. But
> > also o
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 som
> 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
>
>
- 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
- 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 so
> 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
> From: Jens Lorenz [mailto:[EMAIL PROTECTED]]
>
...
> If anyone has some more ideas on this topic (non-ISO-8859-1 characters
> within URIs), I would greatly appreciate some more input.
IMHO, non-ascii characters in URIs should be avoided by all means
possible.
Less issues for you *and* for vi
- Original Message -
From: "thorsten schmid" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 12, 2002 2:17 PM
Subject: encoding problem with xslt
Hi Thorsten,
>
> output:
>
> Integ
> 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 ä
> is not valid,
> the & is reserved for concatenating request parameters.
My apologies, I should have read the me
Manos Batsis wrote:
>>From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
>>>
>>>desired output:
>>href="frameset.xsp?filename=foo.xml&searchstring=Integrations&
>>auml;mter">
>>
>>>Integrationsämter
>>> .
>>>
> From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
> >
> > desired output:
> > href="frameset.xsp?filename=foo.xml&searchstring=Integrations&
> auml;mter">
> > Integrationsämter
> >.
> > ==
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.
>
>
>
> frameset.xsp?filename= select="@sourcefile"/>&searchstring= disable-output-escaping="yes" select="."/>
>
>
>
>
>
You can remove
> From: Gerhard Hipfinger [mailto:[EMAIL PROTECTED]]
>
> Hi!
>
> I know this question was asked a month ago, but the thread ended
without
> a real solution to the problem.
>
> The problem in short:
> Form data with special chars (i. e. german umlauts) is not encoded
> correctly in the FormValid
Hi,
thank you all for your help. You have all been right and
it works fine now ;-)
I am just wondering, is there some more documentation on
the sitemap.xmap, when to use what element with what
consequences?
Thanks, Heike
-
Plea
Hi Heike,
I use these declarations in my sitemap :
iso-8859-1
iso-8859-1
and it's all perfect.
Matthieu
> -Message d'origine-
> De : Franosch, Heike [mailto:[EMAIL PROTECTED]]
> Envoyé : mardi 16 avril 2002 18:33
> Objet : Encoding question
>
>
> Hi all,
>
> is
> From: Franosch, Heike [mailto:[EMAIL PROTECTED]]
>
> Hi all,
>
> is it possible to set the output encoding?
Yes
> I always get a UTF-8, even if I set output encoding to iso-8859-1
> in my stylesheet.
Don't do this.
> Can I influence it somehow in the sitemap?
Yes. Have you seen sample sit
On Tue, 16 Apr 2002, Franosch, Heike wrote:
> Hi all,
>
> is it possible to set the output encoding?
> I always get a UTF-8, even if I set output encoding to iso-8859-1
> in my stylesheet. Can I influence it somehow in the sitemap?
>
Try
ASCII
---
> From: Andrey Demchenko [mailto:[EMAIL PROTECTED]]
>
> Hi, Vadim.
>
> - Original Message -
> From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
>
> > > 2) How can I put "-encoding KOI8-R" to javac
> > > in servlet container e.g. Resin 2.0.5, Tomcat 4.0?
>
> > You can change encoding for
Hi, Vadim.
- Original Message -
From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
> > 2) How can I put "-encoding KOI8-R" to javac
> > in servlet container e.g. Resin 2.0.5, Tomcat 4.0?
> You can change encoding for the whole JVM right now
May be this is offtopic but I do not know
how
> From: Andrey Demchenko [mailto:[EMAIL PROTECTED]]
>
> 1)Thanks. It's works in Cocoon 2.0.1 and 2.0.2.
> I use your recomendations and changed in cocoon.xconf
>value="org.apache.cocoon.components.language.programming.java.Javac"/>
> =
> 2) How can I put "-encoding KOI8-R" to ja
1)Thanks. It's works in Cocoon 2.0.1 and 2.0.2.
I use your recomendations and changed in cocoon.xconf
=
2) How can I put "-encoding KOI8-R" to javac
in servlet container e.g. Resin 2.0.5, Tomcat 4.0?
--
Best regards,
Andrey Demchenko.
- Original Message -
From: "Vad
Vadim Gritsenko wrote:
>Ok, I see, you have got national characters in the Java file (I do not have them, may
>be because of different locale).
>
>Next step for you would be:
>1. Switch back to Javac (pizza does not support Java file encoding option)
>2. Make sure Javac gets "-encoding KOI8-R" c
Ok, I see, you have got national characters in the Java file (I do not have them, may
be because of different locale).
Next step for you would be:
1. Switch back to Javac (pizza does not support Java file encoding option)
2. Make sure Javac gets "-encoding KOI8-R" command line option
and everyt
I have "ðÒÉ×ÅÔ" insted of my
russian characters :(
- Original Message -
From:
yuryx
To: [EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 9:29
AM
Subject: Re: Encoding non-english
characters in XSP (C2.0.2)
I fail to see difference. In both case
I fail to see difference. In both cases, in Cocoon 2.0.1 and in Cocoon2.0.2, XSP page with KOI8-R encoding, produces following Java code:this.characters("\n??\n ");
yes, in sample_xsp.java:
this.characters("\n ");
this.contentHandler.startElement(
> From: yuryx [mailto:[EMAIL PROTECTED]]
>
> Hello all
>
> I have the following problem:
> After updating cocoon from version 2.0.1 to 2.0.2
> non-english characters are not normally decoded on page , generated by
XSP .
I fail to see difference. In both cases, in Cocoon 2.0.1 and in Cocoon
2.0
It might be also xerces - 'cause you changed the parser during
installation. Check xerces's support of encodings.
Vadim
> -Original Message-
> From: Sam NewYork [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 28, 2002 5:23 PM
> To: [EMAIL PROTECTED]
> Subj
You are right. Although it only happened after I installed Cocoon2. I'll
check the tomcat mailing list.
Thanks again.
Sam
>From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: RE: encoding "
> From: Sam NewYork [mailto:[EMAIL PROTECTED]]
>
> I recently installed Cocoon2 with JBoss-2.4.3_Tomcat-3.2.3. I
followed all
> the instructions on the installation page which involved removing
parser.jar
> and jaxp.jar and replacing that with xerces-1.4.4.jar
>
> Now when I try to work with my
lt;[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, December 30, 2001 1:36 PM
> Subject: Re: encoding Shift_JIS problem in cocoon 2.0
>
>
> > Hi,
> > Can you sort out when the conversion to ??? chars happens?
> > Knowing this helps to understand
Hi,
Can you sort out when the conversion to ??? chars happens?
Knowing this helps to understand who is guilty, the xsp-generator, the
transformer, or the serializer
1) Try to remove the xsp step delivering the xml as-is via cocoon
2) Do you use a transformer step?
bye bernhard
Priya Padate wrot
On Friday 28 December 2001 12:04, Cocoon User wrote:
> i recieve pages in Unicode format
> how can a change this i want iso-8859-7
I think you need to configure an additional xml serializer with the
iso-8859-7 encoding, AFAIK the encoding settings in XSL transforms are
ignored.
Here's an examp
Kounis,
try modifying the sitemap.xmap element, by changing the
output enconding to the one you prefer, like in:
iso-8859-7
Best regards,
-
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://
antos
-Mensagem original-
De: Max Larsson [mailto:[EMAIL PROTECTED]]
Enviada: quarta-feira, 28 de Novembro de 2001 7:49
Para: [EMAIL PROTECTED]
Assunto: RE: Encoding
Hi,
thnaks it works at least more than ever, but
still some issues are open. First why does it
work when changing the encoding o
serializer encoding to UTF-8
does than even japanese characters get stored
correctly ??
Max
> -Original Message-
> From: Nuno José Pires dos Santos [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 27. November 2001 16:36
> To: [EMAIL PROTECTED]
> Subject: RE: Encoding
>
>
Try this
ISO-8859-1
-Mensagem original-
De: Max Larsson [mailto:[EMAIL PROTECTED]]
Enviada: terça-feira, 27 de Novembro de 2001 11:28
Para: 'Cocoon Users'
Assunto: Encoding
Hi,
i am testing the employee example, which is
contained with C2 distribution and accessib
69 matches
Mail list logo
