It seems that the ResourceBundleMessageProvider and the XMLMessageProvider
behaves differently when an entry does not exist in a non-default language.
With ResourceBundles, if I have an entry, say
helloWorld.notTranslated=This entry is not translated to any other languages
that only exists in t
> [mailto:[EMAIL PROTECTED]
> Im Auftrag von Mattias J
> Gesendet: Donnerstag, 21. April 2005 15:41
> An: commons-dev@jakarta.apache.org
> Betreff: [i18n] Providers behave different
>
> It seems that the ResourceBundleMessageProvider and the XMLMessageProvider
> behaves dif
l 2005 15:41
> An: commons-dev@jakarta.apache.org
> Betreff: [i18n] Providers behave different
>
> It seems that the ResourceBundleMessageProvider and the XMLMessageProvider
> behaves differently when an entry does not exist in a non-default
> language.
> With ResourceBundles, if I have an ent