tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Assaf Arkin <>
Subject Re: request for comments about Multilinguage JSP
Date Fri, 18 Feb 2000 00:08:51 GMT
You definitely need to cater to both needs. Case in point, you might
have two stylesheets that are almost identical, except for the corporate
logo. Or you might have one stylesheet for online viewing (very
elaborate) and one for printing (very simple).

In my opinion what would work best is if you could select which one to
use based on the client characteristics, or supply them to the XSLT
transformer to apply the proper stylesheet template.

I like Eugene's proposal to have multiple stylesheets, one for each
characteristic. Not as the only solution, but a definite one for cases
that need it.

As a side issue, how about a different stylesheet based on the user's
role. Let's say I have the same common page for both Internet users and
company employees, but company employees get additional links to
Intranet resources.

The role-based security prevents Internet users from reaching these
pages, but I would rather not expose the links to these users.

If I choose to use XSLT, it should be aware of the role when applying
the transformation.

Just a thought.


Eduardo Pelegri-Llopart wrote:
> In many cases the data starts from some single source (say the database)
> and ends up being differentiated based on a number of reasons; let's say
> based on client characteristics for this - that could be supported
> language, or it could be a WAP device vs an HTML browser.
> I don't know where the practical boundary lies between transforming some
> common representation and starting afresh.  I doubt any of us really
> knows given how little experience there is with the differnt
> mechanisms.  If the transformation is very deep it seems to me it may be
> easier to start afresh.  Anyhow, we will find out as we try things out,
> that is why we like our jobs, right?
> A response to the original question in a separate mail.
>         - eduard/o
> Assaf Arkin wrote:
> >
> > I totally agree. And also produce text from within Java code (Java 1.2
> > supports that nicely).
> >
> > But if you need database or progamattic messages, you still end up
> > having one JSP page supporting multiple languages.
> >
> > The point that was raised is whether multiple JSP pages, one for each
> > language, makes sense. XSLT solves that. Java code (and JSP beans) solve
> > the remaining issues.
> >
> > arkin
> >
> > Benson Margulies wrote:
> > >
> > > I don't think that it is realistic to assume that all the text in a
> > > multilingual application will surface via XLT. A JSP/servlet may need to
> > > pull strings from a database based on language.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > For additional commands, e-mail:
> >
> > --
> > ----------------------------------------------------------------------
> > Assaf Arkin                                 
> > CTO, Exoffice Technologies, Inc.              
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Assaf Arkin                                 
CTO, Exoffice Technologies, Inc.              

View raw message