-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Тимур,

Let's start over again: you are providing WAY too much extra
information all at once. We don't need to see your web.xml file. We
don't need to see your HTML files. I looked at your "comparison" but
there was no indication of where the files were different. I can read
neither Russian nor Kazakh. What you do need to do is answer the
questions we are asking to try to help you.

Please answer this simple question:

If the data is correctly-stored in the database (as verified by some
other means), does the fetched-data display correctly in your web pages?

If it's not displaying correctly, please tell us what the Content-Type
HTTP response header is for the page (specifically, the character
encoding). Also, please tell us what the character encoding is for the
/database connection/ to Oracle (the one made from your application to
Oracle).

Finally, how are you connecting to Oracle? Are you using a
Tomcat-configured DataSource or is your web application configuring
things on its own?

I can see that when you attempt to use user.language=ru and
user.country=kz, you get this error from Oracle's driver:

> org.apache.catalina.core.ApplicationContext log MESSAGE =
> ORA-00604: error occurred at recursive SQL level 1 ORA-12705:
> invalid or unknown NLS parameter value specified , ERRORCODE = 604

Can you give us the whole stack trace from that?

It's clear from that error that the default localization settings are
being used to make the database connection. You may have to override
them in order to force the use of the CL8MSWIN1251 code page in the
driver. If the driver is using the correct character encoding, then
Java should get the correct String value. Generating a web page
containing the proper characters should be trivial: just make sure you
send the proper character encoding to the client in your Content-Type
response header.

After you get character-display working, we can tacking character
*input* which is more complicated. Let's make sure we can get data
out, first. Otherwise, you'll never know if you can get the data *in*
correctly.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS2FsDAAoJEBzwKT+lPKRYu84QALcPPMlvjL6RIMoOL4mFOARa
tq8sQXRPt7zWEI0N+dGcmJyvPnAPnvqjWhOsvVSgOd74W/GYXnJ7iw00d/ETW8qK
wlIeLwBAeeHvC5qIPAJUVuMAq4YAIK11+eofKdRM67GuHy8QCK8xAh80E574uwcs
X6zl1/C3jFec2jz0CQskz6YBEAjBK82h9sgZrfNcR+5QOuzqU8bH6CgHLwdJyLiP
2stBT5TJTIHhvUVlB+249GL75fdZHgv4122G8D+mZcpKJkRN44ZlKZF24CrXuPzv
2fhmfShoGLa4ylJM7ZgQy0jnqjuuxYmJGSLRviH69Gtd6xk5ha9lcTXwmME0Z/Qt
C5krjLumfVariSdspNvqvaLWjMAGh7gEMzOyp/wzy3GVXdABwwZEDC00ENt3CxzO
5R2pdxHaXr53THufxbJMc7YzX+ZtV2kMh2FfNR5cW1UY9ABF9Ljx/z2qjcMqWINK
o0edm4VpEVNeg5ms6nvoI1o6cjfaheDfRMaeRoXCbp/uC6JfH/l+p5RF0Vcuhe/h
aVZ9yd6LYY1EmHjEypHmBaXQSKVfdEZUfz60Xm5SZn2GdCyh9QRbVW1vN0+v1gto
c5v7TcwazpY+1ZM25qcPB307/o+73qqJGJlGq4PnnskOLKIelcJ7XCGi9WypQbRw
VvEP9yTXdeX53JQ6R2ij
=dFj8
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to