[jomanda]

Hi! i have a problem. if i reply the string to the browser without any changes, it does not work. what is that?
BUT, if i do the getBytes() trick, and i store and read it from db, it does display correctly

[ovigo22]

Did you check the encoding of the string you get back from the database?
Also, I thought strings were always UTF-16

[Kopilman]

Unless otherwise specified.

[jomanda]

i think, that db read/write trick helps only as conversion from byte[] to String all my db communication seem to be iso-8859-2, and i see no problems with it

[PaulKolin]

Strings in java memory are always utf-16

[ovigo22]

But if you create one with another encoding from bytes, doesn't it transcode it to UTF-16 in memory?

[Kopilman]

Yes...
But who cares how it's stored?

[ovigo22]

So if you create a string by passing bytes and the appropriate encoding, then do .getBytes() won't that return the UTF-16 bytes?

[Kopilman]

Booleans could be stored as 32-bit values.

[ovigo22]

Or does it return the original?

[Kopilman]

ovigo22, no, it'll transcribe it to the encoding specified.

[PaulKolin]

ovigo22, getBytes(String encoding)

[ovigo22]

Kopilman, you're certain of that?

[Kopilman]

ovigo22, Yes. I am.

[jomanda]

ovigo22, .getBytes() without parameters switches to the system defaults

[ovigo22]

Ok
System default
But not the one used when creating the string

[jomanda]

In my case it seems to

[Kopilman]

Nope.
Well, it could be, it's just not guarenteed to be.

[ovigo22]

Right, which means it's not
It has no relevance, but could coincidentally be the same (obviously)
jomanda, you should look at the tomcat source code to see how it's encoding the strings
Maybe it's doing it incorrectly
Or differently than seems appropriate or correct

[jomanda]

I think, that the chances are that i am doing something wrong
Btw. i am not able to enforce browser to specify iso-8859-2 on post

[ovigo22]

Yes but at least you would have some insight instead of relying on simply an imaginary contract for what to deal with

[PaulKolin]

jomanda, we still have not seen any test case...

[jomanda]

I tried <form enctype="...">, but it does not work

[ovigo22]

jomanda, enctype isn't for the encoding, but for the post data format
I.e. application/x-form-urlencoded vs. whatever else
You have to specify a non-default for say, file uploads

[jomanda]

Any idea how to enforce encoding for post, then?