<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi.<BR>
Milos Rancic millosh at gmail.com <BR>Thu Jun 17 00:08:03 CEST 2010 <BR>
<BR>> On Tue, Jun 15, 2010 at 17:13, ISO639-3 <ISO639-3 at sil.org> wrote:<BR>>> I am interested in this group's thoughts regarding whether the<BR>>> Serbo-Croatian macrolanguage in Part 3 (though not included in Part 2, and<BR>>> deprecated in Part 1) is a factor, and in what ways.<BR>
> I was rereading emails and I saw this question again. So, it is just a<BR>> matter of IETF languages, but, clearly a matter of ISO 639.<BR>
> Articulated solution and according to the whole situation should be:<BR>> * Make hbs code obsolete and return it to mark a single language,<BR>> Serbo-Croatian standard.<BR>Definitely some code should mark the standard; I believe the macro-language code can do so. (A description field can be added or changed and/or a comments field added.)<BR>> * Add codes for Kaykavian, Chakavian and Torlakian as languages. (They<BR>> are already in 639-6.)<BR>Well we have not yet integrated 639-6 and these are not yet standards in the sense that Bosnian, Croatian, Serbian, and Montenegrin are. <BR>Plus as far as I know none of these is associated with a particular country. So I am not sure in this regard. Perhaps these codes can wait a tiny bit.<BR>> * Add codes for Shtokavian as a macrolanguage. (Also existing in 639-6.)<BR>Replacing to some degree, but not exactly, [sh] -- o.k. I prefer Shtokavian to simply Neo-Shtokavian because it is more inclusive -- although by only registering the four languages -- Serbian, Croatian, Montenegrin, Bosnian -- we imply that is all there is to it.<BR>> * Put Serbian, Croatian and Bosnian under Shtokavian macrolanguage.<BR>Should not [hbs], Serbo-Croatian standard, also be encompassed under Shtokavian?<BR>> * Add code for Montenegrin and put it under Shtokavian macrolanguage.<BR>This is fine with me -- Montenegro is an independent country and the language is considered a standard. There may be cases however whether it is impossible to identify content as belonging to a particular standard -- such as Montenegrin or Serbian as far as I can tell from what you've said of content that was supposedly Montenegrin. Thus I think that in many cases it will be easier to tag content with the macro-language tag, but the individual tags will help language/dialect development.<BR><BR>
Best,<BR>
C. E. Whitehead<BR><A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A><BR><BR> </body>
</html>