hi,
it is good idea but recently I was thinking more about the functionality
that you can have a special marker or global function that gets String and
then tapestry will produce properties file for you and replace those
markers/function with ${message:whatever} so it can be easily translated.
from my point of view every text in the view that need to be translated
needs its own unique identifier and I dont really care if this descriptive
name or just a number. even if now I have 2 label with the same text it
doesnt mean it will not change in the future.
I think it would be really nice to see a text in tml file rather than
${message:aName}
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski....@gmail.com
______________________
On 5 February 2010 00:39, Thiago H. de Paula Figueiredo
<thiag...@gmail.com>wrote:
> On Thu, 04 Feb 2010 21:33:03 -0200, Christoph Jäger <
> christoph.jae...@polleninfo.org> wrote:
>
> Hi,
>>
>
> Hi!
>
>
> It would be a great help, if t:Label would first search for a property
>> like "name-label", and, if none is found, for "name" (without the trailing
>> "-label").
>>
>
> This logic is implemented in the ComponentDefaultProvider service,
> specifically its defaultLabel(ComponentResources resources) method. You can
> advise it so it uses any logic you want.
>
>
> Is there a good reason not to enhance t:Label to do this? How can I help
>> to get this implemented (in case I am not the only one who thinks this would
>> be a good idea)?
>>
>
> I think it could be a good idea. Please post a JIRA for that.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and instructor
> Owner, software architect and developer, Ars Machina Tecnologia da
> Informação Ltda.
> http://www.arsmachina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
