From Open Siddur Project Development Wiki

The Contributors to the Open Siddur Project, the copyright holder of this work, has published or hereby publishes it under the following licenses: This work is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or any later version. This work is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See version 3 of the GNU General Public License for more details. Deutsch | Deutsch (Sie-Form) | English | Français | +/− This file is licensed under the Creative Commons Attribution ShareAlike 3.0 License. In short: you are free to share and make derivative works of the file under the conditions that you appropriately attribute it, and that you distribute it only under a license identical to this one. Official license العربية | Български | Català | Česky | Dansk | Deutsch | Ελληνικά | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | עברית | Hrvatski | Magyar | Italiano | 日本語 | 한국어 | Македонски | Plattdüütsch | Nederlands | Polski | Português | Русский | Slovenčina | Svenska | తెలుగు | ไทย | Tiếng Việt | Українська | ‪中文(简体)‬ | ‪中文(繁體)‬ | +/− You may select the license of your choice.

JLPTEI supports multilingual original texts and multilingual translations of the original texts.

Prerequisites

Conditional variable

Each translation must define a conditional variable to indicate to a processor whether the translation should be included. The condition must be a two-way switch, with valid values YES and NO. YES indicates that the translation is included, NO that it is not.

Statement of purpose

There are numerous styles of translation. It is strongly recommended (and required for translations in the core distribution) that a translation have its own statement of purpose. This statement should indicate whether the translation is intended to be idiomatic, creative, literal, etc.

Translation files

Translation files must meet all the requirements of other files. They must have a header, and they must have at least one text section. The base URI of translation files is http://jewishliturgy.org/base/text/translation/LANG/TRANSLATION_NAME/FILENAME . If necessary, translations may define their own conditionals in addition to those used in the original text.

LANG is the language code in which the translation is written. TRANSLATION_NAME is the name of the translation. FILENAME may be the same as the filename of the original text.

The translation text itself is stored in a JLPTEI file with concurrent hierarchies, in the same way as original text.

Forward linkage to translated text

Translations are generally stored in a different file from their original texts, and, in general, each file of original text may have any number of translations. In order for the translation to be processed, each translation must have one or more special support files, each of which contains links between the translation files and the files they translate. The links should be be under the conditional control of the translation's associated conditional variable.

These forward linkages are made using links of the form:

<tei:link type="parallel-file" targets="original-file-uri translation-file-uri"/>

Linkage

Translations may be aligned to arbitrary positions in a selection by using a parallel hierarchy in a translation linkage file. The translation linkage file contains a special j:concurrent parallel hierarchy, which includes:

• At least two selections incorporated by reference, using tei:ptr[@type='selection']
• One j:view[@type='parallelGrp'] view, which contains:
  • One or more j:parallelGrp tags, each containing:
    • One j:original tag, which includes singular or ranged references into the selection.
    • One j:parallel tag, which includes the parallel text or references to the parallel text.

Selection pointers

Each selection pointer has the form:

<tei:ptr type="selection" n="FILE_UNIQUE" target="ORIGINAL-SELECTION-URI"/>

The FILE_UNIQUE marker is used to tell which parallel chunks (either j:parallel or j:original) are linked to which selection.

Examples

<!-- in the linking settings file -->
<tei:link type="parallel-file" targets="original-file-uri translation-linkage-file-uri"/>
 
<!-- in the translation linkage file -->
<j:concurrent>
  <tei:ptr type="selection" n="FILE_UNIQUE_1" target="ORIGINAL-SELECTION-URI-1"/>
  <tei:ptr type="selection" n="FILE_UNIQUE_2" target="ORIGINAL-SELECTION-URI-2"/>
  <j:view type="parallelGrp">
    <j:parallelGrp>
      <j:original n="FILE_UNIQUE_1" xml:base="ORIGINAL-SELECTION-URI-1">
        <tei:ptr target="#range(originalSelection_part1_1, originalSelection_part1_N)"/>
      </j:original>
      <j:parallel n="FILE_UNIQUE_2" xml:base="ORIGINAL-SELECTION-URI-2">
        <tei:ptr target="#range(parallelSelection_part1_1, parallelSelection_part1_N)"/>
      </j:parallel>
    </j:parallelGrp>
    <!-- the second (optional) parallel group references different parts of the same selections -->
    <j:parallelGrp>
      <j:original n="FILE_UNIQUE_1" xml:base="ORIGINAL-SELECTION-URI-1">
        <tei:ptr target="#range(originalSelection_part2_1, originalSelection_part2_N)"/>
      </j:original>
      <j:parallel n="FILE_UNIQUE_2" xml:base="ORIGINAL-SELECTION-URI-2">
        <tei:ptr target="#range(parallelSelection1_part2_1, parallelSelection_part2_N)"/>
      </j:parallel>
    </j:parallelGrp>
    <!-- additional parallel groups go here -->
  </j:view>
</j:concurrent>

Generality

The method used for encoding translations may be used for any parallel-aligned text.