best way for handling i18n
Can anybody tell me the best way of handling i18n in struts2. The problem is everyone is using their own properties files for internationalization due to which messages are conflicting with each others properties file even i only have 4 properties files and my own messages are conflicting . So can anyone please tell me the right way for handling internationalization.. if we'll keep only one properties file for internationalization then it become really really huge . So what can be the alternate Please Please tell me the solution.. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: best way for handling i18n
akshi gupta wrote: Can anybody tell me the best way of handling i18n in struts2. The problem is everyone is using their own properties files for internationalization due to which messages are conflicting with each others properties file even i only have 4 properties files and my own messages are conflicting . So can anyone please tell me the right way for handling internationalization.. if we'll keep only one properties file for internationalization then it become really really huge . So what can be the alternate Please Please tell me the solution.. How are your messages 'conflicting'? Struts2 supports multiple properties files which can be placed in several different locations to facilitate sharing messages between all the actions in a package or package hierarchy, among other possibilities. See the Localization documentation for more info: http://struts.apache.org/2.x/docs/localization.html If that doesn't help, post again describing how you have your messages organized currently and exactly how that's causing you problems. L. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
回复:best way for handling i18n
use the custome 标签 在2008-01-22，"akshi gupta" <[EMAIL PROTECTED]> 写道： >Can anybody tell me the best way of handling i18n in struts2. > >The problem is everyone is using their own properties files for >internationalization due to which messages are conflicting with each >others properties file even i only have 4 properties files and my own >messages are conflicting . > >So can anyone please tell me the right way for handling >internationalization.. > >if we'll keep only one properties file for internationalization then it >become really really huge . > >So what can be the alternate > >Please Please tell me the solution.. > >Thanks. > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > >
