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