Please post Tapestry developer questions to the mailing list for best response.
There has been a discussion about simplifyin localization in the manner discussed. In short, each component would have an optional ResourceBundle (i.e., set of properties files) and a new property, or binding type, to expose them. Some details need to be worked out, however. In the meantime, you can write code, like the Workbench Border component, to accomplish the same thing. And, of course, Tapestry will let you mix and match solutions. One of the advantages of Tapestry's multiple-template solution is that it can support alternate layouts ... for example, a Hebrew or Arabic page could be laid out right to left and appear more natural to a native user. -- [EMAIL PROTECTED] http://tapestry.sf.net > Hi Howard, > > we just stared to implement with tapestry and we're on a beginners level. So > sorry if you have already answered this > question. But I searched since a day for an answer and could not find one. We > are thinking about localization and we > only found the way over the html's. I thought there is also the possibilie to > make localized properties files. Yes, I > have seen the stuff in the border example. But is it not possible to refrence a > text directly out of the localized > properties files ? It would be very helpfull e.g. for labels to only maintain > some properties fiels for a sreen instead > of having n times the same HTML only with other label text's. We know that we > can load the properties file into a bean, > but we want to reference the properties in the jwc file directly with out using > a bean. > > Thans for you help in advance. > > Regards Sascha > > ------------------------------- > Sascha Freitag > > objtec gmbh > Spisergasse 32 > 9000 St. Gallen > Tel +41 (0)71 230 32 22 > Fax +41 (0)71 230 32 24 > Mobile +41 (0)79 752 42 00 > > >
