[
Lists Home |
Date Index |
Thread Index
]
Which assumes that you don't send a big document with all translation and
expect the client to make sense of all the xml:lang attributes. So either
you keep the translations separate, list all the translation by
xml:lang-qualified XLinks and let the server fetch the proper translated
documentation on demand through the HTTP mechanisms, or you do have this big
document with all possible translations, and the server has to cut all
content which has not the proper xml:lang mark. I believe the first solution
is better, but this poses the problem that pointer the browser to a RDDL URL
won't immediatly give you a readable documentation (since all human-readable
doc would be external to the root RDDL doc).
Regards,
Nicolas
----- Original Message -----
From: "Rick Jelliffe" <ricko@allette.com.au>
To: <xml-dev@lists.xml.org>
Sent: Sunday, January 20, 2002 7:51 AM
Subject: Re: [xml-dev] RDDL (was RE: [xml-dev] Negotiate Out The Noise)
From: "Nicolas LEHUEN" <nicolas.lehuen@ubicco.com>
>Human-readable documentation is another important problem, with lots of
>specifics consequences, amongst which the need to deal with
>internationalisation. Come on, you can't be serious about
>using xml:lang.
The web architecture for supporting multiple language versions of the
same resource already exists, as part of HTTP. If you configure
your server and filenames correctly, you can serve multiple language
versions of the same document, selected by the language preferences
sent as part of the HTTP request.
Cheers
Rick Jelliffe
-----------------------------------------------------------------
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://lists.xml.org/ob/adm.pl>
|
