Re: problem with character encoding
thx now it is working On 23 Mrz., 09:47, Thomas Broyer t.bro...@gmail.com wrote: On Wednesday, March 23, 2011 7:10:00 AM UTC+1, tanteanni wrote: thx for your investigation, i'll try it with chnaged encoding of propery-file (at the moment i load it via Properties.load.getresourceasstream(file)). but is there a way to let my code let the reencoding, so that properties-file could be utf-8? Just wrap the InputStream returned from getResourceAsStream within an InputStreamReader, specifying the UTF-8 encoding; and thus use the load(Reader) overload of Properties instead of the load(InputStream) one. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: problem with character encoding
thx for your investigation,
i'll try it with chnaged encoding of propery-file (at the moment i
load it via Properties.load.getresourceasstream(file)). but is there a
way to let my code let the reencoding, so that properties-file could
be utf-8?
('til now i thought that all java encoding is utf-x by default :-|)
On 22 Mrz., 18:26, Thomas Broyer t.bro...@gmail.com wrote:
If you use the
java.util.Propertieshttp://download.oracle.com/javase/6/docs/api/java/util/Properties.htmlclass
to read from your properties file, depending on how you load the
properties, the file should be encoded in ISO-8859-1:
The
load(Reader)http://download.oracle.com/javase/6/docs/api/java/util/Properties.htm...)
/ store(Writer,
String)http://download.oracle.com/javase/6/docs/api/java/util/Properties.htm...,
java.lang.String) methods load and store properties from and to a character
based stream in a simple line-oriented format specified below. The
load(InputStream)http://download.oracle.com/javase/6/docs/api/java/util/Properties.htm...)
/ store(OutputStream,
String)http://download.oracle.com/javase/6/docs/api/java/util/Properties.htm...,
java.lang.String) methods work the same way as the
load(Reader)/store(Writer, String) pair, except the input/output stream is
encoded in ISO 8859-1 character encoding.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: problem with character encoding
On Wednesday, March 23, 2011 7:10:00 AM UTC+1, tanteanni wrote: thx for your investigation, i'll try it with chnaged encoding of propery-file (at the moment i load it via Properties.load.getresourceasstream(file)). but is there a way to let my code let the reencoding, so that properties-file could be utf-8? Just wrap the InputStream returned from getResourceAsStream within an InputStreamReader, specifying the UTF-8 encoding; and thus use the load(Reader) overload of Properties instead of the load(InputStream) one. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: problem with character encoding
Hi, is the application deployed on a tomcat? If so, then check the server.xml configuration and especially the conncetor URI encoding definition. HTH, Lukasz On 22 Mrz., 12:32, tanteanni tantea...@hotmail.com wrote: i made a very simple sandbox gwt-app to get familiar with rpc and integrating third-party libraries. this sandbox app simply references a library that offers one service: returning a string read from a property-file within the referenced jar. the problem is the encoding seem to be wrong - special characters are being scrambled (in my case german umlauts). but why? all seem to be set to utf-8: my hole eclipse-workspace including the properties-file read from and the sandbox.html begins with: meta http-equiv=content-type content=text/html; charset=UTF-8 so what could scramble the characters? where to look for wrong encodeing? thx in advance -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: problem with character encoding
no at the moment i only used the integrated jetty in development mode. how to configure jetty? where is gwt-delivered-jetty located? On 22 Mrz., 16:30, Lukasz l.plotni...@googlemail.com wrote: Hi, is the application deployed on a tomcat? If so, then check the server.xml configuration and especially the conncetor URI encoding definition. HTH, Lukasz On 22 Mrz., 12:32, tanteanni tantea...@hotmail.com wrote: i made a very simple sandbox gwt-app to get familiar with rpc and integrating third-party libraries. this sandbox app simply references a library that offers one service: returning a string read from a property-file within the referenced jar. the problem is the encoding seem to be wrong - special characters are being scrambled (in my case german umlauts). but why? all seem to be set to utf-8: my hole eclipse-workspace including the properties-file read from and the sandbox.html begins with: meta http-equiv=content-type content=text/html; charset=UTF-8 so what could scramble the characters? where to look for wrong encodeing? thx in advance -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: problem with character encoding
If you use the java.util.Propertieshttp://download.oracle.com/javase/6/docs/api/java/util/Properties.htmlclass to read from your properties file, depending on how you load the properties, the file should be encoded in ISO-8859-1: The load(Reader)http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#load(java.io.Reader) / store(Writer, String)http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#store(java.io.Writer, java.lang.String) methods load and store properties from and to a character based stream in a simple line-oriented format specified below. The load(InputStream)http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#load(java.io.InputStream) / store(OutputStream, String)http://download.oracle.com/javase/6/docs/api/java/util/Properties.html#store(java.io.OutputStream, java.lang.String) methods work the same way as the load(Reader)/store(Writer, String) pair, except the input/output stream is encoded in ISO 8859-1 character encoding. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
