Hi Lenart
thanks for replying and the input about encoding the properties files!
Unfortunately encoding the properties file will only solve the problem
partially:
Some texts in selects do come from a database and will still get
scrambled...
...but you are probably already aware of that ;-)
Thanks!
Markus
Am 22.11.2012 11:17, schrieb Łukasz Lenart:
2012/11/22 [email protected] <[email protected]>:
I experience some problems with umlauts after upgrading from Struts 2.3.4.1
to 2.3.7:
Text with umlauts like 'ä' from properties files get scrambled in the JSPs,
selects and submit buttons.
file -i shows that properties file are encoded as as iso-8859-1. which they
should be, as far as I know.
Recoding the properties files to UTF-8 actually resolves the problem for the
JSPs. But within the selects and submit buttons the problem persists.
Adding acceptcharset="utf-8" to the forms does not help.
This behaviour is new since version 2.3.7. Do I miss something from my part
or is this a bug newly introduced.
I use tiles and have set in the JSPs
<%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%>
and
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Tomcat 7 is running with URIEncoding="UTF-8"
Markus Fischer
You are right, but all the entities should be encoded in properties
file. Eclipse and IDEA allows you to encode them in fly. In IDEA it
is:
Settings -> File Encodings -> Transparent native-to-ascii conversion checkbox
So when you open your property file with a text editor you should see
something like 0xfc instead ü
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
