Yaroslav, You just threw in Tiles into the mix ! Can't suggest anything haven't used it yet. Perhaps you can rephrase exactly what you'd like to do and use.
- Glenn On 6/24/05, Yaroslav Novytskyy <[EMAIL PROTECTED]> wrote: > Wow! > > meanwhile I've had the same idea. Posted simultaniosly :) > > But I doubt, that this solution will be compatible with tiles :( > > What do you think about that? > > Best regards > Yaroslav Novytskyy > > > > Jeff Beal wrote: > > Probably your best bet would be to use a custom ActionMapping and > > override the findForward() method to return a Locale-specific JSP > > page. > > > > On 6/24/05, Yaroslav Novytskyy <[EMAIL PROTECTED]> wrote: > > > >>Hi! > >> > >>This is exactli what I'd like to avoid and use l10n on pages level not > >>level of defined strings in message bundles for different languages. I > >>don't want to use the english (html) design and to translate english > >>phrases to french, which will be included into english design. I want to > >>use french _page_. That meens french design with includes french text - > >>standalone french jsp. > >> > >> > >>Martin Gainty wrote: > >> > >>>Glenn et al > >>>Another option for Struts localisation is to embed your language > >>>specific strings typically with key="string" defined within your > >>>ApplicationResources_language_country.Properties file > >>>struts-config.xml will reference <message-resources> for key-based tag > >>>or <param-value> (initialisation param) for your servlet for > >>>ApplicationResources (properties) file > >>>When these elements are configured properly in struts-config.xml then > >>>your bean-write will work with <html-messages> > >>>Take a look at this excellent tutorial located at > >>>http://www.systemmobile.com/articles/strutsMessageResources.html#creating-bundle > >>> > >>>Bon Chance, > >>>Martin- > >>>Etats Unis > >>>001-617-852-7822 > >>>----- Original Message ----- From: "Glenn Deschênes" <[EMAIL PROTECTED]> > >>>To: "Struts Users Mailing List" <user@struts.apache.org> > >>>Sent: Friday, June 24, 2005 9:52 AM > >>>Subject: Re: I18N by pages > >>> > >>> > >>>What you can do is have a jsp for each locale language such as > >>>page_fr.jsp and page_en.jsp. > >>> > >>>Your application can store the locale in the user's session object. > >>>Your application can update the session locale when the user switches > >>>between en & fr. > >>> > >>>You can have the following forwards for the action in the > >>>struts-config.xml: > >>><forward name="en" path="/WEB-INF/page_en.jsp"> > >>></forward> > >>><forward name="fr" path="/WEB-INF/page_fr.jsp"> > >>></forward> > >>> > >>>In your ActionForm you can: > >>>return mapping.findForward(get the locale language from the session); > >>> > >>>HTH, > >>>Glenn > >>> > >>>On 6/24/05, Yaroslav Novytskyy <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>>Hello, all! > >>>> > >>>>I just wonder if there is an existing (tested, prooved) way (a kind of > >>>>development pattern) for Struts to make internationalization not by > >>>>message resources but by pages (JSPs, templates)? > >>>> > >>>>The point is that using message resources deleloper can only define a > >>>>string value for different locales. For example for "en" welcome=aaa > >>>>for "fr" welcome=bbb, and you include it like <title><out > >>>>"welcome"></title>. This produces "<title>aaa</title>" for "en" and > >>>>"<title>bbb</title>" for "fr". > >>>> > >>>>That makes you limited to localizing only strings, but not the format. > >>>>E.G. I would like to output "<title>aaa</title>" for "en" and > >>>>"<h1>bbb</h1>" for "fr". And this not the matter of defining this > >>>>strings (<h1>bbb</h1>) in message bundles, but I would like to use > >>>>separate JSPs for "en" and "fr" and that is the point. I would like have > >>>>two jsp files: page1.en.jsp with content of "<title>aaa</title>" and > >>>>page1.fr.jsp with "<h1>bbb</h1>". (P.S. this reduces much (maybe even > >>>>terminates) the mess with message bundles). > >>>> > >>>> > >>>>Please write all your suggestions and thoughts. > >>>> > >>>>Best regards > >>>>Yaroslav Novytskyy > >>>> > >>>>--------------------------------------------------------------------- > >>>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>>For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>> > >>>--------------------------------------------------------------------- > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>>--------------------------------------------------------------------- > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >> > >>--------------------------------------------------------------------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
