Lists Home |
Date Index |
The question of how to handle multiple language versions of the same texts
is fairly old. You can do it with fine grain parallelism (interleaved), or in
course grain (e.g. separate sections in the same document), or in parallel documents.
But the optimal arrangement chosen for editing and storage might not be the
same for delivery over the web. Even if you store everything in one document,
the browser infrastructure is set up to allow different language documents
from the same URL selected by the HTTP preferences.
If you have to support multiple languages, there are some interesting niche
editors around, such TRADOS for translating different versions while maintaining
"translation memory". I see XML Spy put out a Japanized version of their
development tool recently. For complex scripts, WorldPad from SIL is a wonderful
feat, though it does not have any specific markup features. At my company,
we think we have some unique internationalization features in our forthcoming
Topologi Pty. Ltd.
----- Original Message -----
From: "Nicolas Lehuen" <firstname.lastname@example.org>
> 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).
> ----- Original Message -----
> From: "Rick Jelliffe" <email@example.com>
> To: <firstname.lastname@example.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" <email@example.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.
> 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>