Skip to content

Allow character data + editorial elements in <cit> #2912

Description

@martinascholger

In our digital edition project of a 17th-century Spanish–Chinese dictionary, we follow the Lex-0 recommendations for the encoding of example sentences and their translations using <cit>, see https://lex-0.org/translations.html.

Currently, character data and transcriptional, editorial and milestone elements (e.g., <choice>, <supplied>, <lb>, etc.) are not allowed directly within . This limitation prevents us from encoding short connective phrases that occur between citations like “por” (for) or “quiere decir que” (meaning that) or “se llama” (this means) including editorial changes. These phrases are part of the original textual record and are important for representing the original structure.

We would therefore like to propose

  1. allowing character data within <cit> to represent the original textual record
  2. allow structural sub-elements within <cit> from model.choicePart (and choice) for the “editorial view” (https://www.tei-c.org/release/doc/tei-p5-doc/en/html/DI.html#DIMVTV) of the dictionary.
  3. allowing members of model.milestoneLike (in our case especially <lb/> and <pb/>) for the typographical view.
<cit type="example" xml:lang="nan-Latn-PH">
    <quote>Bi ric. Cho. hon teyi. chun toa[*] Tayi[*]. peng</quote>

        quiere de<choice><orig>z</orig><reg>c</reg></choice>ir que

    <cit type="translation" xml:lang="es-Latn-PH">
        <quote>En Su tiempo Tu<choice><orig>b</orig><reg>v</reg></choice>o lo dicho.</quote>
    </cit>
</cit> 


<cit type="example" xml:lang="es-Latn-PH">      
  <quote>La miEl de canas</quote>

      se<supplied> </supplied>lla<lb  break="no"/>ma<pc>.</pc>

 <cit type="translation" xml:lang="nan-Latn-PH">
      <quote>Tung[*]. Chuy</quote>
  </cit>
</cit>

See also discussion at LingSig Meeting in Krakow: #2815

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions