[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: xslt and i18n
Andrew Welch wrote:
I would image it would be straightforward to implement my own i18n solution, something like: 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. 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/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|