Re: hot to set Unicoding to UTF-8
Hi, I think to be able to use UTF-8 you have to encode the properties files as XML properties files (otherwise you have to escape characters that cannot be directly represented on ISO 8859-1). On Tue, Dec 11, 2012 at 8:33 AM, oliver.stef ova...@gmail.com wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Regards - Ernesto Reinaldo Barreiro Antilia Soft http://antiliasoft.com/ http://antiliasoft.com/antilia
Re: hot to set Unicoding to UTF-8
IIRC you have to run on Java 6 for that feature. Sven On 12/11/2012 09:36 AM, Ernesto Reinaldo Barreiro wrote: Hi, I think to be able to use UTF-8 you have to encode the properties files as XML properties files (otherwise you have to escape characters that cannot be directly represented on ISO 8859-1). On Tue, Dec 11, 2012 at 8:33 AM, oliver.stef ova...@gmail.com wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: hot to set Unicoding to UTF-8
Yep! On Tue, Dec 11, 2012 at 9:37 AM, Sven Meier s...@meiers.net wrote: IIRC you have to run on Java 6 for that feature. Sven On 12/11/2012 09:36 AM, Ernesto Reinaldo Barreiro wrote: Hi, I think to be able to use UTF-8 you have to encode the properties files as XML properties files (otherwise you have to escape characters that cannot be directly represented on ISO 8859-1). On Tue, Dec 11, 2012 at 8:33 AM, oliver.stef ova...@gmail.com wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/** image_1.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/** image_2.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.**n4.nabble.com/hot-to-set-** Unicoding-to-UTF-8-tp4654681.**htmlhttp://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. --**--** - To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Regards - Ernesto Reinaldo Barreiro Antilia Soft http://antiliasoft.com/ http://antiliasoft.com/antilia
Re: hot to set Unicoding to UTF-8
On Tue, Dec 11, 2012 at 8:38 AM, Sven Meier s...@meiers.net wrote: Give your file the suffix .utf8.properties. In Wicket 6 you have to use .properties.xml as file extension when using the XML format. The XML format is supported in Wicket 1.5/JDK 1.5 too just the file extension there was just .xml (com.example.MyApp.xml) Sven On 12/11/2012 08:33 AM, oliver.stef wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/**image_1.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/**image_2.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.** n4.nabble.com/hot-to-set-**Unicoding-to-UTF-8-tp4654681.**htmlhttp://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: hot to set Unicoding to UTF-8
With UtfPropertiesFilePropertiesLoader you can use properties with UTF-8 encoding, no XML involved there. Sven On 12/11/2012 09:42 AM, Martin Grigorov wrote: On Tue, Dec 11, 2012 at 8:38 AM, Sven Meier s...@meiers.net wrote: Give your file the suffix .utf8.properties. In Wicket 6 you have to use .properties.xml as file extension when using the XML format. The XML format is supported in Wicket 1.5/JDK 1.5 too just the file extension there was just .xml (com.example.MyApp.xml) Sven On 12/11/2012 08:33 AM, oliver.stef wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/**image_1.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.**n4.nabble.com/file/n4654681/**image_2.pnghttp://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.** n4.nabble.com/hot-to-set-**Unicoding-to-UTF-8-tp4654681.**htmlhttp://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: hot to set Unicoding to UTF-8
I guess you can use language files in xml format instead of properties On Tue, Dec 11, 2012 at 2:33 PM, oliver.stef ova...@gmail.com wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax
Re: hot to set Unicoding to UTF-8
Give your file the suffix .utf8.properties. Sven On 12/11/2012 08:33 AM, oliver.stef wrote: Hi all, When i'm saving my properties file in 'UTF-8' coding, i can't see the correct chars (image 1). but when i'm saving it as displayed if i'm as 'ISO-8859-1' it looks fine (image 2). how can i set wicket to load the properties file to use UTF-8? Thanks! image 1 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_1.png image 2 http://apache-wicket.1842946.n4.nabble.com/file/n4654681/image_2.png -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/hot-to-set-Unicoding-to-UTF-8-tp4654681.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
UTF-8 encoding RFE for warning?
Hi I've UTF-8 encoded all my files, setup tomcat to support utf-8 and everything.. But something did'nt work because my chars where all garble.. Then I tried all sorts of stuff, only to discover that nothing worked. Finally I figured out that I was using .property files and not .property.xml , apparently java does not support utf-8 in .property files. A warning on having utf-8 content in .property files would be nice.. Or is it just general knowledge? regards Nino
Re: UTF-8 encoding RFE for warning?
On Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: Hi I've UTF-8 encoded all my files, setup tomcat to support utf-8 and everything.. But something did'nt work because my chars where all garble.. Then I tried all sorts of stuff, only to discover that nothing worked. Finally I figured out that I was using .property files and not .property.xml , apparently java does not support utf-8 in .property files. A warning on having utf-8 content in .property files would be nice.. Or is it just general knowledge? For me this is a well known fact but many people still hit this problem, I'd love to see a Java program that accepts file as input and returns what encoding is used. There are some tricks with checking the first few bytes but I've never seen something stable that works for all possible encodings. regards Nino -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 encoding RFE for warning?
It's a known fact for me aswell now :) Ok it might be a no go then i guess. Might be the reason why eclipse also has the encoding determined from content they actually have to read all the content to *guess* what encoding it is. regards Nino 2011/11/2 Martin Grigorov mgrigo...@apache.org On Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: Hi I've UTF-8 encoded all my files, setup tomcat to support utf-8 and everything.. But something did'nt work because my chars where all garble.. Then I tried all sorts of stuff, only to discover that nothing worked. Finally I figured out that I was using .property files and not .property.xml , apparently java does not support utf-8 in .property files. A warning on having utf-8 content in .property files would be nice.. Or is it just general knowledge? For me this is a well known fact but many people still hit this problem, I'd love to see a Java program that accepts file as input and returns what encoding is used. There are some tricks with checking the first few bytes but I've never seen something stable that works for all possible encodings. regards Nino -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: UTF-8 encoding RFE for warning?
It's a known fact for me aswell now :) Note that even though properties files need to be in the default encoding, you can use non-iso-latin characters by way of the \u syntax, though a bit more cumbersome than raw Unicode characters. - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 encoding RFE for warning?
Nitpicking a bit: .properties files need to be in ISO 8859-1 encoding not in default. Attila 2011/11/2 Wilhelmsen Tor Iver toriv...@arrive.no It's a known fact for me aswell now :) Note that even though properties files need to be in the default encoding, you can use non-iso-latin characters by way of the \u syntax, though a bit more cumbersome than raw Unicode characters. - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
What i did to make sure this works is everything you did + encodeURIComponent(value) http://www.w3schools.com/jsref/jsref_encodeURIComponent.asp Never had any other encoding problems in any browser afterwards. On Sun 16 Oct 2011 11:56:14 AM EEST, Attila Király wrote: Please provide a small quickstart showcasing the problem to get more help because based on these information it should work. Attila 2011/10/15 Mathias Nilssonwicket.program...@gmail.com Oh, And I've also tried putting org.springframework.web.filter.CharacterEncodingFilter as the first filter -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
Please provide a small quickstart showcasing the problem to get more help because based on these information it should work. Attila 2011/10/15 Mathias Nilsson wicket.program...@gmail.com Oh, And I've also tried putting org.springframework.web.filter.CharacterEncodingFilter as the first filter -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
This is my web.xml. Still does not work ?xml version=1.0 encoding=UTF-8? web-app xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://java.sun.com/xml/ns/javaee; xmlns:web=http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; id=media-server version=2.5 display-namemedia-server/display-name context-param param-namecontextConfigLocation/param-name param-valueclasspath:applicationContext.xml/param-value /context-param context-param param-namelog4jConfigLocation/param-name param-valueclasspath:log4j.xml/param-value /context-param context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param context-param param-namewebAppRootKey/param-name param-valuemedia-server/param-value /context-param filter filter-nameencodingFilter/filter-name filter-classorg.springframework.web.filter.CharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param init-param param-nameforceEncoding/param-name param-valuetrue/param-value /init-param /filter filter filter-nameSpring OpenEntityManagerInViewFilter/filter-name filter-class org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter/filter-class /filter filter-mapping filter-nameSpring OpenEntityManagerInViewFilter/filter-name url-pattern/*/url-pattern /filter-mapping filter-mapping filter-nameencodingFilter/filter-name url-pattern/*/url-pattern /filter-mapping filter filter-namewicket.media/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuese.fototext.media.server.web.application.MediaApplication/param-value /init-param /filter filter-mapping filter-namewicket.media/filter-name url-pattern/*/url-pattern /filter-mapping listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class /listener servlet servlet-nameCXFServlet/servlet-name servlet-classorg.apache.cxf.transport.servlet.CXFServlet/servlet-class /servlet servlet-mapping servlet-nameCXFServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping /web-app -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907026.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
Oh, And I've also tried putting org.springframework.web.filter.CharacterEncodingFilter as the first filter -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3907047.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
Sorry. Forgot to say wicket version 1.4.18 getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); set in init -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3906254.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 not working
You have to configure a filter (write one or reuse existing ones like http://static.springsource.org/spring/docs/3.1.0.RC1/javadoc-api/org/springframework/web/filter/CharacterEncodingFilter.html) to call request.setCharacterEncoding(UTF-8) before wicket gets the request. This is not needed with wicket 1.5. Attila 2011/10/14 Mathias Nilsson wicket.program...@gmail.com Sorry. Forgot to say wicket version 1.4.18 getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); set in init -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3906254.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Why is UTF-8 encoding lost on redirect
Hi,
i have the following situation.
In browser i type my url (localhost:8080/param/Küche).
In page-parameters param is Küche (fine).
On Page there are two links
public MyPage(final PageParameters parameters) {
super(parameters);
StatelessFormVoid form = new StatelessFormVoid(form);
form.add(new StatelessLink(redirectlink) {
@Override
public void onClick() {
setResponsePage(MyPage.class, getPageParameters());
setRedirect(true);
}
});
form.add(new StatelessLink(simplelink) {
@Override
public void onClick() {
setResponsePage(MyPage.class, getPageParameters());
}
});
add(form);
}
}
Clicking on the simplelink provides Küche as parameter. But the url
contains the listener interface
which i would like to remove.
Click chain on the redirectlink leads firstly to K%FCche then to K{a
sign}che and at the end K.
What could that be?
I've created a quickstart for this
https://issues.apache.org/jira/browse/WICKET-3981
Testing this with 1.5-RC7 had no problem. But i'm on 1.4.18 and have to
stay there so long.
Maybe someone can give me a hint.
Thanks
Per
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: [1.4.6] WicketURLDecoder - No current Application found - defaulting encoding to UTF-8
2010/2/5 Igor Vaynberg igor.vaynb...@gmail.com
disable it in your logging configuration
-igor
I tried a lot of configurations , but http.WicketURLDecoder's warning still
pops up...
log4j.rootLogger=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d %-5p %C{2} - %m%n
Then , I tried the following three configurations , but are all invalid ,
WicketURLDecoder's warning still pops up :
log4j.logger.org.apache.wicket.protocol.http.WicketURLDecoder=OFF
log4j.org.apache.wicket.protocol.http.WicketURLDecoder=OFF
log4j.logger.org.apache.wicket.protocol.http.WicketURLDecoder=ERROR ,
console
Re: [1.4.6] WicketURLDecoder - No current Application found - defaulting encoding to UTF-8
looking at the code its using the Application class logger...strange,
i will fix in the branch.
private static final Logger log = LoggerFactory.getLogger(Application.class);
-igor
On Fri, Feb 5, 2010 at 12:02 AM, smallufo small...@gmail.com wrote:
2010/2/5 Igor Vaynberg igor.vaynb...@gmail.com
disable it in your logging configuration
-igor
I tried a lot of configurations , but http.WicketURLDecoder's warning still
pops up...
log4j.rootLogger=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d %-5p %C{2} - %m%n
Then , I tried the following three configurations , but are all invalid ,
WicketURLDecoder's warning still pops up :
log4j.logger.org.apache.wicket.protocol.http.WicketURLDecoder=OFF
log4j.org.apache.wicket.protocol.http.WicketURLDecoder=OFF
log4j.logger.org.apache.wicket.protocol.http.WicketURLDecoder=ERROR ,
console
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
[1.4.6] WicketURLDecoder - No current Application found - defaulting encoding to UTF-8
After upgrading to 1.4.6 , it always pops up this warning : WARN http.WicketURLDecoder - No current Application found - defaulting encoding to UTF-8 It is ok in 1.4.5 , but I don't know why it has such warning in 1.4.6 . How to get rid of it ? Thanks ...
Re: [1.4.6] WicketURLDecoder - No current Application found - defaulting encoding to UTF-8
disable it in your logging configuration -igor On Thu, Feb 4, 2010 at 8:13 PM, smallufo small...@gmail.com wrote: After upgrading to 1.4.6 , it always pops up this warning : WARN http.WicketURLDecoder - No current Application found - defaulting encoding to UTF-8 It is ok in 1.4.5 , but I don't know why it has such warning in 1.4.6 . How to get rid of it ? Thanks ... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Non-english UTF-8 characters in POSTed data
Hi all, I'm probably facing the same problem as described here: http://mail-archives.apache.org/mod_mbox/wicket-users/200804.mbox/%3cdf3d7452-0ac0-4cf7-8164-87e9371d8...@signicat.com%3e I use Maven to build my applications, so I have a beginner's qustion: how to reorganize a project to work with modified version of wicket-ajax.js file? Thanks, Petr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Non-english UTF-8 characters in POSTed data
Hmm.. can't you fix this with encoding settings? getMarkupSettings().setDefaultMarkupEncoding(WebPageConstants.ISO_8859_1); Or something? I would assume a modified version wicket-ajax can be just accomplished by creating a new one in same package. However, if there is no setup for such thing it sounds like a bug. ** Martin 2009/9/16 Petr Fejfar petr.fej...@gmail.com: Hi all, I'm probably facing the same problem as described here: http://mail-archives.apache.org/mod_mbox/wicket-users/200804.mbox/%3cdf3d7452-0ac0-4cf7-8164-87e9371d8...@signicat.com%3e I use Maven to build my applications, so I have a beginner's qustion: how to reorganize a project to work with modified version of wicket-ajax.js file? Thanks, Petr - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Non-english UTF-8 characters in POSTed data
On Wed, Sep 16, 2009 at 1:35 PM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: Hmm.. can't you fix this with encoding settings? getMarkupSettings().setDefaultMarkupEncoding(WebPageConstants.ISO_8859_1); Or something? It seems it cannot. I have in my appliction's init() code: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); and both, static texts from .HTML, translated texts from .XML are show O.K., but data posted from a form are not. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Allright, I fed the daemon ;) I created a new issue in https://issues.apache.org/jira/browse/WICKET-2451 and I found that WICKET-1443 is similar but already closed since 1 year. 2009/9/2 Eelco Hillenius eelco.hillen...@gmail.com: The result is in the attachment file (sorry but I don't have a quick way to do a patch file against SVN trunk at the moment). The mailing list daemon thinks attachments are delicious. The way to submit patches is to attach it to a JIRA issue. Did anyone already open a feature request for this? If not, please open an issue here: http://issues.apache.org/jira/browse/WICKET. Further discussion and patches can go there. Cheers, Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
FYI, spring supports UTF-8 property files as well: see org.springframework.context.support.ReloadableResourceBundleMessageSource Maarten On Wed, Sep 2, 2009 at 2:37 AM, Eelco Hillenius eelco.hillen...@gmail.comwrote: But I'm sure you can write a properties implementation that reads from UTF-8 in a few hours max, especially now that you have an example in Tapestry's code. Patch is welcome :-) Why not just borrow the code from Tapestry? It's Apache licensed of course, so no issues there. Sure, if it makes sense. But it needs to fit in Wicket's framework, and I don't know how Tapestry specific that code for handling those UTF-8 properties files in Tapestry is. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
But I'm sure you can write a properties implementation that reads from UTF-8 in a few hours max, especially now that you have an example in Tapestry's code. Patch is welcome :-) Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org I just had a look at Tapestry 4.0.2 implementation and it uses 13 classes all located in the package org.apache.tapestry.util.text.* and that are under Apache License, Version 2.0. All other imports are java.util.* and java.io.* so at first look it seems to be reusable. The important point is that the reader uses an InputStreamReader that honors the encoding you set in the application. The other 12 classes are a nice reimplementation of the JDK Properties.load0(LineReader lr) method. IMHO the JDK stuff is really outdated and looke like C/C++ code. And 90% of the code in both version is here to handle comments, whitespaces, carriage return and all that kind of stuff, so if somebody knows a good reusable parser able to handle properties files grammar, the job is almost done. Later I'll have a look at T 5.1 implementation and org.springframework.context.support.ReloadableResourceBundleMessageSource as suggested and I'll let you know. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
On Tue, Sep 1, 2009 at 3:39 PM, Johan Compagner jcompag...@gmail.comwrote: Everybody should stop using any other encoding then UTF-8 Common people we should start this change from happening now :) Drop all charsets and all over the world. ban them everywhere, it should be illegal to use them, if you do still use them you should be thrown in to prison for at least 5 years. UTF-8 everywhere! Agreed! So let's set the default settings to UTF-8, instead of the system settings. Would have saved me some time debugging... My development environment uses UTF-8, deployment environment does not, so that was causing some trouble. Antoine
Re: UTF-8
I had a look at T5 and Spring code : - Spring checks if the JDK supports UTF-8 files, and if it does not support it acts like T4 and parses the properties file. The implementation is much more compact than in T4. - T5 does a native2ascii conversion of the properties files on the fly. So I figured out a quick patch that is a combination of the 3 methods : - try to use JDK 6 native implementation - if not available then convert on the fly to ASCII and use native JDK =5 properties The result is in the attachment file (sorry but I don't have a quick way to do a patch file against SVN trunk at the moment). The method readUTFStreamToEscapedASCII is directly borrowed from T5.1 (Apache License 2.0), and I slightly modified PropertiesFilePropertiesLoader constructor and loadProperties().Tell me what you think of that. I only runed the Maven build on wicket-1.4.1 to check that the unit tests are not broken. I think that I should use application.getMarkupSettings().getDefaultMarkupEncoding() to set the encoding of my InputStream, but when doing this the unit tests fail with NullPointerException (and I don't have taken the time to look deeper into this). 2009/9/2 Maarten Bosteels mbosteels@gmail.com: FYI, spring supports UTF-8 property files as well: see org.springframework.context.support.ReloadableResourceBundleMessageSource Maarten - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
The result is in the attachment file (sorry but I don't have a quick way to do a patch file against SVN trunk at the moment). The mailing list daemon thinks attachments are delicious. The way to submit patches is to attach it to a JIRA issue. Did anyone already open a feature request for this? If not, please open an issue here: http://issues.apache.org/jira/browse/WICKET. Further discussion and patches can go there. Cheers, Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Because Wicket uses Java Properties objects and it can't handle UTF-8. In Tapestry they made a wapper around Java Properties so that you can use the good old properties format (ie key=value) with UTF8 encoding and IMO it's a nice feature missing in Wicket. Erm http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Erm http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Which says Wicket 2.0 (yes, it's that old), but it was also one of the first things backported. Loading is automatic, and .xml takes precedence over .properties. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
In case you use Eclipse, there is an utility called Properties Editor http://propedit.sourceforge.jp/index_en.html Vit Olivier Bourgeois wrote: That's exactly what I said : I had to use XML properties files to have UTF-8 localized properties. You can't use simple properties format because Java can't handle natively anything else than ISO. We use also Tapestry here, and you can use UTF-8 properties files (thanks to the wrapper around native Java properties). XML files are allright, but they are definitively verbose. 2009/9/1 Eelco Hillenius eelco.hillen...@gmail.com: Erm http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Which says Wicket 2.0 (yes, it's that old), but it was also one of the first things backported. Loading is automatic, and .xml takes precedence over .properties. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Man, use the native2ascii built-in JDK tool. It's very simple, transforms your messages into ASCII escaped. Regards, Wojtek Olivier Bourgeois pisze: That's exactly what I said : I had to use XML properties files to have UTF-8 localized properties. You can't use simple properties format because Java can't handle natively anything else than ISO. We use also Tapestry here, and you can use UTF-8 properties files (thanks to the wrapper around native Java properties). XML files are allright, but they are definitively verbose. 2009/9/1 Eelco Hillenius eelco.hillen...@gmail.com: Erm http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Which says Wicket 2.0 (yes, it's that old), but it was also one of the first things backported. Loading is automatic, and .xml takes precedence over .properties. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
The people at my office handling translations are using a simple UTF-8 capable editor (that can be Eclipse for instance) and there is no need to escape anything when you use UTF-8 in the properties files. That's much more comfortable when working with arabic or chinese, because people can read without unescaping, and they can also use a diff tool. The point I was raising is that when working on a Tapestry application, people at my office are used to have a simple property format, and you can do this because they made a wrapper around native Java Properties that can handle UTF-8 in properties file. When I switched to Wicket and XML properties files, they complained that it was much more verbose for no gain. And I don't have any objections to this statement. Doing the same thing with Wicket should be easy, basically it should consists of changing the method : PropertiesFilePropertiesLoader.loadProperties(BufferedInputStream in) defined in PropertiesFactory class to *not* use Java Properties directly but instead fill a new Property object from an InputStream. And the InputStream should honor the application encoding set in the Application settings, which in our case is UTF-8. And you return Properties like before. That's it. See : http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/util/text/LocalizedProperties.html 2009/9/1 Wojciech Żaboklicki zabia...@gmail.com: Man, use the native2ascii built-in JDK tool. It's very simple, transforms your messages into ASCII escaped. Regards, Wojtek Olivier Bourgeois pisze: That's exactly what I said : I had to use XML properties files to have UTF-8 localized properties. You can't use simple properties format because Java can't handle natively anything else than ISO. We use also Tapestry here, and you can use UTF-8 properties files (thanks to the wrapper around native Java properties). XML files are allright, but they are definitively verbose. 2009/9/1 Eelco Hillenius eelco.hillen...@gmail.com: Erm http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Which says Wicket 2.0 (yes, it's that old), but it was also one of the first things backported. Loading is automatic, and .xml takes precedence over .properties. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
We usually do multilanguage sites, so we always try to keep the web application in a full UTF-8 cycle. With Wicket we were fine doing the following: as mentioned above: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); 1) Edit connectors in server.xml and add URIEncoding=UTF-8 Yes: http://cwiki.apache.org/WW/how-to-support-utf-8-uriencoding-with-tomcat.html 2) Call request.setCharacterEncoding(UTF-8) (at the very beginning of the cycle) We never had to use this (at least with Wicket 1.4.x). Just make sure your template always has meta http-equiv=Content-Type content=text/html; charset=UTF-8 / in it's header. If you plan to use mod_jk serving UTF-8 encoded URL's with special chars, you also might have to consider this: http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-UsingUTF8encodedURIswithmodjk Best regards, Roman Douglas Ferguson-2 wrote: Excellent. I saw a bunch of emails floating around saying that you'd have to also 1) Edit connectors in server.xml and add URIEncoding=UTF-8 2) Call request.setCharacterEncoding(UTF-8) (at the very beginning of the cycle) Are those also necessary? I'm assuming that I'll need these: property name=hibernate.connection.characterEncodingUTF-8/property property name=hibernate.connection.useUnicodetrue/property On Aug 31, 2009, at 5:48 AM, Tomasz Dziurko wrote: Add this to init() method in your Application class: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); This should be enough. -- Regards, Tomasz Dziurko -- View this message in context: http://www.nabble.com/UTF-8-tp25221136p25240295.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Yeah, one charset to rule them all ! :-) 2009/9/1 Johan Compagner jcompag...@gmail.com: Everybody should stop using any other encoding then UTF-8 Common people we should start this change from happening now :) Drop all charsets and all over the world. ban them everywhere, it should be illegal to use them, if you do still use them you should be thrown in to prison for at least 5 years. UTF-8 everywhere! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
On Tue, Sep 1, 2009 at 1:19 AM, Olivier Bourgeoisolivier.bourgeois@gmail.com wrote: That's exactly what I said : I had to use XML properties files to have UTF-8 localized properties. You can't use simple properties format because Java can't handle natively anything else than ISO. We use also Tapestry here, and you can use UTF-8 properties files (thanks to the wrapper around native Java properties). Ah, right. Well reading is an art :-) It's been a while, but I think I considered 'fixing' or otherwise supporting loading in regular properties files through UTF-8, but decided against it because it would be non-standard even in newer JDK versions, and the newer JDKs already had a solution for reading properties in UTF-8 with xml files. But I'm sure you can write a properties implementation that reads from UTF-8 in a few hours max, especially now that you have an example in Tapestry's code. Patch is welcome :-) Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
On Tue, Sep 1, 2009 at 12:00 PM, Eelco Hilleniuseelco.hillen...@gmail.com wrote: But I'm sure you can write a properties implementation that reads from UTF-8 in a few hours max, especially now that you have an example in Tapestry's code. Patch is welcome :-) Why not just borrow the code from Tapestry? It's Apache licensed of course, so no issues there. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
But I'm sure you can write a properties implementation that reads from UTF-8 in a few hours max, especially now that you have an example in Tapestry's code. Patch is welcome :-) Why not just borrow the code from Tapestry? It's Apache licensed of course, so no issues there. Sure, if it makes sense. But it needs to fit in Wicket's framework, and I don't know how Tapestry specific that code for handling those UTF-8 properties files in Tapestry is. Eelco - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
UTF-8
Is there a documented process for enabling UTF-8 in wicket? D/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8
Add this to init() method in your Application class: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); This should be enough. -- Regards, Tomasz Dziurko
Re: UTF-8
Excellent. I saw a bunch of emails floating around saying that you'd have to also 1) Edit connectors in server.xml and add URIEncoding=UTF-8 2) Call request.setCharacterEncoding(UTF-8) (at the very beginning of the cycle) Are those also necessary? I'm assuming that I'll need these: property name=hibernate.connection.characterEncodingUTF-8/property property name=hibernate.connection.useUnicodetrue/property On Aug 31, 2009, at 5:48 AM, Tomasz Dziurko wrote: Add this to init() method in your Application class: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); This should be enough. -- Regards, Tomasz Dziurko
Re: UTF-8
I am using Wicket 1.4 with UTF-8 pages and properties, and I added in my Application : getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); That's enough. For the localization properties files I had to use XML properties files like this : ?xml version=1.0 encoding=UTF-8? !DOCTYPE properties SYSTEM http://java.sun.com/dtd/properties.dtd; properties entry key=page.titleTitre de la page/entry /properties Because Wicket uses Java Properties objects and it can't handle UTF-8. In Tapestry they made a wapper around Java Properties so that you can use the good old properties format (ie key=value) with UTF8 encoding and IMO it's a nice feature missing in Wicket. 2009/8/31 Douglas Ferguson doug...@douglasferguson.us: Excellent. I saw a bunch of emails floating around saying that you'd have to also 1) Edit connectors in server.xml and add URIEncoding=UTF-8 2) Call request.setCharacterEncoding(UTF-8) (at the very beginning of the cycle) Are those also necessary? I'm assuming that I'll need these: property name=hibernate.connection.characterEncodingUTF-8/property property name=hibernate.connection.useUnicodetrue/property On Aug 31, 2009, at 5:48 AM, Tomasz Dziurko wrote: Add this to init() method in your Application class: getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); This should be enough. -- Regards, Tomasz Dziurko - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
VelocityTemplate and UTF-8
Hello, I cannot seem to get VelocityPanel to output my files properly. I am embedding vm files within Wicket HTML files using VelocityPanels and no matter how I encode the vm file (UTF-8 encoded or unicode escaped), I am not getting the proper characters displayed when the page is served. I have set the default encoding on the MarkupSettings and I have also created a velocity.properties file with: input.encoding=UTF-8 and output.encoding=UTF-8 and set the proper init params on the servlet. Is there something else I need to do or something I'm doing wrong? I know there must be a lot of non-English people using Wicket so if you guys have the solution, it would be a huge help as I'm really struggling getting international languages to work. Thanks!
Re: VelocityTemplate and UTF-8
I figured it out. For reference, I overrode the parseGeneratedMarkup() method to return true and it all comes out properly. On Wed, Jul 22, 2009 at 12:54 PM, Andrew Berman atber...@gmail.com wrote: Hello, I cannot seem to get VelocityPanel to output my files properly. I am embedding vm files within Wicket HTML files using VelocityPanels and no matter how I encode the vm file (UTF-8 encoded or unicode escaped), I am not getting the proper characters displayed when the page is served. I have set the default encoding on the MarkupSettings and I have also created a velocity.properties file with: input.encoding=UTF-8 and output.encoding=UTF-8 and set the proper init params on the servlet. Is there something else I need to do or something I'm doing wrong? I know there must be a lot of non-English people using Wicket so if you guys have the solution, it would be a huge help as I'm really struggling getting international languages to work. Thanks!
Problems with UTF-8 chars in query string
Hello! I am having a problem with the double-encoding of Japanese characters that are in the query string. For example: http://www.example.com/path/q=日本語 If I write the raw value directly in the URL string in my browser, there are no problems. If I write the URL encoded value directly in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with UTF-8 chars in query string
Ok, this seems to have something to do with proxying, not Wicket. When I enter 日本語 into the form, Wicket correctly sends back the reply: HTTP/1.1 302 Location: http://www.example.com/path?q=%E6%97%A5%E6%9C%AC%E8%AA%9E To which my browser redirects with: GET /path/?q=%25E6%2597%25A5%25E6%259C%25AC%25E8%25AA%259E HTTP/1.1 The second request is double-encoded and is not correct. So, not a Wicket problem. However, any ideas where I could look for the solution? Thanks! =David On Jun 9, 2009, at 1:56 PM, David Leangen wrote: Hello! I am having a problem with the double-encoding of Japanese characters that are in the query string. For example: http://www.example.com/path/q=日本語 If I write the raw value directly in the URL string in my browser, there are no problems. If I write the URL encoded value directly in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with UTF-8 chars in query string
Ok, sorry for the noise. I just needed to add the [NE] rule to my RewriteRule in my apache config and that did the trick. Cheers, =David On Jun 9, 2009, at 2:06 PM, David Leangen wrote: Ok, this seems to have something to do with proxying, not Wicket. When I enter 日本語 into the form, Wicket correctly sends back the reply: HTTP/1.1 302 Location: http://www.example.com/path?q=%E6%97%A5%E6%9C%AC%E8%AA%9E To which my browser redirects with: GET /path/?q=%25E6%2597%25A5%25E6%259C%25AC%25E8%25AA%259E HTTP/1.1 The second request is double-encoded and is not correct. So, not a Wicket problem. However, any ideas where I could look for the solution? Thanks! =David On Jun 9, 2009, at 1:56 PM, David Leangen wrote: Hello! I am having a problem with the double-encoding of Japanese characters that are in the query string. For example: http://www.example.com/path/q=日本語 If I write the raw value directly in the URL string in my browser, there are no problems. If I write the URL encoded value directly in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Did you configure tomcat correctly for utf 8? Search this list for the right settings On 30/01/2009, Philipp Daumke dau...@averbis.de wrote: Hi all, when I enter German umlauts (e.g. äöü) in a wicket text field it's converted to äöü. Everything seems to be in UTF-8. I already tried to apply a filter as described in http://wiki.apache.org/tomcat/Tomcat/UTF-8 without success. Any ideas? Thanks for your help Philipp -- Averbis GmbH c/o Klinikum der Albert-Ludwigs-Universität Stefan-Meier-Strasse 26 D-79104 Freiburg Fon: +49 (0) 761 - 203 6707 Fax: +49 (0) 761 - 203 6800 E-Mail: dau...@averbis.de Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó Sitz der Gesellschaft: Freiburg i. Br. AG Freiburg i. Br., HRB 701080 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi Jonas,
thanks for your help, but I think it doesn't help. Just to make sure
that I understood the Application#init correctly, you meant to do it
like this, right(?):
public class MyApp extends WebApplication {
public void init()
{
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
}
public Class getHomePage() {
return Index.class;
}
}
Still, it seems to convert my code from latin1 to utf8, even though I
enter utf8-text.
Thanks for further help
Philipp
Hi,
have you tried setting
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
in your Application#init
If you don't set the default markup encoding explicitly, the default
for it is the 'os provided encoding' (see:
IMarkupSettings#getDefaultMarkupEncoding)
cheers,
Jonas
On Fri, Jan 30, 2009 at 1:02 AM, Philipp Daumke dau...@averbis.de wrote:
Hi Mathias,
'äöü' is actually already converted to 'äöü' when I add a breakpoint at
the onSubmit method of my form (so right when I get the input of the text
field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my
firefox says UTF-8. What I think is that Wicket or Tomcat treats my
UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8, so
into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell which
is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output is
'äöü' again.
Any idea what to do?
All the best
Philipp
Do you save it to a database and then display the text? How do you present
it?
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
no i mean Tomcat settings not wicket settings
search for tomcat utf uri encoding in google
On Fri, Jan 30, 2009 at 09:11, Philipp Daumke dau...@averbis.de wrote:
Hi Jonas,
thanks for your help, but I think it doesn't help. Just to make sure that I
understood the Application#init correctly, you meant to do it like this,
right(?):
public class MyApp extends WebApplication {
public void init()
{
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
}
public Class getHomePage() {
return Index.class;
}
}
Still, it seems to convert my code from latin1 to utf8, even though I enter
utf8-text.
Thanks for further help
Philipp
Hi,
have you tried setting
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
in your Application#init
If you don't set the default markup encoding explicitly, the default
for it is the 'os provided encoding' (see:
IMarkupSettings#getDefaultMarkupEncoding)
cheers,
Jonas
On Fri, Jan 30, 2009 at 1:02 AM, Philipp Daumke dau...@averbis.de
wrote:
Hi Mathias,
'äöü' is actually already converted to 'äöü' when I add a breakpoint
at
the onSubmit method of my form (so right when I get the input of the text
field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my
firefox says UTF-8. What I think is that Wicket or Tomcat treats my
UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8,
so
into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell
which
is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output
is
'äöü' again.
Any idea what to do?
All the best
Philipp
Do you save it to a database and then display the text? How do you
present
it?
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi Philipp,
yes, thats correct. We had similar problems and fixed it that way, but maybe
something else is still not set to UTF-8.
I assume you have configured your tomcat connector using
URIEncoding=UTF-8 (I think that is what Johan is referring to?).
Have you tried adding a meta tag to your markup? Something like
[meta http-equiv=Content-Type content=text/html; charset=UTF-8 /]
cheers,
Jonas
On Fri, Jan 30, 2009 at 9:11 AM, Philipp Daumke dau...@averbis.de wrote:
Hi Jonas,
thanks for your help, but I think it doesn't help. Just to make sure that I
understood the Application#init correctly, you meant to do it like this,
right(?):
public class MyApp extends WebApplication {
public void init()
{
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
}
public Class getHomePage() {
return Index.class;
}
}
Still, it seems to convert my code from latin1 to utf8, even though I enter
utf8-text.
Thanks for further help
Philipp
Hi,
have you tried setting
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
in your Application#init
If you don't set the default markup encoding explicitly, the default
for it is the 'os provided encoding' (see:
IMarkupSettings#getDefaultMarkupEncoding)
cheers,
Jonas
On Fri, Jan 30, 2009 at 1:02 AM, Philipp Daumke dau...@averbis.de wrote:
Hi Mathias,
'äöü' is actually already converted to 'äöü' when I add a breakpoint
at
the onSubmit method of my form (so right when I get the input of the text
field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my
firefox says UTF-8. What I think is that Wicket or Tomcat treats my
UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8,
so
into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell
which
is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output
is
'äöü' again.
Any idea what to do?
All the best
Philipp
Do you save it to a database and then display the text? How do you
present
it?
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi Jonas, hi Johann,
grrh, I forgot to set URIEncoding=UTF-8. Now it works, thank you for
your help.
All the best
Philipp
Hi Philipp,
yes, thats correct. We had similar problems and fixed it that way, but maybe
something else is still not set to UTF-8.
I assume you have configured your tomcat connector using
URIEncoding=UTF-8 (I think that is what Johan is referring to?).
Have you tried adding a meta tag to your markup? Something like
[meta http-equiv=Content-Type content=text/html; charset=UTF-8 /]
cheers,
Jonas
On Fri, Jan 30, 2009 at 9:11 AM, Philipp Daumke dau...@averbis.de wrote:
Hi Jonas,
thanks for your help, but I think it doesn't help. Just to make sure that I
understood the Application#init correctly, you meant to do it like this,
right(?):
public class MyApp extends WebApplication {
public void init()
{
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
}
public Class getHomePage() {
return Index.class;
}
}
Still, it seems to convert my code from latin1 to utf8, even though I enter
utf8-text.
Thanks for further help
Philipp
Hi,
have you tried setting
getRequestCycleSettings().setResponseRequestEncoding(UTF-8);
getMarkupSettings().setDefaultMarkupEncoding(UTF-8);
in your Application#init
If you don't set the default markup encoding explicitly, the default
for it is the 'os provided encoding' (see:
IMarkupSettings#getDefaultMarkupEncoding)
cheers,
Jonas
On Fri, Jan 30, 2009 at 1:02 AM, Philipp Daumke dau...@averbis.de wrote:
Hi Mathias,
'äöü' is actually already converted to 'äöü' when I add a breakpoint
at
the onSubmit method of my form (so right when I get the input of the text
field from my model).
My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my
firefox says UTF-8. What I think is that Wicket or Tomcat treats my
UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8,
so
into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell
which
is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output
is
'äöü' again.
Any idea what to do?
All the best
Philipp
Do you save it to a database and then display the text? How do you
present
it?
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Averbis GmbH
c/o Klinikum der Albert-Ludwigs-Universität
Stefan-Meier-Strasse 26
D-79104 Freiburg
Fon: +49 (0) 761 - 203 6707
Fax: +49 (0) 761 - 203 6800
E-Mail: dau...@averbis.de
Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó
Sitz der Gesellschaft: Freiburg i. Br.
AG Freiburg i. Br., HRB 701080
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
We had similar problems and by changing Connector port=80/ to Connector port=80 URIEncoding=UTF-8/ in the tomcat/conf/server.xml fixed the problem. Tom Johan Compagner wrote: Did you configure tomcat correctly for utf 8? Search this list for the right settings On 30/01/2009, Philipp Daumke dau...@averbis.de wrote: Hi all, when I enter German umlauts (e.g. äöü) in a wicket text field it's converted to äöü. Everything seems to be in UTF-8. I already tried to apply a filter as described in http://wiki.apache.org/tomcat/Tomcat/UTF-8 without success. Any ideas? Thanks for your help Philipp -- Averbis GmbH c/o Klinikum der Albert-Ludwigs-Universität Stefan-Meier-Strasse 26 D-79104 Freiburg Fon: +49 (0) 761 - 203 6707 Fax: +49 (0) 761 - 203 6800 E-Mail: dau...@averbis.de Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó Sitz der Gesellschaft: Freiburg i. Br. AG Freiburg i. Br., HRB 701080 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
UTF-8 bug in wicket? Or in Tomcat?
Hi all, when I enter German umlauts (e.g. äöü) in a wicket text field it's converted to äöü. Everything seems to be in UTF-8. I already tried to apply a filter as described in http://wiki.apache.org/tomcat/Tomcat/UTF-8 without success. Any ideas? Thanks for your help Philipp -- Averbis GmbH c/o Klinikum der Albert-Ludwigs-Universität Stefan-Meier-Strasse 26 D-79104 Freiburg Fon: +49 (0) 761 - 203 6707 Fax: +49 (0) 761 - 203 6800 E-Mail: dau...@averbis.de Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó Sitz der Gesellschaft: Freiburg i. Br. AG Freiburg i. Br., HRB 701080 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Do you save it to a database and then display the text? How do you present it? -- View this message in context: http://www.nabble.com/UTF-8-bug-in-wicket--Or-in-Tomcat--tp21738467p21738754.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi Mathias, 'äöü' is actually already converted to 'äöü' when I add a breakpoint at the onSubmit method of my form (so right when I get the input of the text field from my model). My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my firefox says UTF-8. What I think is that Wicket or Tomcat treats my UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8, so into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell which is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output is 'äöü' again. Any idea what to do? All the best Philipp Do you save it to a database and then display the text? How do you present it? -- Averbis GmbH c/o Klinikum der Albert-Ludwigs-Universität Stefan-Meier-Strasse 26 D-79104 Freiburg Fon: +49 (0) 761 - 203 6707 Fax: +49 (0) 761 - 203 6800 E-Mail: dau...@averbis.de Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó Sitz der Gesellschaft: Freiburg i. Br. AG Freiburg i. Br., HRB 701080 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi Philipp, are your texts are stored in a database? Then you've got two more points where you can search: The encoding of the table and the encoding of the connection. Do you've got the same issues with the templates? Marc Philipp Daumke schrieb: Hi Mathias, 'äöü' is actually already converted to 'äöü' when I add a breakpoint at the onSubmit method of my form (so right when I get the input of the text field from my model). My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my firefox says UTF-8. What I think is that Wicket or Tomcat treats my UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8, so into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell which is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output is 'äöü' again. Any idea what to do? All the best Philipp Do you save it to a database and then display the text? How do you present it? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: UTF-8 bug in wicket? Or in Tomcat?
Hi, have you tried setting getRequestCycleSettings().setResponseRequestEncoding(UTF-8); getMarkupSettings().setDefaultMarkupEncoding(UTF-8); in your Application#init If you don't set the default markup encoding explicitly, the default for it is the 'os provided encoding' (see: IMarkupSettings#getDefaultMarkupEncoding) cheers, Jonas On Fri, Jan 30, 2009 at 1:02 AM, Philipp Daumke dau...@averbis.de wrote: Hi Mathias, 'äöü' is actually already converted to 'äöü' when I add a breakpoint at the onSubmit method of my form (so right when I get the input of the text field from my model). My whole eclipse is in UTF-8, Wicket writes UTF-8 to each HTML-Page, my firefox says UTF-8. What I think is that Wicket or Tomcat treats my UTF8-String äöü as an ISO-8859-1 String and converts it from iso to utf8, so into 'äöü'. When I copy 'äöü' into a tmp.txt file in unix-shell which is in UTF-8 and do an iconv -futf8 -tlatin1 tmp.txt on it, the output is 'äöü' again. Any idea what to do? All the best Philipp Do you save it to a database and then display the text? How do you present it? -- Averbis GmbH c/o Klinikum der Albert-Ludwigs-Universität Stefan-Meier-Strasse 26 D-79104 Freiburg Fon: +49 (0) 761 - 203 6707 Fax: +49 (0) 761 - 203 6800 E-Mail: dau...@averbis.de Geschäftsführer: Dr. med. Philipp Daumke, Kornél Markó Sitz der Gesellschaft: Freiburg i. Br. AG Freiburg i. Br., HRB 701080 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problem using UTF-8 and QueryStringUrlCodingStrategy
Hello, I'm trying to use UTF-8 as the default encoding in a web application using Wicket and Spring. Although everything seems to be working properly, I'm facing a problem when dealing with a page mounted using the QueryStringUrlCodingStrategy. The application configuration * The html pages include the meta tag meta http-equiv=Content-Type content=text/html; charset=UTF-8 / * getRequestCycleSettings().setResponseRequestEncoding() returns UTF-8 as the encoding * I've configured the Spring CharacterEncodingFilter as the first filter in the web.xml filter filter-namecharsetFilter/filter-name filter-class org.springframework.web.filter.CharacterEncodingFilter /filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param /filter filter-mapping filter-namecharsetFilter/filter-name url-pattern/*/url-pattern /filter-mapping The problem If I have a page mounted as: mount(new QueryStringUrlCodingStrategy(/search/feed, SearchFeedPage.class)); and, in another page, a link to that one: BookmarkablePageLink(feed, SearchFeedPage.class, theParameters); where theParameters include, for example, a parameter with the value día The link is correctly encoded (using UTF-8) but, once it is clicked, it is not correctly decoded. Is there something missed in the configuration? is it a bug? If, instead of using QueryStringUrlCodingStrategy I mount the page as: mountBookmarkablePage(/search/feed, SearchFeedPage.class); everything works correctly Thanks -- View this message in context: http://www.nabble.com/Problem-using-UTF-8-and-QueryStringUrlCodingStrategy-tp20325317p20325317.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket,tomcat and UTF-8
i solved it... making the steps as described in the initial post works. however make sure no calls to getparameter is done b4 the setcharencoding. i knew that, but someone had a function call for redirecting and it had a getparameter call. hence the setcharencoding wont work. all in all a error 42 thx all. -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19308386.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wicket,tomcat and UTF-8
Hi i have a problem with tomcat and wicket and UTF-8 im developing my first large wicket app. no matter what i do wicket dont seem to use the utf-8 settings i specified. the incoming request converts the incoming UTF-8 to iso-8859-1 (the default). only tried post since that what wicket uses. assume its not a problem with get. versionstomcat 6 ,wicket 1.4 ,also using hibernate 3 ive done the following; 1. specified on the connector endpoint in server.xml = URIEncoding=UTF-8 useBodyEncodingForURI=true 2. i have a filter infront of the app. setting = request.setCharacterEncoding(UTF-8); 3. i have in wicketapplikation.init = this.getMarkupSettings().setDefaultMarkupEncoding(UTF-8); ,,,this.getRequestCycleSettings().setResponseRequestEncoding(UTF-8); 4.tried adding the metatag in the header also in the html = meta http-equiv=Content-Type content=text/html;charset=UTF-8 / so wat else do i need? i made a regular servlet, setting the above settings (except the wicketapp settings offcourse). and it works just fine. somehow the request.setcharencoding gets overwritten or something. its driving me crazy plz help. thx in advance -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215411.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Wicket,tomcat and UTF-8
I had the same problem some week ago but got no answer on this list. Now I use getMarkupSettings().setDefaultMarkupEncoding(ISO-8859-1); getRequestCycleSettings().setResponseRequestEncoding(ISO-8859-1); in the Application.init() method of wicket 1.4M3. Wicket seems to ignore the XHTML header completely. Stefan -Ursprüngliche Nachricht- Von: Ray trace [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 29. August 2008 09:57 An: users@wicket.apache.org Betreff: Wicket,tomcat and UTF-8 Hi i have a problem with tomcat and wicket and UTF-8 im developing my first large wicket app. no matter what i do wicket dont seem to use the utf-8 settings i specified. the incoming request converts the incoming UTF-8 to iso-8859-1 (the default). only tried post since that what wicket uses. assume its not a problem with get. versionstomcat 6 ,wicket 1.4 ,also using hibernate 3 ive done the following; 1. specified on the connector endpoint in server.xml = URIEncoding=UTF-8 useBodyEncodingForURI=true 2. i have a filter infront of the app. setting = request.setCharacterEncoding(UTF-8); 3. i have in wicketapplikation.init = this.getMarkupSettings().setDefaultMarkupEncoding(UTF-8); ,,,this.getRequestCycleSettings().setResponseRequestEncoding(UTF-8); 4.tried adding the metatag in the header also in the html = meta http-equiv=Content-Type content=text/html;charset=UTF-8 / so wat else do i need? i made a regular servlet, setting the above settings (except the wicketapp settings offcourse). and it works just fine. somehow the request.setcharencoding gets overwritten or something. its driving me crazy plz help. thx in advance -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215411.html Sent from the Wicket - 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: Wicket,tomcat and UTF-8
i tried that ...however...then u cant use the ajax since it only uses xml utf-8 posting so that is not an option heresince i need special chars ...and allready have alot of ajax. Stefan Lindner wrote: I had the same problem some week ago but got no answer on this list. Now I use getMarkupSettings().setDefaultMarkupEncoding(ISO-8859-1); getRequestCycleSettings().setResponseRequestEncoding(ISO-8859-1); in the Application.init() method of wicket 1.4M3. Wicket seems to ignore the XHTML header completely. Stefan - -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215584.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket,tomcat and UTF-8
This is weird by defaul wicket serves out everything in utf8 (yes you should configur tomcat about the url encoding your self) Even if you say something else then ajax will be fixed to utf8 because that is the spec. Are you sure that the browser says that it is not utf8?? If you look at the page info/properties/encoding?? At our place it works fine, ofcourse we also configured all databases and databse connections to use also utf8 Johan On 8/29/08, Ray trace [EMAIL PROTECTED] wrote: i tried that ...however...then u cant use the ajax since it only uses xml utf-8 posting so that is not an option heresince i need special chars ...and allready have alot of ajax. Stefan Lindner wrote: I had the same problem some week ago but got no answer on this list. Now I use getMarkupSettings().setDefaultMarkupEncoding(ISO-8859-1); getRequestCycleSettings().setResponseRequestEncoding(ISO-8859-1); in the Application.init() method of wicket 1.4M3. Wicket seems to ignore the XHTML header completely. Stefan - -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215584.html Sent from the Wicket - 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: Wicket,tomcat and UTF-8
ino its wierd yes my browser says utf-8 . the mysql database is in utf-8. hibernate is utf-8. basically all is utf-8 except the incoming post data.arg. property name=hibernate.connection.useUnicodetrue/property property name=hibernate.connection.characterEncodingUTF-8/property database schema is created with utf-8 ...so that hibernate tools generate the correct tables. all though i dont think its hibernate causing the problems. Johan Compagner wrote: This is weird by defaul wicket serves out everything in utf8 (yes you should configur tomcat about the url encoding your self) Even if you say something else then ajax will be fixed to utf8 because that is the spec. Are you sure that the browser says that it is not utf8?? If you look at the page info/properties/encoding?? At our place it works fine, ofcourse we also configured all databases and databse connections to use also utf8 Johan On 8/29/08, Ray trace [EMAIL PROTECTED] wrote: i tried that ...however...then u cant use the ajax since it only uses xml utf-8 posting so that is not an option heresince i need special chars ...and allready have alot of ajax. Stefan Lindner wrote: I had the same problem some week ago but got no answer on this list. Now I use getMarkupSettings().setDefaultMarkupEncoding(ISO-8859-1); getRequestCycleSettings().setResponseRequestEncoding(ISO-8859-1); in the Application.init() method of wicket 1.4M3. Wicket seems to ignore the XHTML header completely. Stefan - -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215584.html Sent from the Wicket - 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] -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19215950.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket,tomcat and UTF-8
Ray trace wrote: ino its wierd yes my browser says utf-8 . the mysql database is in utf-8. hibernate is utf-8. basically all is utf-8 except the incoming post data.arg. property name=hibernate.connection.useUnicodetrue/property property name=hibernate.connection.characterEncodingUTF-8/property database schema is created with utf-8 ...so that hibernate tools generate the correct tables. all though i dont think its hibernate causing the problems. Have you tried using URIEncoding=UTF-8 in the connector tag of your tomcat server.xml ? It should be similar to the following: Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ HTH, Emanuele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket,tomcat and UTF-8
i dont think u actually read my post but thx anyways. as stated in the initial post i tried that allready. Emanuele Gesuato-2 wrote: Ray trace wrote: ino its wierd yes my browser says utf-8 . the mysql database is in utf-8. hibernate is utf-8. basically all is utf-8 except the incoming post data.arg. property name=hibernate.connection.useUnicodetrue/property property name=hibernate.connection.characterEncodingUTF-8/property database schema is created with utf-8 ...so that hibernate tools generate the correct tables. all though i dont think its hibernate causing the problems. Have you tried using URIEncoding=UTF-8 in the connector tag of your tomcat server.xml ? It should be similar to the following: Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ HTH, Emanuele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19216327.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket,tomcat and UTF-8
It's a standard tomcat problem that everybody sooner or later encounters... This will work for you: http://cagan327.blogspot.com/2006/05/utf-8-encoding-fix-tomcat-jsp-etc.html Just use the EncodingFilter and I bet my [EMAIL PROTECTED]@#$ it will work :-) Am 29.08.2008 um 11:04 schrieb Ray trace: i dont think u actually read my post but thx anyways. as stated in the initial post i tried that allready. Emanuele Gesuato-2 wrote: Ray trace wrote: ino its wierd yes my browser says utf-8 . the mysql database is in utf-8. hibernate is utf-8. basically all is utf-8 except the incoming post data.arg. property name=hibernate.connection.useUnicodetrue/property property name=hibernate.connection.characterEncodingUTF-8/ property database schema is created with utf-8 ...so that hibernate tools generate the correct tables. all though i dont think its hibernate causing the problems. Have you tried using URIEncoding=UTF-8 in the connector tag of your tomcat server.xml ? It should be similar to the following: Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ HTH, Emanuele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19216327.html Sent from the Wicket - 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: Wicket,tomcat and UTF-8
im really happy for all the help but... as stated in the top/first post i allready did all these things bro. but thx anyway Peter Ertl wrote: It's a standard tomcat problem that everybody sooner or later encounters... This will work for you: http://cagan327.blogspot.com/2006/05/utf-8-encoding-fix-tomcat-jsp-etc.html Just use the EncodingFilter and I bet my [EMAIL PROTECTED]@#$ it will work :-) Am 29.08.2008 um 11:04 schrieb Ray trace: i dont think u actually read my post but thx anyways. as stated in the initial post i tried that allready. Emanuele Gesuato-2 wrote: Ray trace wrote: ino its wierd yes my browser says utf-8 . the mysql database is in utf-8. hibernate is utf-8. basically all is utf-8 except the incoming post data.arg. property name=hibernate.connection.useUnicodetrue/property property name=hibernate.connection.characterEncodingUTF-8/ property database schema is created with utf-8 ...so that hibernate tools generate the correct tables. all though i dont think its hibernate causing the problems. Have you tried using URIEncoding=UTF-8 in the connector tag of your tomcat server.xml ? It should be similar to the following: Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ HTH, Emanuele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19216327.html Sent from the Wicket - 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] -- View this message in context: http://www.nabble.com/Wicket%2Ctomcat--and-UTF-8-tp19215411p19217648.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
UTF-8 Byte Order Marks in .html files
Hi, I found out - through a lot of trial and error - that if your .html file has a Byte Order Mark, the ?xml encoding=utf-8 ? at the top of the document is ignored. The document is treated as something else - I'm not sure what. The effect is that the special output characters become the ? unknown characters. Is this a known issue? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: UTF-8 Byte Order Marks in .html files
On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin [EMAIL PROTECTED] wrote: I think it might be your browser that is not displaying the unicode chars. That you see the odd symbols at all means that the made it to the client side. Are you on a Mac? Hi! Thanks for the reply. No, I'm on Firefox 3 on Windows. Do you have an idea why removing the BOM fixes it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: UTF-8 Byte Order Marks in .html files
Not sure what you mean by BOM (Bill Of Materials?) However I have seen something odd with documents there were generated on a Mac with little ? in various places. - Brill Pappin On 25-Jun-08, at 2:22 PM, Miguel Paraz wrote: On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin [EMAIL PROTECTED] wrote: I think it might be your browser that is not displaying the unicode chars. That you see the odd symbols at all means that the made it to the client side. Are you on a Mac? Hi! Thanks for the reply. No, I'm on Firefox 3 on Windows. Do you have an idea why removing the BOM fixes it? - 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: UTF-8 Byte Order Marks in .html files
Hi, if your editor prefixes your templates with a BOM(1), Wicket is not able to recognize the encoding in your xml declaration, see org.apache.wicket.util.io.XmlReader#xmlDecl . You might want to create a JIRA request, that Wicket should skip a leading BOM in the encoding detection. Regards Sven 1 - http://de.wikipedia.org/wiki/Byte_Order_Mark Brill Pappin schrieb: Not sure what you mean by BOM (Bill Of Materials?) However I have seen something odd with documents there were generated on a Mac with little ? in various places. - Brill Pappin On 25-Jun-08, at 2:22 PM, Miguel Paraz wrote: On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin [EMAIL PROTECTED] wrote: I think it might be your browser that is not displaying the unicode chars. That you see the odd symbols at all means that the made it to the client side. Are you on a Mac? Hi! Thanks for the reply. No, I'm on Firefox 3 on Windows. Do you have an idea why removing the BOM fixes it? - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with opening inline PDF file due to ;charset=UTF-8 in content type
Hi After upgrading from wicket 1.2.6 to 1.3 we got a problem with opening PDF files inline in a browser window. At least for some browser versions and/or PDF readers, it now opens the PDF file in a separate window instead of inline. The difference is that in Wicket 1.3 ;charset=UTF-8 is always appended to the content type. If ResourceState::getContentType() returns application/pdf, this is what I see in a HTTP debugger: Wicket 1.2.6: Content-Type: application/pdf Wicket 1.3.1: Content-Type: application/pdf; charset=UTF-8 The ;charset=UTF-8 is appended in ResourceStreamRequestTarget, and I can't see a way to override it. Any suggestions how to fix this? Niels -- View this message in context: http://www.nabble.com/Problem-with-opening-inline-PDF-file-due-to-%22-charset%3DUTF-8%22-in-content-type-tp15757124p15757124.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need XML pages in iso-8859-1 encoding ipv utf-8
I tried getMarkupSettings().setDefaultMarkupEncoding( ISO-8859-1 ); and -Dfile.encoding=ISO-8859-1 but they didn't work. Instead I used : getRequestCycleSettings().setResponseRequestEncoding(ISO-8859-1); which solves the problem. Tom Desmet wrote: Hi, I have a problem with XML page incodings. We use wicket for applications on our cisco ip phones. The firmware http client on these phones does not understand utf-8 xml. So we need to provide iso-8859-1 encoded xml responses so that the output is rendered correctly. We tried setting the correct xml header ... ?xml version=1.0 encoding=ISO-8859-1?, and the xml page is in the correct encoding. Wicket reads this page, and re-encodes it as UTF-8. So the output is no longer displayed correctly on our phones. Is there some possibility to have the output rendered as ISO-8859-1 ? -- View this message in context: http://www.nabble.com/Need-XML-pages-in-iso-8859-1-encoding-ipv-utf-8-tp14797286p14834105.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Need XML pages in iso-8859-1 encoding ipv utf-8
Hi, I have a problem with XML page incodings. We use wicket for applications on our cisco ip phones. The firmware http client on these phones does not understand utf-8 xml. So we need to provide iso-8859-1 encoded xml responses so that the output is rendered correctly. We tried setting the correct xml header ... ?xml version=1.0 encoding=ISO-8859-1?, and the xml page is in the correct encoding. Wicket reads this page, and re-encodes it as UTF-8. So the output is no longer displayed correctly on our phones. Is there some possibility to have the output rendered as ISO-8859-1 ? -- View this message in context: http://www.nabble.com/Need-XML-pages-in-iso-8859-1-encoding-ipv-utf-8-tp14797286p14797286.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need XML pages in iso-8859-1 encoding ipv utf-8
hi tom, Wicket reads this page, and re-encodes it as UTF-8. So the output is no longer displayed correctly on our phones. Is there some possibility to have the output rendered as ISO-8859-1 ? on intializing your application try setting getMarkupSettings().setDefaultMarkupEncoding( ISO-8859-1 ); regards, --- jan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need XML pages in iso-8859-1 encoding ipv utf-8
I have a problem with XML page incodings. We use wicket for applications on our cisco ip phones. The firmware http client on these phones does not understand utf-8 xml. So we need to provide iso-8859-1 encoded xml responses so that the output is rendered correctly. We tried setting the correct xml header ... ?xml version=1.0 encoding=ISO-8859-1?, and the xml page is in the correct encoding. Wicket reads this page, and re-encodes it as UTF-8. So the output is no longer displayed correctly on our phones. Is there some possibility to have the output rendered as ISO-8859-1 ? If you can, maybe you could just start the jvm with: -Dfile.encoding=ISO-8859-1 I think that will solve your problem. -- Edvin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
