uzi wrote:
> i liked this article regarding encoding:
> http://java.sun.com/developer/technicalArticles/Intl/HTTPCharset/index.html
Thanks for the hint. Looks nice.
Cheers,
Heinz
-
To start a new topic, e-mail: users@tomc
Georg Sauer-Limbach wrote:
>> I do not think it is very obvious, that the response class is writing
>> the characters using the platform's default encoding in this case
>
> Yes. And this is true for many, many places in the
> Java library. Always watch out if you see some
> String being processed
Georg Sauer-Limbach wrote:
the question is: How do you create the output of
the servlet, that is, with which Writer or OutputStream.
yes you're right: I simply used the output stream.
But if you just obtain the output byte stream of the servlet,
ie by calling
OutputStream outputStream = res
Markus Schönhaber wrote:
... ServletOutputStream is "suitable for writing binary data in the
response" as the docs say. If you want to transmit textual data, use
HttpServletResponse#getWriter() (see my question above).
yes, this really is a point, Georg's answer already pointed me to the
right d
Markus Schönhaber wrote:
> Works fine for me.
Well, that is really a surprise for me. I tried this in 3 different
operating systems and it was consequently wrong.
> You do call response#setContentType before response#getWriter, don't you?
> There's no filter changing things?
Well, the code is m
[EMAIL PROTECTED] wrote:
> , etc.) just some German special characters (ä ö ü).
sorry for that encoding problem, it should read ä ö ü. I first sent the
message using a different mail address. Then I got a response from the
list server, that I'm not allowed to send messages to this list and
afte
Hi all,
I noticed some encoding problems inside servlets, when switching from
Tomcat 5.5.20 to Tomcat 6.0.10. I looked for it in the mailing lists,
but didn't find something appropriate.
Scenario:
An own servlet (that is: a class derived from HttpServlet) is creating
very simple HTML output, con
