Subject: Re: [xsl] xslt and i18n From: Michael Müller-Hillebrand <mmh@xxxxxxxxxxxxx> Date: Thu, 5 Feb 2009 12:53:22 +0100 |
I would image it would be straightforward to implement my own i18n solution, something like:
<title> <xsl:value-of select="fn:getLocalisedValue('page.title', 'The English Title', 'de_DE')"/> </title>
where the arguments are token key, default value and locale.
That is almost the way I usually do it, in conjunction with a localization.xml file. I don't supply any default text, because I have defined a default language and assume that those strings will always be present in the XML file.
I think that replacing all literal texts inside template by xsl:value-of and function call is overkill and it makes stylesheet less readable.
To overcome this limitation I have integrated Gettext library into Saxon some time ago:
http://xmlguru.cz/2006/10/saxon-gettext
For my applications, customers love the ease of use with the localization.xml, which can easily be extended and corrected without any further software. To handle gettext files, they would need poedit and would have multiple files for all languages. Which might better fit other workflows.
-- _______________________________________________________________ Michael M|ller-Hillebrand: Dokumentation Technology Adobe Certified Expert, FrameMaker Consulting and Training, FrameScript, XML/XSL, Unicode Blog [de]: http://cap-studio.de/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xslt and i18n, Jirka Kosek | Thread | Re: [xsl] xslt and i18n, Andrew Welch |
[xsl] Free XML Editor?, Jesper Tverskov | Date | Re: [xsl] Free XML Editor?, Jirka Kosek |
Month |