That's true, native2ascii is unnecessarily any more. Try to locate the issue whether it is caused at server side or by html page encoding. What's that value in tapestry page.java level? If it is correct, then this should be the html encoding problem. 2008/12/4 Thiago H. de Paula Figueiredo <[EMAIL PROTECTED]>
> Em Wed, 03 Dec 2008 14:58:39 -0300, Imants Firsts <[EMAIL PROTECTED]> > escreveu: > > Hi Ray! >> >> The properties files should be in ascii encoding and the unicode >> characters should be escaped with \u, for example "\u0161" for š >> character. JDK comes with native2ascii tool that does the conversion. >> > > That's not correct anymore. Since some Tapestry version I don't recall, the > property files need to be UTF-8 encoded, so no conversion needs to be done. > > From http://tapestry.apache.org/tapestry5/guide/localization.html: > > "Properties File Charset > > Tapestry uses the UTF-8 charset when reading the properties files in a > message catalog. This means that you don't have to use the Java native2ascii > tool." > > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > Consultor, desenvolvedor e instrutor em Java > http://www.arsmachina.com.br/thiago > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
