idnits 2.17.1 draft-carrasco-language-code-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-29) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 129 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (31 March 1998) is 9495 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1766' is defined on line 121, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1766 (Obsoleted by RFC 3066, RFC 3282) Summary: 13 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 M.T. Carrasco Benitez 2 3 Expires 30 September 1998 31 March 1998 5 Codes for language transformation 7 Status of this Memo 9 This document is an Internet-Draft. Internet-Drafts are working 10 documents of the Internet Engineering Task Force (IETF), its areas, 11 and its working groups. Note that other groups may also distribute 12 working documents as Internet-Drafts. 14 Internet-Drafts are draft documents valid for a maximum of six 15 months. Internet-Drafts may be updated, replaced, or obsoleted by 16 other documents at any time. It is not appropriate to use Internet- 17 Drafts as reference material or to cite them other than as a "working 18 draft" or "work in progress". 20 To view the entire list of current Internet-Drafts, please check 21 the "1id-abstracts.txt" listing contained in the Internet-Drafts 22 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 23 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 24 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 25 (US West Coast). 27 Distribution of this document is unlimited. Please send comments to 28 the author at . This document is 29 intended to become an informational RFC, and its content is designed 30 for adoption in other standards and specifications. 32 Overview and Rational 34 The RFC1766 describes the language tags. In the present form, it 35 does not allow to indicate language transformations such as 36 transliteration. This memo is a proposition to allow such 37 transformations. 39 Overview 41 This is a draft proposal to extend the RFC1766 to cover language 42 transformations (transliteration/transcription/trans-anything) from 43 one language (the source language) to another (the target 44 language). 46 In this context, tranformation means that the source language is 47 expressed in another way (e.g., in another alphabet) for people 48 familiar with the target language. This is not translation. There 49 can be many different transformation schemes between two 50 languages. 52 The source language and the target language could be the same. In 53 this case, it will be a transformation within the same language. For 54 example, a transformation from English expressed with the Latin 55 alphabet into English in Braille. 57 Question: Does it makes sense to include Braille transformation ? 59 Syntax 61 This is the proposed syntax: 63 ss-tran-tt-sss 65 where 67 * ss : Source language. Primary language tag. ISO 639 two character 68 language code. Mandatory. 70 * tran : Transformation indicator. First subtag. Literal string 71 "tran". Mandatory. 73 * tt : Target language. Second subtag. ISO 639 two character language 74 code. Optional. If missing, the target language is the same as the 75 source language. 77 * sss : Transformation scheme. Second (if the target language is 78 missing) or third subtag. Must be three or more characters to avoid 79 confusion with the target language. Optional. If missing, the default 80 transformation is applied. 82 Examples 84 * fr-tran : French to French with the default transformation (e.g., 85 Braille). 87 * el-tran-en : Greek to English with the default transformation 88 (e.g., some transliteration). 90 * fr-tran-mybraille2 : French to French with transformation 91 mybraille2. 93 * el-tran-en-mytran3 : Greek to English with the transformation 94 mytran3. 95 This syntax only requires registering "tran" with AINA. 97 Schemes 99 A scheme system is needed that defines: 101 * The tranformations between ordered (i.e., ru-en is different from 102 en-ru) language pair. 104 * The default transformation for each ordered language pair. 106 Author's Address 108 Manuel Tomas CARRASCO BENITEZ 109 The European Agency for the Evaluation of Medicinal Products 110 7 Westferry Circus 111 Canary Wharf 112 London E14 4HB 113 U.K. 115 Phone: +44 171 418 8645 116 Email: manuel.carrasco@emea.eudra.org 117 URL: http://dragoman.org 119 References 121 [RFC1766] 122 "Tags for the Identification of Languages", H. Alvestrand, March 1995. 123 Available at http://ds.internic.net/rfc/rfc1766.txt 125 This document is html format. 126 http://dragoman.org/winter/lanco.html