Localization priority stack

Hi,

We are trying to implement a way to allow users to customize descriptions in 
the enumeration tables. One barrier is the fact that the resource bundle takes 
priority over the value of the description in the database.

What we would like to do is change it such that the description values in the 
database will initially be NULL. If this is the case, then we would pull the 
localized value from the resource bundle. If it is not the case, then we would 
use the value in the database. If we ever attempt to get something from the 
resource bundle and fail to find the value in the user's current locale, we 
would then grab the default system locale value.

Now we know this would affect all the fields that are being localized at the 
entity level, but are wondering if anyone suspects this will affect anything 
else adversely.

Alternatively, we could also add a new layer onto this stack that represents 
user preferences. And we could use this to specify custom descriptions for the 
user. And this would then take priority over the resource bundle.

Thanks in advance,
Andrei Tulai