> But remember that an extension to HTML to allow multiple body parts, which > could be in different languages and/or different code sets, has been > proposed (though currently rejected). When such a facility becomes available > we need to have in place a method that can cope with it, without having to > invent something new. Today is possible to have bilingual, trilingual ... docs. The language label proposal is for how to label monolingual HTML docs. > Something else for you to think about. The eXtensible Markup Language (XML) > will allow multilingual documents of any structure to be transmitted over > the web. We have been very careful to make this 10646 compliant from day 1. > What ever method the I18N group come up for language identification should > be usable with documents other than those starting <HTML and be usable with > both monolingual and multilingual documents. XML should also have a way to label monolingual docs with similar functionalites to the ones in considerations. TomasReceived on Friday, 28 February 1997 03:18:30 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:47 GMT