<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR><BR>Hi!<BR><BR>Doug Ewell doug at <A href="http://ewellic.org/" target=_blank><SPAN id=lw_1255043444_0 class=yshortcuts>ewellic.org</SPAN></A> <BR>Thu Oct 8 14:52:46 CEST 2009 <BR><BR><BR><BR>CE Whitehead <cewcathar at hotmail dot com> wrote:<BR><BR>> If the language subtag registry gets too cumbersome and you need to <BR>> index it and want help, let me know.<BR><BR>> I don't think the Registry is "cumbersome" in the sense that it is <BR>> harder to work with than it should be. It's a large file, but there are <BR>> a lot of languages and scripts and countries in the world.<BR><BR>Right, but it would be nice to have an indexed version for slower computers.<BR><BR>>> It's entirely possible that the dates coincide, but that doesn't mean <BR>>> the histories are related, which was my point.<BR>><BR>> ???<BR>><BR>> Basically "Early Modern" here means after the <SPAN id=lw_1255043444_1 class=yshortcuts>Middle Ages</SPAN>, and before <BR>> the nineteenth (and maybe the eighteenth) century, whether we are <BR>> talking about language, literature, national history. That's my <BR>> interpretation of the term.<BR><BR>> I think we agree in principle on this point, and I don't <BR>> wish to belabor it further.<BR>Yes, fine, no need to belabor anything. The time frame should not be specified; the variant can be precised with the date it was catalogued, not used; that's the best way; that's what's now in the comments field; if that is not enough, f at some time down the road that is it is not, then maybe I'll ask again to change the description field, or someone else can.<BR><BR>> I could not find the URL for it at your site. Sorry, I tried to link <BR>> to it but it was not there.<BR><BR>> As I said later, it's not publicly available due to some issues <BR>> that have caused me to be dissatisfied with it. I could send it to <BR>> you off-list, but I don't want the issues to turn into a support burden; <BR>> I'd rather get it right next time.<BR>O.k. you can try to send it to me in private; my laptop is mini mini mini though so I can't guarantee I can download it and I don't know how long I'll be in shape too, to do anything (health issues), but take care. (actually, gosh, I don't even open email on my laptop because it's all wireless, I work from one site, and offline, and then when I'm done, move what I need from that one site to where I need it)<BR>It sounds need, good luck getting it right! Hope you can share it with the list; I'd rather just link to it online!<BR><BR>> The IANA Language Subtag Registry is a data source. To the extent it <BR>> is incorporated into software, it is up to each developer or team <BR>> to make the Registry and their code work together, including <BR>> indexing the Registry data as needed. Indexing of this sort is <BR>> an application-dependent concept.<BR>> I don't think I expressed that the job was somehow beyond me or too <BR>> big for me. I built both the initial RFC 4646 Registry and the <BR>> initial RFC 5646 Registry (both before the incremental changes <BR>> discussed on this <BR>> list) and wrote several programs to help index and otherwise manage <BR>> the data during the Internet-Draft stages of these two documents.<BR>Yes, you do a lot.<BR><BR>Best,<BR><BR><BR><BR>C. E. Whitehead<BR><BR><A href="http://us.mc582.mail.yahoo.com/mc/compose?to=cewcathar@hotmail.com" ymailto="mailto:cewcathar@hotmail.com"><SPAN id=lw_1255043444_2 class=yshortcuts>cewcathar@hotmail.com</SPAN></A><BR><BR><BR>> --<BR>> Doug Ewell | Thornton, Colorado, USA | <A href="http://www.ewellic.org/" target=_blank><SPAN id=lw_1255043444_3 class=yshortcuts>http://www.ewellic.org</SPAN></A><BR>> RFC 5645, 4645, UTN #14 | ietf-languages @ <A href="http://is.gd/2kf0s" target=_blank><SPAN id=lw_1255043444_4 class=yshortcuts>http://is.gd/2kf0s</SPAN></A> ­<BR><BR><BR><BR> </body>
</html>