On 17-06-2008 at 23:30, Will Hartung wrote: > > On Jun 17, 2008, at 9:28 PM, Oscar Westra van Holthe - Kind wrote: > > > > Or if you prefer not to do that, you can (ab)use that hierarchy by > > overriding > > the Locale to use: as soon as the customer is identified, add a > > variant to > > the Locale.
[...] > Clever I like it. > > But does it have the granularity at the string level? i.e. if I have > a StripesResource_en_US_myCustomer.properties, and it doesn't have > "msg.nextpage", will it walk the hierarchy to find the message or > will it stop because it found a property file, even tho it may not > have the message? > > That I don't know. As it happens, I do know: for simple applications, I use two .properties files: translations.properties translations_nl.properties Only the former contains the configuration for DisplayTag, like which export to support, etc. and both contain the translations. And since DisplayTag wёrks as expected for the dutch (nl) language, I know that the granularity is indeed at the String level. Oscar -- ,-_ /() ) Freedom is a willingness to accept consequences. (__ ( =/ () ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
