I18n and special Characters

537 views
Skip to first unread message

harkon

unread,
Jul 27, 2009, 1:04:03 AM7/27/09
to Google Web Toolkit
Hi!
In my GWT application I used some special Characters like ÄÖÜ etc.
The display does not show them correctly.
I read that this issue is related to different encodings and I used
some other encodings settings in javac option, like UTF8 and
ISOsomething.
But nothing helps. If I give a special Character during runtime in a
dialog this character was stored correctly...

Help me :)

Cheers
Vic

Ian Bambury

unread,
Jul 27, 2009, 4:03:01 PM7/27/09
to Google-We...@googlegroups.com
Set everything to UTF=8

The project (if not the default for Eclipse if that is what you are using).

The class files will not pick this up unless they change and are saved (just putting a space at the end of a line will do)

The HTML index file (<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'/>)

Off the top of my head I think that is all.

Carl Pritchett

unread,
Jul 28, 2009, 8:31:56 PM7/28/09
to Google Web Toolkit
Make sure also that your properties files are set to UTF-8 (right
click in eclipse and set to UTF-8)

On Jul 28, 6:03 am, Ian Bambury <ianbamb...@gmail.com> wrote:
> Set everything to UTF=8
> The project (if not the default for Eclipse if that is what you are using).
>
> The class files will not pick this up unless they change and are saved (just
> putting a space at the end of a line will do)
>
> The HTML index file (<meta http-equiv='Content-Type' content='text/html;
> charset=UTF-8'/>)
>
> Off the top of my head I think that is all.
>
> Ian
>
> http://examples.roughian.com
>
> 2009/7/27 harkon <victor.sauerm...@googlemail.com>

harkon

unread,
Aug 7, 2009, 6:25:03 AM8/7/09
to Google Web Toolkit
Thanx - that solved problem. I formerly wondered why the display
remains in unreadable character - as I registered, that the char set
changing in eclipse changed the characters. Therefore the chars were
unreadable in code :)
Okay, now the next stage:

I use a MySql DB and this one in latin. The view is now in utf8 and
each "umlaut" character in DB appears crippled in the view. And vice
versa. Special characters on the view are persistet crippled.
Okay, this is not a SOOOO critical impact - because the view of those
unreadable chars result in the correct special characters.
I tried to create a table in UTF8 character encoding inserted some
special characters - but still the problem remain.

Some ideas for that?

Cheers
harkon
Reply all
Reply to author
Forward
0 new messages