Tempest in an Armenian teapot resolved

[Debbie Garside]

 Michael wrote:

> Nicely spotted.

+1

However, my crystal ball tells me that there are a number of appeals in the
offing; not least when RFC4646bis reaches "last Call".  To this end I would
suggest that those official bodies, who will have to expend (far too much)
time in dealing with such appeals, should perhaps look at the refining the
RFC that defines the appeals process and introduce similar sanctions as per
those that are used within English Law for Vexatious litigation.

See: > http://en.wikipedia.org/wiki/Vexatious_litigation which actually
shows info re Vexatious Litigation in California.  

I think this would reduce the amount of time expended. Praemonitus
praemunitus.

Best regards

Debbie Garside




> -----Original Message-----
> From: ietf-languages-bounces at alvestrand.no 
> [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of 
> Michael Everson
> Sent: 26 September 2006 15:37
> To: IETF Languages Discussion
> Subject: Re: Tempest in an Armenian teapot resolved
> 
> At 10:15 -0400 2006-09-26, John Cowan wrote:
> >It turns out that Classical Armenian already appears in the 
> code list 
> >of ISO FDIS 639-3 with the code element 'xcl'.  A pity that no one 
> >noticed this before!  Middle Armenian is also there with 
> code element 'axm'.
> >
> >So although Classical Armenian (in common with most of the world's
> >languages) cannot be represented within the RFC 4646 
> framework, it will 
> >be representable in RFC 4646bis.
> 
> Nicely spotted.
> --
> Michael Everson * http://www.evertype.com 
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
> 
> 
> 
>