I'd like to improve the national language support in Jetspeed. The idea is
pretty simple:
* We write a set of templates for each language.
* The templates are moved into respective subdirectories (e.g.
templates/jsp/en/{layouts,navigations,screens} for JSP templating and
english language).
* The JetspeedSesionValidator adds the language to the user's TempStore.
This could be the user agent's preferred language and as a fallback the
locale.default.language setting in TR.p.
* The template system is modified to use the user.getTemp("locale") for
searching the templates in the respective subdirectory (I think subclassing
the TurbineTemplateService is the easiest way of doing this). We can have a
set of default templates that'll be choosen if the language specific
template directories don't contain the requested template. (E.g. for the
Ecs screen template, as this it 100% language independent)
Comments, want me to develop this (Shouldn't take too long ;-))?
ingo.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?: [EMAIL PROTECTED]
