Ron, Thanks for the response. I just found it, it was lost in my e-mail inbox.
My issue is that I have one page for the entire system. What I wanted to avoid was having a seperate .properties for every component (75 at last count). It make internationalization more difficult. Thanks for telling me about the page, I will have to think about what is the best way to handle it. regards, Mark -----Original Message----- From: news on behalf of Ron Piterman Sent: Wed 10/5/2005 9:26 AM To: [email protected] Subject: Re: 3.0.3 Component Localization In Tapestry 3 AND in tapestry 4 each component has its own .properties file for its resources. You could however access the messages of your page using the ognl page.getMessage('key') but you can not use <span key="..."> in your template in this way... Cheers, Ron PS - I would consider the design you are using. If a component is to be used only in one page, you could use a block instead. A Part of the Idea of a component is that you can drop it everywhere... ????? Mark Stang: > Hi, > I am using 3.0.3 and it appears that I must localize at the component level. > I have a single page and I can localize there for "page" specific stuff, > however, when I try and localize at the component level it seems to require a > .properties file for each component. Is this true? > > thanks, > > Mark > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
