Hi,
Just wondering how this should be handled without DRY.
In many scenarios we have multiple languages that should have the same
markup but different text. This could be handled by using variation and put
every language in an own html file like myWicketPage_style_en.html.
However, this is not
Create a panel with just the markup you need and switch them out with
the isvisible based on the current language needed? Similar to the post
for Re: Adding/Replacing links in Panels by Michael Sparer below. I
use WebMarkupContainer, but I only have two states. 14 may get a little
messy
Ideally the markup should stay in the markup file and the text in that
markup that needs to be localized would be localized via wicket:message and
a properties file. In cases like below, you would break the text into
properties-localized hunks and into panels with multiple markup localization
We use a combination of the following for that sort of l10n/i18n.
1. wicket:message
2. A Label with a StringResourceModel, and setEscapeModelStrings(true)
3. Fragments
Scott
On Fri, Feb 13, 2009 at 8:16 AM, Warren Bell warrenbe...@gmail.com wrote:
Create a panel with just the markup you need
It would be a lot of split ups in the properties files and a lot of
wicket:message but I guess it is the best way when separation markup from
pure text.
This is always a problem. I'm dealing with the same concern when a user
want's to add html markup to a news that is saved in the database.
