Schnitzer, Jeff wrote:
I've been thinking more and more about using XSL at compile-time to
generate Velocity templates which have all the header, navbar, etc type
formatting. It seems like it would be easy to add an
internationalization step too. This would probably offer more
flexibility than
Jaap van Hengstum wrote:
Again, correct me if I'm wrong :-)
But what if there would not be just one message but instead one
message (selected at runtime) out of a possible number of messages. The
view would then have to either [1] select the localized message at
runtime or [2] include every
Kevin O'Neill wrote:
Having been a cocoon user for a long time XSLT is something that the
majority of developers will never get. It's a big mind shift from an
imperative to a functional language. So I would caution against exposing
XSLT to the masses. On the other hand if the xml to X/HTML where
It might be fun to setup a small library of some basic website styles
that other could crib. Like the starter templates that ship with things
like FrontPage and DreamWeaver. Header, Footer, Menu at the left. Menu
at the top and bottom, and so forth
I'm into that. I might even be able to
be possible to include different xsl
based on the locale.
-Oorspronkelijk bericht-
Van: Aapo Laakkonen [mailto:[EMAIL PROTECTED]
Verzonden: Tuesday, September 23, 2003 4:11 AM
Aan: [EMAIL PROTECTED]
Onderwerp: [Mav-user] I18n/l10n
I would like to know what do you think is the best way
At the moment, I use a combination of (1) and (2).
A disadvantage of (4) - if I see it correctly -
is that I create messages at runtime (f.e. validation
error messages) and it would be more complicated in
the view if I had to create them at compiletime.
Yes, but as I see those validation
something I was thinking about since your
build-time approach looks interesting enough to consider.
-Oorspronkelijk bericht-
Van: Aapo Laakkonen [mailto:[EMAIL PROTECTED]
Verzonden: Tuesday, September 23, 2003 12:54 PM
Aan: [EMAIL PROTECTED]
Onderwerp: RE: [Mav-user] I18n/l10n
At the moment, I
PROTECTED]
Onderwerp: RE: [Mav-user] I18n/l10n
At the moment, I use a combination of (1) and (2).
A disadvantage of (4) - if I see it correctly -
is that I create messages at runtime (f.e. validation
error messages) and it would be more complicated in
the view if I had to create them
: [EMAIL PROTECTED]
Onderwerp: [Mav-user] I18n/l10n
I would like to know what do you think is the best way to write
localized messages in web application. I have a few possibilities:
1. Servlet Filter (outputstream search/replaces)
2. Resource Bundles
3. Database lookups
4. Ant task that does
From: Aapo Laakkonen [mailto:[EMAIL PROTECTED]
I would like to know what do you think is the best way to write
localized messages in web application. I have a few possibilities:
4. Ant task that does the replaces and deploys each
language in it's own dir and then use Maverick's
I would like to know what do you think is the best way to write
localized messages in web application. I have a few possibilities:
1. Servlet Filter (outputstream search/replaces)
2. Resource Bundles
3. Database lookups
4. Ant task that does the replaces and deploys each
language in it's own
11 matches
Mail list logo
