| 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 |
| Signs with structure (Component OVER Component) or (Component
Crossing Component) where the components do exist independently Productivity; avoiding creation of artificial parts |
Summary of results: The conclusions are that only two of the signs surveyed here justify a left-right division into sign atoms to be encoded separately. All of the remainder should be encoded as sign atoms, and named (consistent with received tradition) using a sign-over-sign naming structure, not a sign-followed-by-sign structure, or in some cases with an indivisible single name SIGN. In addition, it turns out that there is only a single example in which the upper and lower parts of a SIGN-OVER-SIGN structure are distinct, so that the sign name syntax should use some word taking only a single argument, not a word like "OVER" that relates two arguments. Thus a name simply SIGN PAIRED (used in the full list of signs proposed on this site) or use of the word "PARALLEL" (as in the Ellermeier / Studt naming pattern, though they diagrammatically illustrate with two sign names) would be more appropriate. The list below gives 27 simple sign-over-sign examples, 11 sign-crossing-sign examples, with four signs appearing in each of these two ways, possibly in contrast. There are three examples which have this kind of structure only etymologically, which can be considered fused far back in the history of Cuneiform, and of course have simple atomic names in the tradition. Among those complex signs where we might be tempted to make a left-right division, productivity of components shows clearly that four have the structure sign-over-sign, not sign-followed-by-sign, while six are without a conclusive analysis. There are two examples of a higher complexity where we can make a first left-right division and then treat the parts as having an upper-lower division. These are (EN CROSSING EN).(IM CROSSING IM) and NINNI5.KINDA = (TIR3 OVER TIR3).((GAD.GAR) OVER (GAD.GAR)). But there are no examples of the lower degree of complexity whose major division is left-right. Since there are no such, it is probably best that the small residue of hard cases either be named as atoms or be named in the sign-over-sign structure, if parts can be identified which do function as independent signs. |
Simple Examples of (SIGN OVER SIGN) (Source?) (SU OVER SU) (source?) (BAL OVER BAL) ZATU sign (U$ OVER U$) Labat #66 (ZI OVER ZI), Fara #469, ZATU sign #420 Labat #66a (ZI OVER ZI).A ZATU #42 (BAD OVER BAD) Labat #96a MÉNBULUG = (BULUG OVER BULUG) Labat #99a1 (EN CROSSING EN), Fara #534 CDLI-Civil (SAG OVER SAG) Labat #151a (LUGAL OVER LUGAL) Labat #206a LAH = (DU OVER DU) (Source?) (NI OVER NI) CDLI-Civil (GA2 OVER GA2) CDLI-Civil (GISH CROSSING GISH) (if at right angles, is this a name
for another sign?) Ellermeier #330_60v (LU2 OVER LU2) Fara #364 (SHAR2 x DISH) OVER (SHAR2 x DISH) Ellermeier #375_45 NINNI5 = (TIR OVER TIR), Labat #375c, Fara #205 Labat #404x GINGIRA = (KISIM5 OVER KISIM5) Fara #405 (KIR2 OVER KIR2) ZATU sign (AMAR OVER AMAR) Labat #459av (DU6 OVER DU6).SHE.SAR (source?) (GABA OVER GABA) UET-II #174 (?MI.MI or MI OVER MI ?) CDLI-Civil (GUD OVER GUD) Both (SIGN OVER SIGN) and (SIGN CROSSING SIGN), in contrast? ZATU .eps image (GI OVER GI) CDLI-Civil (GAN2 OVER GAN2) Labat #326v (GI4 OVER GI4), Fara #467, ZATU .eps image Fara #234 (BU OVER BU) Examples of (SIGN CROSSING SIGN) Labat #99a2 (EN CROSSING EN).(IM CROSSING IM) Labat #169 DAH = (MU CROSSING MU), Fara #15, ZATU sign #66 Labat #371a SIRSIR looks as if it might be a special fused form of one sign over or crossing itself. Labat #374 RI8 = (MU$ CROSSING MU$), Fara #236 Labat #383a TALTAL = PI CROSSING PI Labat #399x (IM CROSSING IM) (because of merger, perhaps better: NI2
CROSSING NI2) Labat #569 SUH3 = (GU CROSSING GU), Fara #510 Etymological examples which were no longer transparent
SIGN OVER SIGN NIR = *(NUN OVER NUN) Examples of (SIGN OVER SIGN) where an attempt to divide
the total horizontally as (Component.Component) is not supported by
listed signs. Labat #441a (UL OVER UL) (source?) (KAD5 OVER KAD5) Labat #87c ($ILAM OVER $ILAM) Examples of (SIGN OVER SIGN) where neither way of making a first division is supported by listed signs. Labat #567a appears like (SIG4 OVER SIG4).SHU2. Ellermeier #449_46 DIMSAR ?? = (IGI.SHIR.gunu.PUR2) OVER (IGI.SHIR.gunu.PUR2). All of the three elements exist independently, but none of them doubled as SIGN OVER SIGN is listed as an independent sign. Labat #369 (SHE.GAD.GAR) OVER (SHE.GAD.GAR). Labat #370 (SHE.TAB.GAR) OVER (SHE.TAB.GAR) Labat #566b (LUM.GAR) OVER (LUM.GAR) Labat #144f ZIZNA = (TUR.ZA OVER TUR.ZA) Problem examples (suggest simply coding and naming as single signs, at least until a better analysis is pointed to?) Ellermeier #375_46 NINNI5.KINDA = (TIR OVER TIR).KINDA. Labat #125a UBISHAGA (is this a deformation of an unrecognized sign when stacked one above another?) Labat #99b2 MERMER5 (unknown parts, and a completely unique arrangement ((X.X) over (Y.Y)) Labat #99b3 GASHMU looks like (ASH.TUG2.TUG2.ASH) CROSSING (ASH.TUG2.TUG2.ASH) HILIBU (? source for listing ?) appears to be (SHU.SHU.tenu) over (SHU.SHU.tenu), |