Andrew Welch wrote:
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.
Jirka Kosek wrote:
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
That sounds interesting!
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
--
_______________________________________________________________
Michael Müller-Hillebrand: Dokumentation Technology
Adobe Certified Expert, FrameMaker
Consulting and Training, FrameScript, XML/XSL, Unicode
Blog [de]: http://cap-studio.de/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--