-
Notifications
You must be signed in to change notification settings - Fork 4
Home
Welcome to the Wiki of Luis Enrique Sam Colop's 1999 Poetic K'iche' Edition of the Popol Wuj!
¡Bienvenidxs al Wiki de la edición poética K’iche’ 1999 del Popol Wuj por Luis Enrique Sam Colop !
Si gusta leer en español, haz clic aquí
Topics discussed:
- Parts
- Sections
- Individual lines and alignment
- Pagebreaks
- Notes
Colop divides the text into five parts. These parts are numbered and named in K'iche', with the following order:
- Nab'e
- Ukab'
- Rox
- Ukaj
- Ro'
These parts are encoded at minimum using the following element and attributes: <div type="nima-tasik">. Here, the type attribute is set to mean "major section". This element is the largest division of the text.
Immediately after this element, the name of the part will be encoded in a <head> element. For instance:
<div type="nima-tasik">
<head>NAB'E</head>
Sections are the next level of division in the text. They are signaled in the text through grey bolded uppercase lines. These sections will be encoded using the <lg> element, with a @type attribute set to "tasik" (meaning "section" in K'iche', as recommended by scholar Ajpub' Pablo García Ixmatá), and an @xml:id attribute set to lgPART.SECTION, e.g. the first section in part 1 (NAB'E) would be lg1.01.
The header of the section is both a header and part of the text itself. Here we will mention how the section title interacts with the text, and how each case will be encoded. In particular, the <seg> element will signal the header while not interrupting the flow of the text.
Case 1: Section titles separate from non-bolded text
In the case that the section title does not interact with non-bolded text, the title will be encoded as regular lines, but using a <seg> element with the following attributes: <seg rend='caps' type='uwach-tasik'>. Here, the type attribute set to uwach-tasik means "section-header". For instance, the following section (Colop 1999: 22):
<lg n='0' xml:id='lg01' type='tasik'>
<l n='1'><seg rend='caps' type='uwach-tasik'>ARE' UXE' OJER TZIJ WARAL K'ICHE' UB'I'</seg></l>
Case 2: Section titles interact with non-bolded text
Consider the following beginning of a section :
K'EJE K'UT UTIJTOB'EXIK CHIK WINAQ TZ'AQ
WINAQ B'IT KUMAL Tz'aqol
B'itol;
Alom,
K'ajolom;
(Colop 1999: 30)
To properly encode the distinction between the header text and the non-header text, we will end the <seg> element after the final bolded text.
<lg xml:id='lg0PART.SECTION' type='tasik'>
<l n='x'><seg rend='caps' type='uwach-tasik'>K'EJE K'UT UTIJTOB'EXIK CHIK WINAQ TZ'AQ,</l>
<l n='x+1'><space quantity="29" unit="chars" /><seg rend='caps' type='uwach-tasik'>WINAQ B'IT KUMAL</seg> Tz'aqol</l>
<l n='x+2'><space quantity="46" unit="chars" />B'itol;</l>
<l n='x+3'><space quantity="46" unit="chars" />Alom,</l>
<l n='x+4'><space quantity="46" unit="chars" />K'ajolom;</l>*
*The use of the <space> element will be discussed below.
Colop's edition of the Popol Wuj uses individual line alignment to show the poetic groupings that occur throughout the text. This is done primarily through indentation, with the highlighted word or word-part (morpheme, specifically) aligned with the proper grouping. We lay out some examples below:
Case 1: Basic word alignment
K'o nab'e wujil,
ojer tzib'am puch,
xa ewal uwach ilol re,
b'isol re.
Había un libro original,
que fue escrito antiguamente,
sólo que están ocultos quienes lo leen
quienes lo interpretan.
(Colop 1999: 22; Colop 2007: 23)
Case 2: word-part/morpheme alignment
xa ajkun xk'amowik ri k'uwal,
yamanik,
fue un médico quien tomó sus joyas y
sus gemas;
(Colop 1999: 45; Colop 2007: 50)
In order to encode what Sam Colop calls semantic rhyme, these alignments will be preserved through the <space> TEI element. This allows us to show intentful alignment using characters as the base units. Using a Python algorithm on an accurately indented plaintext version of the text, we can generate the number of character whitespaces necessary to align these lines. The encoding of the above examples would thus be:
Case 1 Encoding
<l n='x'>K'o nab'e wujil,</l>
<l n='x+1'>ojer tzib'am puch,</l>
<l n='x+2'>xa ewal uwach ilol re,</l>
<l n='x+3'><space quantity='14' unit='chars' />b'isol re.</l>
Case 2 Encoding
<l n='x'>xa ajkun xk'amowik ri k'uwal,</l>
<l n='x+1'><space quantity='11' unit='chars' />yamanik</l>
While this encoding of Colop's edition of the Popol Wuj captures the logical form of the text, it may serve useful in different visual versions of the text to preserve the page breaks from the original text. To this end, we encode these breaks as milestones using the <pb> element with an @xml:id attribute set to a unique identifier of the page. For instance, page 24 of the text would have the milestone <pb xml:id="colop1999-024".
Notes are signaled in the text by a superscript number following the relevant term(s), and a corresponding note body in either the left or right margin of the page. Following the U.Va. Library TEI Encoding Guidelines, we distinguish between the note reference, often represented as a superscripted number above the target word or phrase, and the note body, the content of the note itself.
Within the note reference, superscript numbers will be marked with a <ref> element with a corresponding target attribute that matches the unique xml:id attribute of the note body. Marking up the superscripted number is done with an <hi> element with a corresponding rend attribute set equal to superscript.
The note body immediately follows the referenced line. This is marked up with a <note> element, with the corresponding unique attribute xml:id set equal to n and the superscripted number, padded with 0's to 3 digits (e.g. note 37 appears as n037), and the attribute place set equal to which margin the note appears on (left or right). The <note> element is followed by a <seg> and <hi> element to mark the superscript number, and the note contents. The note contents are then encoded as it is formatted in the text.
See the below example:
<l n='x'>-Maja b'i qab'i, xa ojub'om<ref target='n109'><hi rend='superscript'>109</hi></ref>,</l>
<note xml:id='n109' place='right'><seg type='note-symbol'><hi rend='superscript'>109</hi></seg>'Somos cerbataneros/cazadores'; viene de <hi rend="bold">ub' ~ wub'</hi>, cerbatana'.</note>
<l n='x+1'>...</l>