Hi, I was just wondering why StringResourceModels and wicket:message tags handle umlauts (mutated vowels) such as the German ö, ä or ü differently. More precisely, if a put the following word into a properties file (I used a $ instead of the & to prevent browsers and mail-clients taking this as html ;-)):
M$auml;nner StringResourceModel's output is: M$auml;nner (in the Browser) and M$amp;auml;nner (in HTML) whereas wicket:message's output is: Männer (in the Browser) and M$auml;nner (in HTML) obviously StringResourceModel escapes the special characters and wicket:message doesn't. It isn't that big problem that keeps my project stuck, but I'd like to know if this is a desired behaviour and what the wicket-way to handle umlauts in property files would be like ----- Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/StringResourceModel-and-wicket%3Amessage-tag-handle-umlauts-differently-tp14602077p14602077.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]
