Hi Sripathi, thanks for the ideas,
But I added a debug point before setting the string "søgning" to the UiBinder dynamically. The string comes correctly to the debug point and after i set the string to the UiBinder it appears wrong.. That is where i get stuck. I tried both utf-8 and iso-8859-1 character settings in the host page, but the result was same.. Please advice.. Regards, Kahawala On Sat, Mar 13, 2010 at 12:32 PM, Sripathi Krishnan < [email protected]> wrote: > if i use static special characters in the UiBinder it get rendered >> correctly. So i think this happens when loading dynamic data. >> > By dynamic data I assume you mean a RPC call has the data. > > How are you storing the data? If you are using databases, make sure that > you are using the right encoding (UTF-8 is the most popular) in the > database. If there is any code that is doing things like String.getBytes() > or using raw InputStreams, make sure it sets the right character encoding. > > With character encoding, you need to be consistent throughout your > application stack - database through browser. Data usually gets mangled when > passing between two layers - like DB to app, or app to file system, > webserver to browser etc. So, the trick to solve is to look at each layer > interaction one by one. > > > --Sri > http://blog.530geeks.com > > > On 12 March 2010 23:51, venura kahawala <[email protected]> wrote: > >> Hi Thomas >> >> Thanks for the reply. >> >> But i tried the way that you have mentioned and i couldn't get the >> expected results. All my files are encoded with utf-8. >> Any comment is appreciated. >> >> Thanks, >> Kahawala >> >> >> On Fri, Mar 12, 2010 at 8:14 PM, Thomas Broyer <[email protected]>wrote: >> >>> >>> >>> On Mar 12, 2:09 pm, kahawala <[email protected]> wrote: >>> > Hi, >>> > >>> > I have a simple GWT application that uses both Messages and Constant >>> > interfaces to do the internationalization. I want to show danish >>> > special characters like "æ" in my danish version. >>> >>> To make it simple, *all* of your files should be encoded in >>> UTF-8: .java, .properties, .xml and .html >>> And in your .html page, also make sure the browser interprets it as >>> being UTF-8-encoded (browsers have a page encoding menu that shows you >>> which encoding they thought the page was in). It generally is as >>> simple as putting a <meta charset='utf-8'> in the HTML's head (though >>> some server configuration could override it by sending an explicit >>> charset= parameter in the Content-Type HTTP header). >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Web Toolkit" group. >>> To post to this group, send email to [email protected] >>> . >>> To unsubscribe from this group, send email to >>> [email protected]<google-web-toolkit%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-web-toolkit?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-web-toolkit%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
