You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Gregory Entin <gr...@auktion24.ru> on 2000/07/08 12:51:41 UTC

Localization using XSL's

Does anybody have experience localizing websites with XSL?

What is good approach for this:

1. Having a set of XSL's per language
2. Having localized messages attached to main XML
3. Having imported XSL with named templates that are called from page
template
4. Having additional XML that is attached to XSL via documnet() function and
selecting message by <xsl:value-of
select="$messages/message[@name='msg33']"/>.

First is very simple, but hard to manage. Second is not good because it will
parse localized message for each request. Number 3 is OK, but I am not sure
if performance is good (haven't tested yet), and also localization in XSL
template do not look nice to edit it.
Number 4 has perfect localized messages data structure, but is not very fast
as XALAN should process XML for each request. Does anybody know the way to
preload XML into variable namespace of XSL? Then it will be perfect
solution.

Best regars,

Gregory Entin
Auktion24 development

Email: entin@auktion24.ch
Pager: 5841@pager.sibpage.ru, operator 186555
Addr:  pr. Lavrent'eva 6-214, Novosibirsk, Russia 630090
Tel:   7 3832 396297 (office)
       7 3832 301412 (home)