Message-Id: <6.1.2.0.2.20050412014332.0309ceb0@mail.jefsey.com>
Date: Tue, 12 Apr 2005 03:00:22 +0200
To: "Debbie Garside" <debbie@ictmarketing.co.uk>,
	"'Randy Presuhn'" <randy_presuhn@mindspring.com>, <ltru@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: RE: [Ltru] [psg.com #882] registry should copy non-English
	fieldsfrom ISO documents
In-Reply-To: <200504112220.j3BMK84I004532@smtp-los03.proxy.aol.com>
References: <011a01c53ee2$4a1a5d60$7f1afea9@oemcomputer>
	<200504112220.j3BMK84I004532@smtp-los03.proxy.aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

At 00:20 12/04/2005, Debbie Garside wrote:
> >  3) In those cases where a French name for a language is available from
> > the ISO documents, the remaining question is whether it should be
> > included in the same field as the reference name, using some kind of
> > delimiter, or given a field of its own.  Based on the technical arguments
> > so far, I believe the preference would be to use a separate field to hold
>the French name, when available, for a language.
>
>This is how it is currently held within the -6.

OK.

> > Note that this resolution would NOT entail translating entries for which
> > French translations are not already present in the ISO documents, nor
> >would it require a registrant to obtain a French name for a language, nor
> >should it be in any way understood as constraining the names displayed by
> >implementations or used by users.
> >
> > Would this be an acceptable statement of rough consensus?
>
>For me... Yes

I am sorry, I can only repeat this a definitive blocking opposition for me. 
For the reasons I gave several times. However once the principle of dual 
language (at least) naming necessity is established, practical arrangements 
can be quite flexible.

1. if an Englist or French (or other languages to be added) name for a 
language is missing, it will be accepted as non fully documented until a 
name is provided (a IANA procedure and Reviewer will have to be designated).
2. the same IANA registration could only be entered in English or French. 
It will be up to the French/English Reviewer to make sure the name in the 
missing language(s) is provided.

jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru