Hi Ryan, hi Kent,
thank you for the feedback !
So I think using the 'good, old' solution to split the sentence into 3 parts
would be the lesser evil :)
Until there is a solution provided by Tapestry directly, like
'messages.parseMessage()' ?
So it could be possible to include a simple component-id into the .properties
file
Maybe
Please click {myComponentId} here {/myComponentId} to register.
expanded to
Please click <span jwcid="myComponentId"> here </span> to register.
So the component parameters have to be specified in the .jwc/.page.
Ups ... sorry, im zoning out ... ;)
Thanks again !
Gerald
Kent Tong wrote:
>The only solution that I can think of is to use a separate html
>for each language. Then you don't need the .properties files
>and the whole sentence will be in the html file.
>
>If you'd like, you can still use the .properties files even if
>you use multiple html files.
Ryan wrote:
>Where {0} is replaced with <a href=3D"..."> and {1} with </a>. This has
>the nasty side effect of not being able to 1) specify the sentence in
>the html template, 2) not being able to create a link within a
>sentence that is composed of a tapestry component and 3) just plain
>annoying. It would be nice if tapestry had some mechanism to make this
>easier to deal with (fully understanding other frameworks have similar
>issues).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
