Strange problem with I18N keys in xml resource bundle

2010-07-20 Thread Thomas Götz
I have a strange problem with an I18N key which is stored in an xml resource bundle. I try to set the following keys for a german translation: - PagingNavigator.first - PagingNavigator.previous - PagingNavigator.next - PagingNavigator.last - PagingNavigator.page I noticed that wicket already

Re: Strange problem with I18N keys in xml resource bundle

2010-07-20 Thread Ernesto Reinaldo Barreiro
Maybe because the key should be PagingNavigation.page? Ernesto On Tue, Jul 20, 2010 at 10:19 AM, Thomas Götz t...@richmountain.de wrote: I have a strange problem with an I18N key which is stored in an xml resource bundle. I try to set the following keys for a german translation: -

Re: Strange problem with I18N keys in xml resource bundle

2010-07-20 Thread Thomas Götz
On 20.07.2010 10:53, Ernesto Reinaldo Barreiro wrote: Maybe because the key should be PagingNavigation.page? Ha! Nice one, thanks ;-) The naming is a little bit inconsistent IMHO. -Tom - To unsubscribe, e-mail:

Re: Strange problem with I18N keys in xml resource bundle

2010-07-20 Thread Ernesto Reinaldo Barreiro
Tomas, It might be because PagingNavigation.page is read from within PagingNavigation component. Maybe it is consistent in the sense that it refers to the component using the resource. I don't know if a convention is followed for these things on core components? By the way... Would it be a good

Re: Strange problem with I18N keys in xml resource bundle

2010-07-20 Thread Thomas Götz
On 20.07.2010 12:40, Ernesto Reinaldo Barreiro wrote: Tomas, It might be because PagingNavigation.page is read from within PagingNavigation component. Maybe it is consistent in the sense that it refers to the component using the resource. I don't know if a convention is followed for these