Hi,
I agree w/ Mike about an Informative appendix in IPP Everywhere
that updates IPP/1.1 Implementor's Guide (RFC 3196) with a good
discussion of matching of (underspecified and overspecified) tags
for natural languages.
Glen - note that the IANA subtag registry was machine-generated
by Doug Ewell in collaboration with the actual ISO standard groups
that produced all the source tags - this registry was verified by folks
from Unicode Consortium, Microsoft, Google, and others active in
the IETF LTRU WG - I was active for ten years in this IETF WG.
I would not characterize that IANA registry as "a mess" - it's used in
the message catalog and text processing software in a lot of operating
systems and all major web browsers.
Tricky - yes - that's the point of lifting examples from RFC 4647 to
show the language tag matching rules in practice.
The list for printers of 50 common natural languages is useless - I've
seen plenty of printers that support 100 or more.
But document DATA can be in any language (not just the console ones
in IPP generated-natural-language-supported) and UTF-8 or other
Unicode transcoding content can be correctly rendered using the
correct glyphs for the script and language by printers from many
manufacturers.
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 Fri, May 4, 2012 at 1:31 PM, Petrie, Glen <glen.petrie at eitc.epson.com>wrote:
> Mike****
>> ** **
>> And yes, it is a mess... :(****
>> ** **
>> [gwp] No kidding; this looks worse and bigger than ISO 639-3!!!!****
>> ** **
>> Again thanks.****
>> ** **
>> glen****
>> ** **
> ------------------------------
>> *From:* Michael Sweet [mailto:msweet at apple.com]
> *Sent:* Friday, May 04, 2012 10:20 AM
> *To:* Petrie, Glen
> *Subject:* Re: [IPP] What natural-language registry is used by IPP?****
>> ** **
>> Glen,****
>> ** **
>> The IANA language subtag registry is here:****
>> ** **
>>http://www.iana.org/assignments/language-subtag-registry****>> ** **
>> ** **
>> ** **
>> ** **
>> On May 4, 2012, at 10:15 AM, "Petrie, Glen" <glen.petrie at eitc.epson.com>
> wrote:****
>>>> ****
>> Mike,********
>> ****
>> ****
> ------------------------------
>> ****
>> ****
>> IANA already has a registry that we can (and should) use. However I am
> not opposed to providing an example list of common language tags and
> aliases, with a pointer to the IANA registry as the definitive source.
> Ideally this should be part of an implementer's guide, but since I don't
> think we want to update RFC 3196 it can go in a non-normative appendix that
> references RFC 3196 as part of IPP Everywhere.********
>> ****
>> [gwp] What is the name of the IANA registry? I can find stuff on
> “format” but not a list.********
>> ****
>> Thanks ahead of time, glen********
>> ** **
>> __________________________________________________****
>> 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/20120506/fc6d239f/attachment-0001.html>