Build your properties files using you local (latin 2) encoding so that
you don't need to put any escaped characters in. Then, as part of the
build pocess run native2ascii on all of the properties files to get all
the extended characters correctly escaped.
regards,
Chris
Matej Knopp wrote:
Hi,
there's a big discussion today about customizing validator
messages/their resource keys. Would it be possible in future to
decouple the messages from property files? I think resource bundle is
a good thing, when you are using latin 1. For all other encoding is a
pain, because you have to escape each foreign character. In my
country, we are using latin 2 and a lot of characters not found in
latin1. So using property files for this feels really cumbersome.
Would id be possible to have an interface with function similiar to this?
interface IMessageProvider
{
String getString(Component component, String path, Locale locale);
}
With a reasonable default (caching) implementation that would use
property files?
And I one could use different implementation (with xml or whatever)
-Matej
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
