Hi,
Per the IETF RFC Index, the latest successors to RFC 1766 are:
5646 Tags for Identifying Languages. A. Phillips, Ed., M. Davis, Ed..
September 2009. (Format: TXT=208592 bytes) (Obsoletes RFC4646) (Also
BCP0047) (Status: BEST CURRENT PRACTICE)
4647 Matching of Language Tags. A. Phillips, M. Davis. September 2006.
(Format: TXT=45595 bytes) (Obsoletes RFC3066) (Also BCP0047) (Status:
BEST CURRENT PRACTICE)
Language tags can now include embedded tags for scripts,
geographic regions (not just countries), variants, and private
use tags.
Parsing language tags is no longer simple. Beware that they
embedded the script tag (if present) BEFORE the region tag
(e.g., 'US'). Naive parsers will fail badly. See the ABNF on
pages 5-6 of RFC 5646. Reference libraries for parsing do
exist.
Both simple language tags (e.g., 'en') and simple region tags
(e.g., 'US') can now be EITHER 2 or 3 characters. Script
tags must be exactly 4 characters. Variant tags can be 5-8
characters. See the examples right after the ABNF.
Of course the fixed language and country tags of 2 characters
in the Printer MIB v2 are broken - they were broken when it
was published, but I failed to convince the other editors to let
me fix it (many naive clients would have been broken).
BEWARE: 3-character language tags are in common use
and are in fact preferred where an older 2-character tag was
already registered (I can't explain why - never understood it).
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Mon, Apr 30, 2012 at 8:04 PM, Michael Sweet <msweet at apple.com> wrote:
> Glen,
>> On Apr 30, 2012, at 3:59 PM, Petrie, Glen wrote:
>> Can someone provide me the reference for the natural-language registry is
> used by IPP?****
>>> From RFC 2911:
>> 4.1.8 'naturalLanguage'
>> The 'naturalLanguage' attribute syntax is a standard identifier for a
> natural language and optionally a country. The values for this
> syntax type are defined by RFC 1766 <http://tools.ietf.org/html/rfc1766> [RFC1766 <http://tools.ietf.org/html/rfc1766>]. Though RFC 1766 <http://tools.ietf.org/html/rfc1766>
> requires that the values be case-insensitive US-ASCII [ASCII <http://tools.ietf.org/html/rfc2911#ref-ASCII>], IPP
> requires all lower case to simplify comparing by IPP clients and
> Printer objects. Examples include:
>> 'en': for English
> 'en-us': for US English
> 'fr': for French
> 'de': for German
>> The maximum length of 'naturalLanguage' values used to represent IPP
> attribute values is 63 octets.
>>> which leads to RFC 3282 (the replacement), which references ISO 639,
> 639-2, 3166, and 15924.
>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20120501/4c52ae55/attachment-0001.html>