> NB: http for non-committer/anonymous access!
You can read from it as far as I know. Just not commit :-) But indeed,
you probably want http instead.
Eelco
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-m
On Friday, October 5, 2007, 6:53:51 PM, Eelco <[EMAIL PROTECTED]> wrote:
>> Thanks so much, Eelco :-). I can't find the new example, however... Where
>> did you commit it? It doesn't show at the examples page
>> (http://wicketstuff.org/wicket13/). I've also tried an URL similar to pub,
>> but it i
> Thanks so much, Eelco :-). I can't find the new example, however... Where
> did you commit it? It doesn't show at the examples page
> (http://wicketstuff.org/wicket13/). I've also tried an URL similar to pub,
> but it isn't there.
You'll have to get it from our subversion repo:
https://svn.apach
ew this message in context:
http://www.nabble.com/Best-approach-to-localization-tf4572706.html#a13064155
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> Best way to go is probably to use tags for static
> blocks that need to be localized.
To illustrate that, I just committed an alternative implementation of
pub (called pub2). Please look and compare! :-)
Eelco
-
To unsubscrib
> the *pub* example (http://wicketstuff.org/wicket13/pub/) shows how a
> localized string can be retrieved from a properties file and then
> dinamically inserted in a page. Still, with the exception of that string,
> the remaining markup is kept static, which results in separated, localized
> HTML
even though it allows
the production of a single HTML file for all locales, obviously has a higher
development cost... Would the benefit be high enough to justify that choice?
Thanks so much,
Cristina
--
View this message in context:
http://www.nabble.com/Best-approach-to-localization-tf4572706
