The bottom-up search for messages is how Tapestry is looking for
translations now. But the problem is that we are talking about replacing
existing translation. Tapestry stops searching when the component's message
catalog contains a particular key. You need somehow to tell Tapestry to
continue sear
I'll take a look at it, once I've closed my other ticket(s).
Robert
On Dec 5, 2009, at 12/59:00 AM , Joost Schouten (ml) wrote:
Hi,
Could one of the comitters have a look at the provided patch at: https://issues.apache.org/jira/browse/TAP5-937
?
Is it possible to get it included in T5.2.0
Unless you put the definitions in your application's app.properties,
right? Then you still have to provide the custom resources component-
by-component, but the translations go in a single place.
Robert
On Dec 7, 2009, at 12/75:53 PM , Igor Drobiazko wrote:
Hm, what about components that are
Hm, what about components that are used in several pages? In this case I
have to repeat the translations again and again.
On Sun, Dec 6, 2009 at 9:02 PM, Howard Lewis Ship wrote:
> Perhaps what's really needed is for components to more frequently have
> a parameter used to override its internal
Congrats!
On Mon, Dec 7, 2009 at 10:31 AM, wrote:
> Author: uli
> Date: Mon Dec 7 18:31:35 2009
> New Revision: 888068
>
> URL: http://svn.apache.org/viewvc?rev=888068&view=rev
> Log:
> Add myself (Ulrich Stärk) to the committers lists.
>
> Modified:
> tapestry/tapestry-site/trunk/pom.xml
>
On Sun, Dec 6, 2009 at 9:02 PM, Howard Lewis Ship wrote:
> Perhaps what's really needed is for components to more frequently have
> a parameter used to override its internal messages with a new messages
> object (presumably form the page).
Yep, that should be the solution if not limited to the c
