Hi,
Peter - your proposal appears to be wobbling between
(1) One new field
- ExpectedScript (complete list)
(2) Two new fields
- DefaultScript (do NOT use a script subtag)
- ExpectedScript (not including DefaultScript value??)
If this registry (and RFC3066bis) don't make VERY clear
when script subtags MUST NOT be used, then we're making
no headway.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com
> -----Original Message-----
> From: ltru-bounces at lists.ietf.org
> [mailto:ltru-bounces at lists.ietf.org]On
> Behalf Of Peter Constable
> Sent: Thursday, April 14, 2005 10:20 AM
> To: LTRU Working Group
> Subject: RE: [Ltru] Re: Moving Forward
>
>
> > From: ltru-bounces at lists.ietf.org
> [mailto:ltru-bounces at lists.ietf.org]
> On
> > Behalf Of Doug Ewell
>
>
> > I do think that anyone proposing that the initial registry contain
> > default-script information for all 479 ISO 639-1 and -2 languages
>
> That is not what Frank or I have suggested. A default-script
> field only
> needs values for languages like English for which we don't want people
> to use script subtags in general.
>
>
>
> Peter Constable
>
> _______________________________________________
> Ltru mailing list
> Ltru at lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru
>
_______________________________________________
Ltru mailing list
Ltru at lists.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.