Lists Home |
Date Index |
We use an XSL transform to localise XML.
We've used this transform on several layers. We've applied transforms to
the data XML to come up with translated instances (translating content not
tags). We have translated the XSL to localize interface widget contents.
We've translated XHTML output before sending it to the browser. We use
the same set of tags to indicate translatable content at each of these
layers and the same transform as well.
Our markup for translatable elements could be put into schemas as well.
Although we have not yet localized any of our schemas, I think we will be
taking that path within the next 6 months. Perhaps this is a good use
case for dynamically generated schema.
We haven't approached solving this, and in fact I just thought of it as I
read this thread, so if anyone has identified better solutions for
localizing schemas, let me know.
On Thu, 4 Nov 2004 09:55:55 -0000, Michael Kay
>> Shouldn't it be the case that the validation process necessitates
>> a 2-stage parsing ? What I mean is that XSD can only do a lexical
>> validation, a second follow-up stage that validates against the
>> application semantics is required.
> That's actually four levels already: unicode encoding, XML
> schema validity, and application validity. And yes, you often need
> But that doesn't stop you wanting individual levels to be configurable. A
> very simple example, when I validate new documents I want to check that
> date is today. That kind of thing is very easily achieved by a
> schema. Equally, the application-level validation is often done using
> stylesheets, and people often transform stylesheets for the same reason:
> need things to be configurable at that level too.
> Michael Kay
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>