Skip to content

Home

Jump to bottom
Aldo Ismael Barriente edited this page Jul 7, 2021 · 15 revisions

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’ del Popol Wuj por Luis Enrique Sam Colop del 1999!

Si gusta leer en español, haz clic aquí

Encoding Conventions and Guidelines

  1. Parts
  2. Sections
  3. Individual lines and alignment
  4. Pagebreaks
  5. Notes

1. Parts

Colop divides the text into five parts. These parts are numbered and named in K'iche', with the following order:

  1. Nab'e
  2. Ukab'
  3. Rox
  4. Ukaj
  5. Ro'

These parts are encoded at minimum using the following element and attributes: <div type="part">. This element is the largest division of the text. For easier future processing, these parts will also have an @n attribute corresponding to their order.

Immediately after this element, the name of the part will be encoded in a <head> element. For instance:

<div type="part" n="1">
    <head>NAB'E</head>

2. Sections

Sections are the next level of division in the text. They are signaled in the text through bolded lines. This means that the "title" 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='section-header'>. For instance, the following section (Colop 1999: 22):

<lg n='0' xml:id='lg01' type='section'>
    <l n='1'><seg rend='caps' type='section-header'>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 n='y' xml:id='lg0y' type='section'>
<l n='x'><seg rend='caps' type='section-header'>K'EJE K'UT UTIJTOB'EXIK CHIK WINAQ TZ'AQ,</l>
<l n='x+1'><space quantity="29" unit="chars" /><seg rend='caps' type='section-header'>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>

3. Individual lines and alignment

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>

4. Page breaks

5. Notes

Clone this wiki locally