Print

Print


What are the opinions of JAC members? There are certainly different criteria for 639-3 and 639-2. Another option would be to include Serbo-Croatian as a "language group" in 639-5 only.
 
H�vard
 
~~~~~~~~~~~~~~~~
H�vard Hjulstad
mailto:[log in to unmask]
~~~~~~~~~~~~~~~~
 


From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On Behalf Of Peter Constable
Sent: Wednesday, November 09, 2005 3:06 PM
To: [log in to unmask]
Subject: Re: ISO 639 JAC issue - Serbo-Croatian

Havard:

 

I consider your analysis correct with one small modification: it is the *draft* code table for ISO 639-3 that has an identifier hsb for the macrolanguage. I have all along assumed it was up to the JAC to decide whether to include that in part 3.

 

 

Peter

 


From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On Behalf Of Havard Hjulstad
Sent: Tuesday, November 08, 2005 6:05 AM
To: [log in to unmask]
Subject: ISO 639 JAC issue - Serbo-Croatian

 

Dear JAC members,

 

One ballot is actually still missing, but the result is clear: Serbo-Croatian is not approved in ISO 639-2, and it is not "un-deprecated" in ISO 639-1. There does not seem to be any purpose in ciculating a second ballot at this point.

 

Since the ballot was based on an "internal" request, and since the decision actually means no change, I shouldn't think that it is necessary to publicise it more widely.

 

The consequences of the decision are the following (in my analysis):

 

ISO 639-1 has the alpha-2 identifier sh, which is deprecated; users need to choose one or more of the identifiers sr, hr, bs.

 

ISO 639-2 has no identifier; users need to choose one or more of the identifiers srp/scc, hrv/scr, bos (T/B identifiers).

 

ISO 639-3 has an identifier hsb, assigned to the "macro-language".

 

First question: Am I right in this analysis?

 

Second question: Is this the best solution?

 

Third question: If not -- what to do?

 

Best regards,

H�vard

 

~~~~~~~~~~~~~~~~
H�vard Hjulstad
Standard Norge / Standards Norway
  P.O.Box 242, NO-1326 Lysaker (Norway)
  +47 67838645 (direct)   fax: +47 67838601
http://www.standard.no/
mailto:[log in to unmask]
~~~~~~~~~~~~~~~~

 
https://listserv.loc.gov/cgi-bin/wa?A3=ind0511&L=ISOJAC&E=quoted-printable&P=132892&B=------_%3D_NextPart_001_01C5EAC0.ED41CF26&T=text%2Fhtml;%20charset=iso-8859-1&XSS=3&header=1
listserv.loc.gov
CC-MAIN-2023-50
13500
application/http; msgtype=response
sha1:IXOK4DYSKEYKXSM7YHMLREYOME7ULO44
<urn:uuid:bf6b59fb-9138-43fc-86cf-5557146f7b0e>
2023-12-06T04:02:19Z
104.16.55.16
text/html
sha1:KPG4ZZITRGGNBBASPE36VENC73MTF3PC
<urn:uuid:72b9a963-41d4-4709-aa4b-8957474fcf2d>
https://listserv.loc.gov/cgi-bin/wa?A3=ind0511&L=ISOJAC&E=quoted-printable&P=132892&B=------_%3D_NextPart_001_01C5EAC0.ED41CF26&T=text%2Fhtml;%20charset=iso-8859-1&XSS=3&header=1
response
<urn:uuid:759cabed-adb5-497c-81e8-ce43d6308dd9>
isPartOf: CC-MAIN-2023-50
publisher: Common Crawl
description: Wide crawl of the web for November/December 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-39
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/