[Home] [By Thread] [By Date] [Recent Entries]
Hi,
I agree that it is getting of topic but still think that i18n is a sophisticated issue that requires multiple approaches with three main ones, (each impacting XSLT design, to some degree) typically to be used in that order: - Separate files as Andrew proposes, whenever possible, typically for large text sections - Translation dictionaries for common/frequent terms and expressions, typically in reference tables - Attribute i18n for custom labels and display attributes, hence the XSLT question, as namespaces and XSLT make this very easy As for @lang or @xml:lang, the value point for @xml:lang is that if we have a standard way of defining language selection, processing can better be generalized. The same should be true for attribute i18n. Thank you, Cheers, ac Friends --
|

Cart



