Re: Encoding problem (UTF-8)

2008-05-16 Thread jgn

Hi. The problem was tomcat's version. On Ubuntu I was using tomcat 5.5
 and on Windows Tomcat 6. I just installed Tomcat 5.5 on Windows too and
 the problem was fixed. Of course you need to put the URIEncoder on the
 connectors of tomcat, add the the parameter -Dfile.encoding=UTF-8 to
 JAVA_OPTS, change the IDE to UTF-8, etc. 
-- 
View this message in context: 
http://www.nabble.com/Encoding-problem-%28UTF-8%29-tp16984643p17275086.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Encoding problem (UTF-8)

2008-04-30 Thread jgn

Hi. I am having a problem with encoding. I was using ISO-8859-1 but the
Autocomplete did not display the right way some characters (accutes) so I
decide to change all to UTF-8 (including the -Dfile.encoding=UTF-8, changing
the editor to UTF-8 and the URIEncoder to the connectors on the server.xml).
The problem with the autocomplete component is already fixed with this
changes, but I am using too the OnEvent component from t5components. The
function on the server side returns a JSONObject but :|, again, there are
problems with some characters (non US-ASCII characters).

I develop in Ubuntu and changing all to UTF-8 fixed both problems, but on
Windows dose not works with the JSONObject. The database is on UTF-8, all
data is saved ok, the only problem I get is when returning data on a
JSONObject.

Any idea ? :|

Thank you.
-- 
View this message in context: 
http://www.nabble.com/Encoding-problem-%28UTF-8%29-tp16984643p16984643.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: Encoding problem (UTF-8)

2008-04-30 Thread Martin Kersten
In Windows the Writer and Reader using CP as default 
encoding/decoding style. Seams like the JSONObject uses such
Writer/reader without setting the format explicitly.

Got the same Issue with JDOM once.

Check your JSONObject.write(...) methods. Where does your 
Writer comes from and what is its character enconding.

Cheers,

Martin (Kersten)

-Ursprüngliche Nachricht-
Von: jgn [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 30. April 2008 16:59
An: users@tapestry.apache.org
Betreff: Encoding problem (UTF-8)


Hi. I am having a problem with encoding. I was using ISO-8859-1 but the 
Autocomplete did not display the right way some characters (accutes) so I 
decide to change all to UTF-8 (including the -Dfile.encoding=UTF-8, changing 
the editor to UTF-8 and the URIEncoder to the connectors on the server.xml).
The problem with the autocomplete component is already fixed with this changes, 
but I am using too the OnEvent component from t5components. The function on the 
server side returns a JSONObject but :|, again, there are problems with some 
characters (non US-ASCII characters).

I develop in Ubuntu and changing all to UTF-8 fixed both problems, but on 
Windows dose not works with the JSONObject. The database is on UTF-8, all data 
is saved ok, the only problem I get is when returning data on a JSONObject.

Any idea ? :|

Thank you.
--
View this message in context: 
http://www.nabble.com/Encoding-problem-%28UTF-8%29-tp16984643p16984643.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
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]



Re: Encoding problem (UTF-8)

2008-04-30 Thread Marcus
Hi,

We're using autocomplete mixin with no problem, maybe this help.

http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding

Marcus


Re: Encoding problem (UTF-8)

2008-04-30 Thread Foror
j I develop in Ubuntu and changing all to UTF-8 fixed both problems, but on
j Windows dose not works with the JSONObject. The database is on UTF-8, all
j data is saved ok, the only problem I get is when returning data on a
j JSONObject.

Some problem with TextStreamResponse (TAPESTRY-2058). Fix it:

class TextStreamResponse ...

  + private String _charset; // charset get from 
_contentType(;charset=UTF-8)
 // or get from tapestry.response-encoding

public InputStream getStream() throws IOException {
   - return new ByteArrayInputStream(_text.getBytes());
   + return new ByteArrayInputStream(_text.getBytes(_charset));
}

...

return new TextStreamResponse(application/json, jsonObject.toString());


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]