RFC3066bis: looking ahead

Addison Phillips [wM] aphillips at webmethods.com
Tue Jan 20 19:33:26 CET 2004

?? But the problem would still be: how do you distinguish an ISO3166-2 from
an ISO639-3? The lang subtag isn't at issue here, as it isn't the lang code
that's the problem. It's the secondary tag. If ISO639-3 can identify a
language exactly, then it can appear in the first position. If it can't then
RFC3066 has to disambiguate 639-3's from other potential tag's "namespaces".


Addison P. Phillips
Director, Globalization Architecture
webMethods | Delivering Global Business Visibility
Chair, W3C Internationalization (I18N) Working Group
Chair, W3C-I18N-WG, Web Services Task Force

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: mardi 20 janvier 2004 10:11
> To: ietf-languages at alvestrand.no
> Subject: RE: RFC3066bis: looking ahead
> > From: Mark Davis [mailto:mark.davis at jtcsv.com]
> > Currently, we can tell script from region by length. But if you toss
> in two tags
> > for language, where the second can be of length 2 or 3, then you can't
> tell
> >
> > lang-sublang
> > from
> > lang-region
> True; I hadn't commented on that possibility and should have.
> The "sublang" (as you call it), I would say, could only ever be three
> letters. This is true by the nature of relationship between the parts of
> ISO 639. My inclination is that we should go further, though, in
> freezing the use of two-letter identifiers from ISO 639-1 to exactly
> those that are in use today.
> So, there still isn't a problem.
> 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

More information about the Ietf-languages mailing list