attachment-0001
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://63/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Glen,<div><br><div><div>On May 4, 2012, at 9:56 AM, "Petrie, Glen" <<a href="mailto:glen.petrie@eitc.epson.com">glen.petrie@eitc.epson.com</a>> wrote:</div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="blue" style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1" style="page: Section1; "><div><div style="margin: 0in 0in 0.0001pt; "><font size="3"><font color="#000000">...</font><span style="color: blue; font-family: 'Times New Roman'; font-size: 12pt; "> </span></font></div><div style="font-family: 'Times New Roman'; font-size: 12pt; margin: 0in 0in 0.0001pt; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">3. Do not support extended ISO 639 language codes since technically they violate RFC 5656 (which requires the shortest ISO 639 code be used); for example, "english" is not OK but "en", "en-us", "en-uk", etc. are fine<o:p></o:p></span></font></div><div style="font-family: 'Times New Roman'; font-size: 12pt; margin: 0in 0in 0.0001pt; "><font size="3" color="blue" face="Times New Roman"><span style="font-size: 12pt; color: blue; "> </span></font></div><div style="font-family: 'Times New Roman'; font-size: 12pt; margin: 0in 0in 0.0001pt; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">[gwp] I did not understand that ISO 639 (-3) was using “english" as a tag but was using “eng”; I understand that the new ISO 639 tags are three chars in length and I have not discovered extensions (eng-xxx); yet! Note that ISO 639-3 has some 8000+ tags; so that some “secret decoder ring”.</span></font></div></div></div></div></blockquote><div><br></div>My example wasn't necessarily the best; will update accordingly.</div><div><br></div><div>As for the decoder ring, I'm fine keeping the list short to those people are actually using widely (which keeps us to around 50 or so...)</div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="blue" style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1" style="page: Section1; "><div><div style="font-family: 'Times New Roman'; font-size: 12pt; margin: 0in 0in 0.0001pt; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "><o:p></o:p></span></font></div></div><div style="font-family: 'Andale Mono'; font-size: medium; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">[gwp] Question: Should PWG create it own list of language tags? The list could be based on what is generally used by everyone else but not all of the ones in ISO 639-3. I do not know if a language tag hierarchy exists that would reduce the ISO 639-3 list down to more manageable list of tags.<o:p></o:p></span></font></div></div></div></div></blockquote><br></div><div>I would not want the PWG to tackle defining its own registry - that way lies madness... :)</div><div><br></div><div>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.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>