| Please choose from the categories below |
Cuneiform Signs |
|
Analysis and reports to support an international standard for computer encoding of the Cuneiform writing system Research on the development of Cuneiform signs |
| Sign Names -- Distinct Names and Alternate Names |
First here are alternate names for the same signs, useful to eliminate duplicates. The pages CuneiformSigns.org/SignList1.htm etc. attempt to keep to traditional names, therefore do not use exactly the same names as in the UTC proposal of February 2004. Second are signs where name distinctions are needed. Third is a discussion of mergers of six or more signs yielding later KU, and etymological information distinguishing some of these as to their original component identities. Overlap of GAN2 tenu with SHE3 is also an issue for correct identification of signs. AG or AK Some names which better respect unities and immediate constituents
MUL rather than AN AN AN (a cluster, not a sequence of independent
signs) TUR3 = NUN x LAGAR (as shown by the etymologically related older forms;
not = NUN.LAGAR) UTUA2 = "DAG x KISIM5" (a unit even though not visually infixed;
not = DAG.KISIM5) The same remarks apply here as to TUR3 above. KISIM5
x infixes occur only visually as part of UTUA2 x those infixes, KISIM5
x infixes are not immediate constituents of those signs. * Signs which are distinguished from each other: ERIN2 (= ERIM?) and PUR2 are distinct (unrelated in early forms, see Labat #393) GIR3 is now distinguished from PIRIG KU vs. DUR2 vs. TUG2 vs. NAM2 vs. SHE3 = ESH2 vs. ZI3 (all eventually
merged as late KU) *** At least a three-way distinction is needed for these TUK or KAB Labat #309, Fara #473, ZATU #277 with further distinctions? HI vs. SHAR2 were originally distinct, later merged. If SHAR2 (large circle) was originally only in numbers, then we can keep that distinction, as Tinney appears to do in the PSL list (only SHAR2 and SHAR2 x U). Thus HI x (DISH or KIN or GAD or ASH) rather than SHAR2 x (those infixed signs). The following three are distinct. EDIN (two forms separated by Labat #168, the second incorrectly called the "gunu" form of the first ? If they are distinct, an additional sign name is needed to distinguish them) The following is a four-way distinction for which the names need to
be distinct. In particular, the third should not be named as the fourth.
Later UNUG and simple AB merged. Labat #555 ZUM is two distinct signs, note the dotted line dividing the oldest forms. Need an additional name to distinguish one of them. Distinctions Distinctions DUG x ASH at least two AB2 and KISIM5 are distinct? GISHGAL is URU x MIN, not URU x A. (PSL list has both container-infix signs) UG5 is EZEN x BAD not EZEN x AN ? (PSL list has both container-infix signs?) GI4 not GI.gunu (it is not typical .gunu in any case, the February UTC proposal distintinguished these) *** Sign names which are alternates (I corrected the concordance for a couple of these where my usage was not the same as Steve Tinney's -- haven't revisited this small group for their current status) Where I have a different usage than the PSL list, and am not yet making
changes: Questions: Are these pairs distinct? PSL has both. PSL has neither: *** The KU family of mergers This section was written in reference to the UTC proposal of October, 2003, and has not been significantly updated since the version of February, 2004, although as Steve Tinney indicated, additional distinctions were added there. The questions about etymological identity especially of some infixed and superimposed forms may remain, and will be addressed more comprehensively later. Examples are included below. A distinction KAR2 (= "GAN2.tenu") vs. GAN2 may be valid as independent signs, where the rotation (.tenu) is not conditioned by context. But many of the instances of GAN2 when superimposed on another sign seem to really be simply that, and the sign is turned so that it will be most identifiable as a Gestalt, not confused with the wedges of the base sign? That is to say, the turning does not signify that GAN2.tenu was superimposed, but that simple GAN2 is. In fact, many of these may have been SHE3 (= ESH2), not GAN2 at all in origin. Sign names which apply to the full historical range may therefore need to be corrected from GAN2 to SHE3 or equivalent. Similar reasoning may be valid for DISH.tenu or ASH.tenu, under conditions we perhaps can state, or perhaps do not yet know? The next six are all distinguished by Krebernik 1998, but are all merged in Labat #536. The PSL list as of early October distinguished TUG2, ESH2 (= SHE3), and KU. The name KU has at least sometimes been used to refer to the result of merging all of these in later cuneiform. For infixed signs belonging to these six, can we usually identify which original sign they go back to? KU (one horiztontal inside rectangle, touches both sides) Here are the relevant sign names included in the PSL list. TUG2 GU2 TIMES SAL PLUS TUG2 These two later merged as expected from the Are these two or three alternate names for the same sign, There is only one example of SIGN x ESH2 in the combined CDLI-Civil
list where the identity of the infixed component is one I can unambiguously
recognize, namely this next one KA x SHE3.) Fara and ZATU have the following EZEN x SHE not EZEN.$e$$ig I do not find signs in the concordance unequivocally analyzed as SIGN x DUR2, (For semantic reasons I have considered SAL x DUR2 instead of SAL x textile as a conceivable origin of NIN 'lady' or 'goddess', a woman who wears cloth vs. a woman on a seat / throne? But "considered" is as far as I can go here.) |
| Copyright © 2003. All Rights Reserved. Much of the analytical material on this web site will be included in an etymological study and concordance to cuneiform signs, to be published shortly, and may be used to validate the sign list, but should not be cited in any detail until it is published (guaranteed 2004 probably spring). Permission is granted for others to use the information on these web pages for preparation of a proposal to Unicode for a standard encoding of Cuneiform. The proposed sign list itself is free of any restrictions. |