OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Internationalization and naming

[ Lists Home | Date Index | Thread Index ]
  • From: "Rick Jelliffe" <ricko@allette.com.au>
  • To: "XML-Dev Mailing list" <xml-dev@ic.ac.uk>
  • Date: Tue, 5 Jan 1999 12:53:29 +1100

Simon St.Laurent writes:

> Will English vocabularies be used, or will other languages be used?

> This seems like something that the next generation of schemas could
> address neatly, by providing room for something like a translation
> table, identifying elements and their 'standard' equivalents.  This
> could open up validation considerably, and possibly make it a lot
> easier to get buy-in from user communities that perhaps have no
> input toward the standards or their choice of language.

I think we can observe the rule that the more a name is like a
the less reason there is need for a local version. The more the name is
a variable, the less reason for an internationally understandable

SGML allowed you to remap keywords: you could change CDATA to
KDATEN or whatever. But no-one did.

When a standard DTD is specified, I think there is good reason to avoid
providing alternative names. The biggest one is documentation. If
I write a book in English, and the examples cannot be directly used by
people in other languages, then that makes life more complicated for
foreigners than less. (The AF approach seems less satisfactory
than the DCD approach because of this. )

I think we still have a few years before we need to seriously consider
issue: have CSS implementations been tested using non-Western
Native Language Markup yet?  My preliminary tests indicate that the
current betas do not handle non-ASCII characters in attribute tests or
element names.  After these problems are fixed up, and after more XML
products support character encodings that people actually use, then we
can turn our attention to alternatives.

Actually, IMHO the thing that is actually required for
is a Website giving error messages and commmon element names in multiple
languages. That way you can write your code to return a URI,
and content-negotiation can return the specific error message in the

Rick Jelliffe

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS