Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-20 Thread Kovács István
Hi Igor, On 20/03/07, Igor E. Poteryaev <[EMAIL PROTECTED]> wrote: PrintWriter pw = response.getPrintWriter("text/html; charset=UTF-8"); instead of PrintWriter pw = response.getPrintWriter("text/html"); thanks for the suggestion. I had the same thing in mind but have not had time to find the c

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-20 Thread Igor E . Poteryaev
Kovács István gmail.com> writes: > > I've built an application using the quickstart Maven prototype. It all > works fine, but serves the output in ISO-8859-1 (Latin-1), not UTF-8. > Kent Tongs book on Tapestry 4 says "Tapestry always use UTF-8 to > encode the output, regardless the encoding of t

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Istvan Szucs
p! Árvízt?r? kútfúró! Sorry Kofa... it isnt the solution. Best Regards Stef > -Original Message- > From: [EMAIL PROTECTED] > Sent: Mon, 19 Mar 2007 14:51:10 +0100 > To: users@tapestry.apache.org > Subject: Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying > &

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Kovács István
Howard, Thanks for the reply (and for Tapestry, of course :-). I've figured "mvn package" out, so I have the WAR. On encoding: On 19/03/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: [...] Tapestry's localization support has only been partially "roughed in"; T4 has additional features, such

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Kovács István
Hi Istvan :-) Thanks, now I have the WAR, deployed on Tomcat, configured as you suggested. Unfortunately, I still have encoding issues. Trouble is, what I need to fix is not the URI encoding, but encoding of the HTTP response. I seem to be getting content encoded in ISO-8859-2 or Windows-1250, wi

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Howard Lewis Ship
mvn package will create the WAR file (in the target directory), which you can then use in any servlet container. Tapestry's localization support has only been partially "roughed in"; T4 has additional features, such as meta-data to control the charset and encoding when reading in a .properties f

Re: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Davor Hrg
none of those options worked for me in T5, nor template text nor text from database (text from database displays correctly in the console) Davor Hrg On 3/19/07, Istvan Szucs <[EMAIL PROTECTED]> wrote: Deploy mavenized project: 1. pom.xml: war 2. command prompt: mvn deploy 3. You have a *.war f

RE: Tapestry 5 - Jetty - ISO-8859-1 instead of UTF-8; deploying

2007-03-19 Thread Istvan Szucs
Deploy mavenized project: 1. pom.xml: war 2. command prompt: mvn deploy 3. You have a *.war file in your 'project/target' directory. Open tomcat manager and deploy your *.war file with admin role. Jetty: ??? - Jetty + UTF-8: -Dorg.mortbay.util.URI.charset=UTF-8 Tomcat + utf-8: Update t