- From: Carrasco Benitez Manuel <manuel.carrasco@emea.eudra.org>
- Date: Fri, 16 Oct 1998 10:53:32 +0100
- To: www-international@w3.org
- Cc: "'tc46sc2@elot.gr'" <tc46sc2@elot.gr>, Harald.Alvestrand@maxware.no
After the discussion on this list a few months ago, the consensus was the the following is needed - Source language - Target language - Transformation method For example: "This is a Greek to English transliteration using the method foo" At present, RFC1766 does not allow this. The syntax and mechanism used is secondary, i.e., it could be my proposal or a totally different one (http://dragoman.org/winter/lanco.html). The reason to propose the extending of the RFC1766 is because it looks like an easy way. In particular, nothing has to be changed to HTML, HTTP, etc. Once a mechanism is accepted, there are more task to be done, probably by different fora. In particular a register with the name of the transformations for each language pair. There is an ISO subcommittee deailing with transliteration, but I do not know active they are: ISO TC46/SC2 International Technical Committee 46 / Subcommittee 2 Conversion of Written Languages http://elot.gr/tc46sc2/ I cross-post this message to their list. Regards Tomas
Received on Friday, 16 October 1998 05:53:47 UTC