This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Globalization with XSL-XML
- To: xsl-list at lists dot mulberrytech dot com
- Subject: RE: [xsl] Globalization with XSL-XML
- From: timw at 3d3 dot com
- Date: Wed, 14 Nov 2001 09:47:44 +1100
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi Annalisa,
There are lot of issues in localization, not only the language itself, but
also the display of numbers, the way the page is read (Left to right/right
to left and top to bottom/bottom to top), date display and more.
http://aspn.activestate.com/ASPN/Cookbook/XSLT/Recipe/65427 has a method of
replacing language tags using an XML of translated strings included using
document()
I have developed an XML file of currencies with number display which I would
be happy to supply you with if you would like.
The pages I am currently developing use automatic translation between German
and English, although as Jim Fuller pointed out in his post, pre-parsing
will probably give a quicker response, with a folder for each language.
Tim Watts
> -----Original Message-----
> From: Annalisa Ricci [mailto:Annalisa.Ricci@loria.fr]
> Sent: Tuesday, 13 November 2001 9:17 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] Globalization with XSL-XML
>
>
> Hi all,
>
> I would know your opinion about the handling
> of multilinguistic Web sites with XML and XSL.
>
> For example, are they convenient for handling Web applications
> (see Input Forms) that can dynamically change their display, adapting
> themselves to different languages and countries?
> And how to handle multilanguage inputs?
>
> Why to choose XML-XSL and not, for ex., the Java properties?
>
> There is someone that could tell me his opinion and/or redirect me to
> a web site?
>
> TIA,
> Annalisa
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list