[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltru] Re: RFC 4646 production "grandfathered" considered harmful



Mark Davis wrote:
 
> grandfathered = "i-" irregular
>             / irregularEverson
>             / 1*3ALPHA 1*2("-" (2*8alphanum)) ; registered grandfathered codes that are well-formed, but would not otherwise be valid
 
> irregulari = "ami" / "bnn" / "default" / "enochian" / "hak" /
> "klingon" / "lux" / "mingo" / "navajo" / "pwn" / "tao" / "tay" / "tsu"

> irregularEverson = "en-GB-oed" / "sgn-BE-fr" / "sgn-BE-nl" /
> "sgn-CH-de"

Splitting i-anything from the rest is fine, IMO unnecessary to
enumerate them in the ABNF:  Any decent parser could handle
x-anything, it should be also able to handle i-anything.  With
that you'd get:

grandfathered = i-legacy / irregular / ( 2*3ALPHA "-" 3*8ALPHA )
i-legacy      = "i-" 3*8ALPHA 
irregular     = sgn-legacy / "en-GB-oed" / "zh-min-nan"
sgn-legacy    = "sgn-" ( "BE-fr" / "BE-nl" / "CH-de" )

Cheating, zh-min-nan isn't really irregular, but together with
en-GB-oed and <sgn-legacy> it's the list of grandfathered tags
with three parts. 

Frank



_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www1.ietf.org/mailman/listinfo/ltru




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.