On 11/21/05, Matej Knopp <[EMAIL PROTECTED]> wrote: > Having a component on every place localized text is, doesn't seem to be > a very good solution for me. As well as not be able to localize button > captions. > > The solution I've chosen was to translate the markup during parsing > (using my own modified MarkupParser). This solution works quite well for me. >
what kind of translation? Are you replacing placeholder? So it is similiar to the wicket:message thing we recently introduced? Juergen ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
