Mailing-List: contact users-help@wicket.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@wicket.apache.org
Received-SPF: pass (athena.apache.org: domain of
 tomwnorton.mailing.lists@gmail.com designates 209.85.214.172 as permitted
 sender)
MIME-Version: 1.0
From: Tom Norton <tomwnorton.mailing.lists@gmail.com>
Date: Wed, 31 Jul 2013 11:44:52 -0400
Message-ID: 
 <CA+-Pn+wy4q=01+jDG-F_5ThvjSJuKJw-_j9yHJy0XQC2jrYbhQ@mail.gmail.com>
Subject: Wicket Content Parameters
To: users@wicket.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff242a379753904e2d09cc8

--e89a8ff242a379753904e2d09cc8
Content-Type: text/plain; charset=ISO-8859-1

We just received our content back from our translators.  They translated
everything correctly for our velocity templates.  However, when they
translated our wicket content, they also translated the parameters (one
translator even replaced the curly braces with parentheses).

Does anyone know it it's possible to use the ${...} syntax for content
parameters instead of {...}?  I ask because most translators already know
to steer clear of the ${...} syntax, since it's the de facto syntax for
parameters embedded into strings.

Thanks,
Tom

--e89a8ff242a379753904e2d09cc8--