But this global message catalog (aka the namespace catalog) is documented to be working in 3.x. I'm using 3.0.3 and it doesn't seem to work. Another user on this list has reported the same problem.
So this shouldn't be considered a change infunctionality, right? or is the documentation wrong & it's only a 4.x feature? Thanks, - Mike Howard Lewis Ship <[EMAIL PROTECTED]> 12/14/2005 09:41 AM Please respond to "Tapestry users" <[email protected]> To Tapestry users <[email protected]> cc Subject Re: I18N 3.x vs. 4.x The only change is that there is now a global message catalog for the entire application, which is used when a particular message key is not found in the message catalog for an individual page or component. On 12/14/05, Mark Stang <[EMAIL PROTECTED]> wrote: > Hi, > Has the mechanism for internationalization changed from 3.x to 4.x? > > We may have to and I need to know if I should convert to 4.x before or after I internationalize. > > And how much trouble has it been to internationalize applications? > > thanks, > > Mark > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
