[YES] The Linguasphere proposal is suited to RFC 3066(oritssuccessors) and its consuming protocols

[Addison Phillips [wM]]

I think what Peter is saying is:

  i. If someone wanted to use the ISO15924 script code 'prsl' (not currently
assigned, I believe), then they wouldn't have to submit a request for it.

  ii. If someone wanted to use 'prsl' in an extension (e.g. a private use
subtag), then they also wouldn't have to submit a request for it.

  iii. If someone wanted to use 'prsl' as a primary language subtag, then
they would have to register it.

  iv. Otherwise 'prsl' is forbidden as a (variant) subtag *and* cannot be
registered under RFC 3066bis.

Addison

Addison P. Phillips
Director, Globalization Architecture
webMethods | Delivering Global Business Visibility
http://www.webMethods.com
Chair, W3C Internationalization (I18N) Working Group
Chair, W3C-I18N-WG, Web Services Task Force
http://www.w3.org/International

Internationalization is an architecture.
It is not a feature.

> -----Original Message-----
> From: ietf-languages-bounces at alvestrand.no
> [mailto:ietf-languages-bounces at alvestrand.no]On Behalf Of Peter
> Constable
> Sent: 2004"N6OZ7"u 9:42
> To: ietf-languages at iana.org
> Subject: RE: [YES] The Linguasphere proposal is suited to RFC
> 3066(oritssuccessors) and its consuming protocols
>
>
> I wrote:
>
> > Secondly, you have said that the number of custom tag requests would
> be
> > cut back, but I question how big an issue that would be. Sure, if
> > someone wanted to request "prsl", they wouldn't have to.
>
> Let me re-word that a bit more clearly. If someone wanted to use "prsl",
> they wouldn't have to submit a request for it.
>
>
> Peter
>
> Peter Constable
> Globalization Infrastructure and Font Technologies
> Microsoft Windows Division
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages