From manuel.carrasco@emea.eudra.org  Wed Nov 19 13:04:10 1997
Received: from eudra.org (rek.is.eudra.org [193.131.65.10]) by dkuug.dk (8.6.12/8.6.12) with SMTP id NAA07634; Wed, 19 Nov 1997 13:04:07 +0100
Received: from  by eudra.org (4.1/EUDRA-1.0m)
	id AB21513; Wed, 19 Nov 97 12:02:53 GMT
Posted-Date: Wed, 19 Nov 1997 12:00:18 -0000
Received: by WS014 with Internet Mail Service (5.0.1457.3)
	id <WQMSC9KW>; Wed, 19 Nov 1997 12:00:17 -0000
Message-Id: <5DFB753C1329D1119DEC00805F15C342D923@WS015>
From: Carrasco Benitez Manuel <manuel.carrasco@emea.eudra.org>
To: "'Harald.T.Alvestrand@uninett.no'" <Harald.T.Alvestrand@uninett.no>,
        mgm@sybase.com
Cc: rosenne@NetVision.net.il, Converse@sesame.demon.co.uk, i18n@dkuug.dk,
        xojig@xopen.co.uk, sc22wg14@dkuug.dk, www-international@w3.org,
        wgi18n@terena.nl, keld@dkuug.dk
Subject: Transliteration
Date: Wed, 19 Nov 1997 12:00:18 -0000
X-Priority: 3
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain

1) Transliteration has to addressed.

2) Considering transliteration as language variation is easy from a
computer point of view: no new mechanisms are needed.

3) The comprehensive coding on languages is another problem.

4) Three parameters are needed to code transliteration:

      4.1) Translit : A code to indicate transliteration.
      4.2) Source : A language code in a language system.  For example,
"el" for Greek in ISO 639.
      4.3) Target  : A language code in a language system.  For example,
"fr" for French in  ISO 639.

5)  In an evolution of RFC 1766 could be: t-el-fr

     where:
      t   =  Translit.
      el  = Source.
      fr  = Target.

6) If RFC 1766 moves to a more comprehensive language code system, the
transliteration could follow.

7) Script is only one of the factors.  For example:
    Papadopoulos : Greek transliteration into French.   Uses the Latin
script.
    Papadopulos   : Greek transliteration into Spanish.  Uses the Latin
script. 

Regards
Tomas