Ive tried to update the maven repos with the encoding param but there was still no change, im going to leave it be for a while and come back to it. Thanks again for everyones assistance.
On Thu, Dec 4, 2008 at 10:57 AM, Andy Pahne <[EMAIL PROTECTED]>wrote: > > That's whatI did as well, and it works here. > > Anyway: it also works, when the property files are ISO encoded (ASCII) and > UTF-8 chars are properly escaped. > > Andy > > > > Jakub Vlasak schrieb: > > Hi, >> >> i've had similar problem with slovak character, and I've solved it ba >> adding >> the UTF-8 encoding parameter to the java compiler. >> Edit the pom.xml file, the maven-compiler-plugin like this: >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-compiler-plugin</artifactId> >> <configuration> >> <source>1.5</source> >> <target>1.5</target> >> <optimize>true</optimize> >> *<encoding>UTF-8</encoding>* >> </configuration> >> </plugin> >> >> Hope this will help. >> >> On Thu, Dec 4, 2008 at 10:08 AM, Ray <[EMAIL PROTECTED]> wrote: >> >> >> >>> I've put in logging on the java page when bringing back the message, and >>> its >>> coming out incorrectly with ? instead of the special characters, so its >>> nothing to do with the html I believe. >>> >>> I've since learned that the fact that im using Windows may also be having >>> an >>> effect as it may be saving the file in a format that is unexpected by >>> Tapestry, but im only hedging a guess there really. >>> >>> Thanks for the feedback so far, its been great. >>> >>> >>> >>> >>> On Thu, Dec 4, 2008 at 1:44 AM, dh ning <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>>> 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] >>>>> >>>>> >>>>> >>>>> >>>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
