Diego Manilla Suárez schrieb: > Michael escribió: >> Diego Manilla Suárez schrieb: >> >>> Hi. I'm using displaytag on a web app which lets the user switch the >>> display language. I've set the locale provider to I18nJstlAdapter, and >>> whenever the user switches languages, I invoke <fmt:setLocale> tag. I >>> have two configuration files, displaytag_en.properties and >>> displaytag_es.properties. >>> >>> The problem is if I switch from English to Spanish, the titleKeys >>> attributes change, but some other attributes don't. For example, if I >>> have something like this: >>> >>> <display:table name="searchResults" uid="searchResults"> >>> <display:column titleKey="text.search.result.title" property="title" /> >>> </display:table> >>> >>> The title of the column will show in Spanish just fine. But, if there >>> are no results, the basic.msg.empty_list will shown is the one from >>> displaytag_en.properties, instead of displaytag_es.properties. >>> >>> What's the problem here? >>> >> Hi Diego, >> >> did you supply the empty list property in the en *and* es bundle? >> If you didn't supply in es then displaytag loads the default properties >> from the jar file. >> >> Mike >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> displaytag-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/displaytag-user >> >> > Hi Michael, thanks for your help. > > Yes, I have that property in both files. When I set the default language > of my browser to Spanish, the basic.msg.empty_list property is correctly > loaded and displayed in Spanish. It seems that Displaytag is using the > locale provider for loading title keys but it always used > request.getLocale() for other properties. I don't know if this makes > sense, I'll keep investigating.
Yes, if no matching bundle is found displaytag tried request#getLocale which is undesired because result is faulty. You end up in the wrong locale. You should create a displaytag.properties and put all base props there for those locales which aren't found by displaytag_<lang>.properties. Mike ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ displaytag-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/displaytag-user
