Re: [xsl] XSLT (2) namespace safe i18n patterns

Subject: Re: [xsl] XSLT (2) namespace safe i18n patterns
From: Jirka Kosek <jirka@xxxxxxxx>
Date: Tue, 24 Nov 2009 20:31:57 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Odling-Smee wrote:
>> xml:lang is all about mixing languages in the same file, however that
>> often causes more problems than in solves, and far better to have one
>> language per file.
> 
> I would be interested to understand what complications you are referring to.
> 
> I have a project where - perhaps misguidedly - I do have translations
> in one file. The advantages I see in doing this is that it is easy to
> see if any translations are missing (indeed a simple XSLT could tell
> you this) and would readily allow the translator to see the original
> text and perhaps existing translations in other languages. Finally I
> think it makes it trivial to define an XSLT function for fallback
> processing for missing country/language translations.

Sorry for small self-promotion, but I think that for many applications
GNU gettext is good solution for managing translations of message and
text inside code. I have written small Saxon extension which brings
gettext into XSLT2.0. Advantage is that you can use all gettext tools
for managing translations with your XSLT code. No need to write custom
code for things that have been already done.

http://xmlguru.cz/2006/10/saxon-gettext

			Jirka

- --
- ------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@xxxxxxxx      http://xmlguru.cz
- ------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
- ------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
- ------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksMNK0ACgkQzwmSw7n0dR7T9ACgtJtl2DEfIzrE+IP6ktYWA+aq
ZNkAoL2/D451i1RIl5Cz7G5wrQ6aJ6zv
=V2DE
-----END PGP SIGNATURE-----

Current Thread