Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Dan Tran
Take a look at this link
http://www.anassina.com/struts/i18n/i18n.html

It has a section dealing with WS4 without using filter

-D
- Original Message -
From: "Gemes Tibor" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 2:46 AM
Subject: Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding


2003. január 15. 11:32 dátummal Hirschmann, Bernhard ezt írtad:

> I think I have to study this in more detail - it still isn't quite clear
> for me.
> What is this SetCharacterEncoding filter doing? Is it only working with
> Tomcat? (We use WebSphere 4)

I don't know websphere, but if it conforms to the servlet specs v2.3 then it
is.

> I also have unicode characters from the DB which have to be displayed
> correctly. Is this filter good for that?

No. It is for the user submitted data to convert into the proper encoding.

Tib

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

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




Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Giri Alwar
If I am not mistaken, under Servlet 2.3 spec, you can call the
setCharacterEncoding() method on the request and set it to a desired
encoding before reading any parameters from the request. The container is
responsible for providing you with request parameters in the encoding your
specified from this point on. WAS 4.0 does not support the J2EE 1.3 spec (it
supports 1.2.1). You will need WAS 5.0 for this to work. It is working in
Tomcat because the version of Tomcat you have supports J2EE 1.3.

- Original Message -
From: "Gemes Tibor" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 4:46 AM
Subject: Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding


2003. január 15. 11:32 dátummal Hirschmann, Bernhard ezt írtad:

> I think I have to study this in more detail - it still isn't quite clear
> for me.
> What is this SetCharacterEncoding filter doing? Is it only working with
> Tomcat? (We use WebSphere 4)

I don't know websphere, but if it conforms to the servlet specs v2.3 then it
is.

> I also have unicode characters from the DB which have to be displayed
> correctly. Is this filter good for that?

No. It is for the user submitted data to convert into the proper encoding.

Tib

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



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.435 / Virus Database: 244 - Release Date: 1/1/2003

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




Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Gemes Tibor
2003. január 15. 11:32 dátummal Hirschmann, Bernhard ezt írtad:

> I think I have to study this in more detail - it still isn't quite clear
> for me.
> What is this SetCharacterEncoding filter doing? Is it only working with
> Tomcat? (We use WebSphere 4)

I don't know websphere, but if it conforms to the servlet specs v2.3 then it 
is.

> I also have unicode characters from the DB which have to be displayed
> correctly. Is this filter good for that?

No. It is for the user submitted data to convert into the proper encoding.

Tib

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




AW: AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Hirschmann, Bernhard


>> Nothing is wrong with utf-8. Maybe it would be the best to use it, even
>> though everything is much more complex while handling stuff like the html
>> form entries, which have to be converted.

> No, as far as you are using the SetCharacterEncoding filter coming with
the 
> example application of Tomcat.

I think I have to study this in more detail - it still isn't quite clear for
me. 
What is this SetCharacterEncoding filter doing? Is it only working with
Tomcat? (We use WebSphere 4)

I also have unicode characters from the DB which have to be displayed
correctly. Is this filter good for that? 

Bernhard

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




Re: AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Gemes Tibor
2003. január 15. 10:52 dátummal Hirschmann, Bernhard ezt írtad:
> >> The reason is, that I don't want to use utf-8, but ISO-8859-1 for my
> >> html pages. And if a "ü" appears in the ISO-8859-1 characterset in the
>
> browser,
>
> > What is wrong with utf-8?
>
> Nothing is wrong with utf-8. Maybe it would be the best to use it, even
> though everything is much more complex while handling stuff like the html
> form entries, which have to be converted.

No, as far as you are using the SetCharacterEncoding filter coming with the 
example application of Tomcat.

> reports... So I think I better use the ISO-8859-1 character set with html
> characters like "&". It may be stupid, but it eases a lot.

I use iso-8859-2 if I know that each user input is covered in it. However I 
need to use the abovementioned filter in this case too.

Hth,

Tib

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




AW: AW: AW: Transforming a String to valid HTML encoding

2003-01-15 Thread Hirschmann, Bernhard

>> The reason is, that I don't want to use utf-8, but ISO-8859-1 for my html
>> pages. And if a "ü" appears in the ISO-8859-1 characterset in the
browser,

> What is wrong with utf-8?

Nothing is wrong with utf-8. Maybe it would be the best to use it, even
though everything is much more complex while handling stuff like the html
form entries, which have to be converted.

The main reason is that our customer has problems with its application
server configuration when I deliver JSPs in utf-8. I don't know what kind of
problems, because it is not possible for me to check the configuration - it
is a high security area where they run their servers, and there are reasons
why I'm not allowed to check it. I just deliver and get the bug reports...
So I think I better use the ISO-8859-1 character set with html characters
like "&". It may be stupid, but it eases a lot.

Regards
Bernhard

--
To unsubscribe, e-mail:   
For additional commands, e-mail: