Keith Sader wrote: >> But, I didn't know what to do with more complex messages, which may be >> multiple paragraphs, with HTML, images, links, etc. And may contain >> Struts/JSTL tags too.[...] >> In that directory, we place JSP files that contain the more complex >> messages. In the ApplicationResouces.properties file, we specify a URL to >> the file containing the complex message. >> > > Ok, I think you're making too much work for yourself. If I understand > it(I8N) correctly, the only thing one really has to do is name all of > those .properties files with the right country code, insert the > translated text with the correct subsitution placeholders, and > presto, the magic container will render the correct stuff for you. > I think the point was that it wasn't simply an issue of I18Ning prompts, but rather the entire page (or chunks) could change. For various language, cultural, or use-case reasons this makes sense.
For a never-deployed app we used the same idea of adding a locale extension to the name of JSP files (which IIRC tied into some twisted tile processing code???) so we had home_en.jsp, home_jp.jsp, form1_en.jsp, etc. Somehow or another the Right Thing happened but I'll be darned if I remember how at this point, rendering this post OT :/ Dave
