<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 8 Sep 2008, at 23:37, Frank Ellermann wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Michael Everson wrote:<br><br><blockquote type="cite">I trust that this compromise will prove satisfactory.<br></blockquote><br>Actually this again shows that the possibility of "generic variants" are a bug in RFC 4646.</div></blockquote><div><br></div><div>Why? en-fonipa and bo-fonipa are both perfectly reasonable descriptions of text.</div><br><blockquote type="cite"><div>What is really needed is an extension registry for this zoo (fonipa, fonupa, pinyin, ...), but as long as nobody creates it, and as long as this ugly hole in RFC 4646 permits such "generic variant" kludges, go for it.</div></blockquote><div><br></div><div>I don't follow you, but I see that you support registering the "pinyin" tag with</div><br><blockquote type="cite"><div>I'd strip the remark about "omitting Latn", however.</div></blockquote><div><br></div><div>I could live with that but I think in the real world people will omit it.</div><br><blockquote type="cite"><div>A proper extension registry could arrange that, but the generic variant kludge asks for hardcoding this<br>info in applications to get the matching right.</div></blockquote><div><br></div></div><div>I don't follow. What's wrong with tagging bo-Latn-pinyin? It specifies a particular well-defined orthography for a particular language. I certainly do not think that bo-Latn-bopinyin would be "better".</div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Everson Mono'; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: 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: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Everson Mono'; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-family: '-webkit-monospace'; ">Michael Everson * <a href="http://www.evertype.com/">http://www.evertype.com</a></span></div></div></span></div></span> </div><br></body></html>