LISTSERV mailing list manager LISTSERV 16.0

Help for ISOJAC Archives


ISOJAC Archives

ISOJAC Archives


ISOJAC@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ISOJAC Home

ISOJAC Home

ISOJAC  July 2011

ISOJAC July 2011

Subject:

Re: possible addition to Syriac Macrolanguage

From:

Peter Constable <[log in to unmask]>

Reply-To:

ISO 639 Joint Advisory Committee <[log in to unmask]>

Date:

Sat, 9 Jul 2011 07:20:27 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

When 639-3 was first being developed, there were no hard and fast criteria for how macrolanguages would get constituted. All that was clear was that macrolanguages were warranted in cases in which there had been ambiguities of usage--sometimes assuming one language and sometimes assuming more than one. Some of the macrolanguage cases were necessitated by MARC usage in which the same ID was used for a dominant variety but also "as a collective" for other related but less developed varieties. Sometimes, an entry had come into 639-2 from MARC as though there were one language (e.g. "Cree") but when there clearly are multiple distinct languages (a reality reflected in Ethnologue 14, which was a source for drafts of 639-3). And sometimes an entry had come into 639-2 from MARC which was simply ambiguous and I was left trying to make sense how best to map it to entities in Ethnologue 14 (e.g., "Rajasthani", "Lahnda", "Marwari").

In the case of [syr], MARC describes it as being used for "Modern Syriac" or "Neo-Syriac". I don't recall now for what reasons it was decided to map that to only [aii] and [cld]. If there are good reasons to consider broadening the scope of [syr] to include other related, modern varieties, that can certainly be considered.

Aside from Turoyo being referred to "modern Syriac" in a particular publication, it would be useful to know what practical benefits there would be of including it within the denotation of [syr]. (If it were included in the [syr] macrolanguage, it would continue to representable using [tru].) An example of such an argument might be, "It is written in Syriac script, and there are widely-used software implementations using [syr] and applying it to content in that script, a significant portion of which is in the Turoyo variety."


Peter

-----Original Message-----
From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On Behalf Of ISO639-3
Sent: Friday, July 08, 2011 12:42 PM
To: [log in to unmask]
Subject: possible addition to Syriac Macrolanguage

Dear JAC members,

I have recently received a request to add Turoyo to the Syriac macrolanguage. It is referred to as "modern Syriac" in a recent publication (Brock, S.P. 2006. An Introduction to Syriac studies. Piscataway, NJ: Gorgias Press. ISBN 1-59333-349-8, p.1).

In looking into this request, I was curious to know how the current two languages were incorporated into Syriac as a macrolanguage, while some other related languages were not. Does this need further discussion and processing to determine the languages which should be included?

In any case, I need to respond the the Turoyo request, and would like your input.

Sincerely,

Melinda Lyons
ISO 639-3 RA
SIL International
7500 W. Camp Wisdom Rd.
Dallas, TX 75236

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
January 2021
November 2020
June 2020
May 2019
February 2019
September 2018
April 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
May 2016
April 2016
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
October 2013
September 2013
August 2013
July 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager