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 --
This has been fun, and is clearly an important topic, but it is off
topic for XSL-List.
Please take this discussion off list or to another forum.
Thank you.
-- Tommie
--~------------------------------------------------------------------
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>
--~--