Another artifact. The original requirement was: - MUST allow 33 - SHOULD allow 42 The smaller limit was because extlangs weren't actually permitted... however... a close examination of the text in 4646 reveals that 34 is ALSO not the number. That's because a registered primary language subtag is now longer than a language-extlang sequence. Hence: <t>Protocols or specifications that specify limited buffer sizes for language tags MUST allow for language tags of at least 35 characters. Note that <xref target="RFC4646">RFC 4646</xref> recommended a field size of 42 characters because it included all three elements of the 'extlang' production. Two of these are now permanently reserved, so a registered primary language subtag of the maximum length of eight characters is now longer than the longest language-extlang combintation. Protocols or specifications that commonly use extensions or private use subtags might wish to reserve or recommend a longer "minimum buffer" size.</t> And the art: language = 8 (longest registered value) script = 5 (if not suppressed: see Section 4.1) region = 4 (UN M.49; ISO 3166-1 requires 3) variant1 = 9 (needs 'language' as a prefix) variant2 = 9 (needs 'language-variant1' as a prefix) total = 35 characters Addison Phillips Globalization Architect -- Lab126 Internationalization is not a feature. It is an architecture. > -----Original Message----- > From: Peter Constable [mailto:petercon at microsoft.com] > Sent: Tuesday, July 08, 2008 9:54 PM > To: Phillips, Addison; LTRU Working Group > Subject: RE: 4.4.1: limited buffer sizes > > > From: Phillips, Addison [mailto:addison at amazon.com] > > > > Well they're both wrong. The actual number is 34. > > I suspected such a number. > > > > The text has been modified to read: > > ... > > <t>Protocols or specifications that specify limited buffer sizes > for > > language tags MUST allow for language tags of up to 34 > characters.</t> > > > > <t>Protocols or specifications that specify limited buffer sizes > for > > language tags SHOULD allow for language tags of at least > > 34 characters. > > The latter statement seems pointless in light of the former: the > former makes the latter mandatory. (That was part of my concern > earlier; I should have stated that explicitly.) > > > > Peter _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.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.