«

I'm having this encoding issue that drives me nuts.

Basically there's a form:

<%@page contentType="text/html" pageEncoding="UTF-8"%>
(...)
head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
</head>
(...)
<h1> Header: š ć đ � <h1>
<% out.println("Print: " + request.getParameter("txtArea")); %>
<form method="post" action="newjsp.jsp">
<textarea name="txtArea">š ć đ �</textarea>
<input type="submit" value="Submit"/>
</form>
--
1) When i press submit it prints out " Å¡ ć đ Ä� "
2) If I change encoding from UTF-8 to Windows-1250, I get lots of
question marks: ? ? ? ?
3) If i change encoding from UTF-8 to iso-8859-1, the data prints ok,
but <h1> Header: š ć đ � <h1> becomes <h1> Header: ? ? ? ? <h1>
4) If I change method to GET with utf-8 encoding everything's fine

p.s. "š ć đ �" are croatian letters

On Apr 27, 5:21*pm, Live DVB <live...@gmail.com> wrote:
> /cut

Well in the end, after few more hours of work I changed URIEncoding to
"windows-1250" at my server.xml, also changed all utf-8 to
windows-1250. I then changed the letters with their ascii(hex?)
counterparts č etc. I guess that's it.

On 27-04-2010 11:21, Live DVB wrote:
> I'm having this encoding issue that drives me nuts.
>
> Basically there's a form:
>
> <%@page contentType="text/html" pageEncoding="UTF-8"%>
> (...)
> head>
> <meta http-equiv="Content-Type" content="text/html;
> charset=UTF-8">
> </head>
> (...)
> <h1> Header: š ć đ �<h1>
> <% out.println("Print: " + request.getParameter("txtArea")); %>
> <form method="post" action="newjsp.jsp">
> <textarea name="txtArea">š ć đ �</textarea>
> <input type="submit" value="Submit"/>
> </form>
> --
> 1) When i press submit it prints out " Å¡ ć đ Ä� "
> 2) If I change encoding from UTF-8 to Windows-1250, I get lots of
> question marks: ? ? ? ?
> 3) If i change encoding from UTF-8 to iso-8859-1, the data prints ok,
> but<h1> Header: š ć đ �<h1> becomes<h1> Header: ? ? ? ?<h1>
> 4) If I change method to GET with utf-8 encoding everything's fine
>
> p.s. "š ć đ �" are croatian letters

If you are consistent (labeling and actual content match), then
all encodings supported by the browser and server should work
fine.

To get it working with ISO-8859-1 / Windows-1250 I think you
need to save the file in that encoding instead if the UTF-8 it
apparently is saved in.

The first problem indicates is a bit more tricky. Somewhere
some UTF-8 is being interpreted as ISO-8859-1 / Windows-1250.
Default charset in Java maybe.

Arne

On 27-04-2010 16:49, Live DVB wrote:
> On Apr 27, 5:21 pm, Live DVB<live...@gmail.com> wrote:
>> /cut
>
> Well in the end, after few more hours of work I changed URIEncoding to
> "windows-1250" at my server.xml, also changed all utf-8 to
> windows-1250.

That seems all fine.

> I then changed the letters with their ascii(hex?)
> counterpartsč etc. I guess that's it.

That is a poor hack.

You could most likely have fixed the last problem by
just saving the file in windows-1250.

Arne

On Apr 28, 2:46*am, Arne Vajhøj <a...@vajhoej.dk> wrote:
> That is a poor hack.
>
> You could most likely have fixed the last problem by
> just saving the file in windows-1250.
>

Well you're correct of course, it's not really a good solution,
however, changing the encoding on project properties didn't solve the
problem. I'm not sure of some other way to do this (I'm using
Netbeans).

Live DVB <> writes:

> Well in the end, after few more hours of work I changed URIEncoding to
> "windows-1250" at my server.xml, also changed all utf-8 to
> windows-1250. I then changed the letters with their ascii(hex?)

BAD change. You should use ISO-8859-1 instead, it's a universal standard
unlike windows-anything.

--
Jukka Lahtinen

Jukka Lahtinen wrote:
> Live DVB <> writes:
>
>> Well in the end, after few more hours of work I changed URIEncoding to
>> "windows-1250" at my server.xml, also changed all utf-8 to
>> windows-1250. I then changed the letters with their ascii(hex?)
>
> BAD change. You should use ISO-8859-1 instead, it's a universal standard
> unlike windows-anything.
>
ISO-8859-1 doesn't work for all European languages. There are other
ISO-8859-? variants.

Lars Enderin <> writes:
> Jukka Lahtinen wrote:
>> Live DVB <> writes:

>>> Well in the end, after few more hours of work I changed URIEncoding to
>>> "windows-1250" at my server.xml, also changed all utf-8 to
>>> windows-1250. I then changed the letters with their ascii(hex?)

>> BAD change. You should use ISO-8859-1 instead, it's a universal standard
>> unlike windows-anything.

> ISO-8859-1 doesn't work for all European languages. There are other
> ISO-8859-? variants.

Sorry, I forgot that, always using iso-8859-1 myself when writing
Finnish. (Does windows-1250 support some languages not supported in
iso-8859-1?)

Anyway, my point was that windows-1250 is platform-specific, meant only
for M$ systems, while iso standards are platform-independent and
universally standardized.

--
Jukka Lahtinen

bugbear <bugbear@trim_papermule.co.uk_trim> writes:

> I'm confused. In 2010, coding a website under Java, why
> would anyone use anything other than utf-8, giving
> full Unicode support?

To avoid multibyte encoding. It makes file sizes and string lengths
confusing and there are editors and other software that don't support
it.

--
Jukka Lahtinen

On 28/04/2010 09:06, bugbear wrote:
> Lars Enderin wrote:
>> Jukka Lahtinen wrote:
>>> Live DVB <> writes:
>>>
>>>> Well in the end, after few more hours of work I changed URIEncoding to
>>>> "windows-1250" at my server.xml, also changed all utf-8 to
>>>> windows-1250. I then changed the letters with their ascii(hex?)
>>> BAD change. You should use ISO-8859-1 instead, it's a universal standard
>>> unlike windows-anything.
>>>
>> ISO-8859-1 doesn't work for all European languages. There are other
>> ISO-8859-? variants.
>>
>
> I'm confused. In 2010, coding a website under Java, why
> would anyone use anything other than utf-8, giving
> full Unicode support?

I think the OP tried that and couldn't get it to work.

Surely there is a UTF-8 solution?

--
RGB