Links from the original languages to Translation Words. Previously the links in UHB and UGNT were used (but that didn't enable them to be customized for Gateway Languages).
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Robert Hunt 6033264935 Refresh with latest data 1 week ago
1CH_twl.tsv Refresh after publishing 1 month ago
1CO_twl.tsv Fixed occurrence bug for phrases 1 month ago
1JN_twl.tsv Refresh after publishing 1 month ago
1KI_twl.tsv Refresh after publishing 1 month ago
1PE_twl.tsv Refresh after publishing 1 month ago
1SA_twl.tsv Refresh after publishing 1 month ago
1TH_twl.tsv Fixed occurrence bug for phrases 1 month ago
1TI_twl.tsv Refresh after publishing 1 month ago
2CH_twl.tsv Refresh after publishing 1 month ago
2CO_twl.tsv Refresh after publishing 1 month ago
2JN_twl.tsv Refresh after publishing 1 month ago
2KI_twl.tsv Refresh after publishing 1 month ago
2PE_twl.tsv Refresh after publishing 1 month ago
2SA_twl.tsv Refresh after publishing 1 month ago
2TH_twl.tsv Fixed occurrence bug for phrases 1 month ago
2TI_twl.tsv Refresh with latest data 1 week ago
3JN_twl.tsv Refresh after publishing 1 month ago
ACT_twl.tsv Fixed occurrence bug for phrases 1 month ago
AMO_twl.tsv Refresh after publishing 1 month ago
COL_twl.tsv Fixed occurrence bug for phrases 1 month ago
DAN_twl.tsv Refresh after publishing 1 month ago
DEU_twl.tsv Refresh after publishing 1 month ago
ECC_twl.tsv Refresh after publishing 1 month ago
EPH_twl.tsv Refresh with latest data 1 week ago
EST_twl.tsv Refresh after publishing 1 month ago
EXO_twl.tsv Refresh after publishing 1 month ago
EZK_twl.tsv Refresh after publishing 1 month ago
EZR_twl.tsv Fixed occurrence bug for phrases 1 month ago
GAL_twl.tsv Refresh after publishing 1 month ago
GEN_twl.tsv Refresh with latest data 1 week ago
HAB_twl.tsv Refresh after publishing 1 month ago
HAG_twl.tsv Refresh after publishing 1 month ago
HEB_twl.tsv Refresh after publishing 1 month ago
HOS_twl.tsv Refresh after publishing 1 month ago
ISA_twl.tsv Refresh after publishing 1 month ago
JAS_twl.tsv Refresh after publishing 1 month ago
JDG_twl.tsv Refresh after publishing 1 month ago
JER_twl.tsv Refresh after publishing 1 month ago
JHN_twl.tsv Fixed occurrence bug for phrases 1 month ago
JOB_twl.tsv Refresh after publishing 1 month ago
JOL_twl.tsv Refresh after publishing 1 month ago
JON_twl.tsv Refresh after publishing 1 month ago
JOS_twl.tsv Refresh after publishing 1 month ago
JUD_twl.tsv Refresh after publishing 1 month ago
LAM_twl.tsv Refresh with latest data 1 week ago
LEV_twl.tsv Refresh after publishing 1 month ago
LICENSE.md Initial commit 2 months ago
LUK_twl.tsv Refresh with latest data 1 week ago
MAL_twl.tsv Refresh after publishing 1 month ago
MAT_twl.tsv Fixed occurrence bug for phrases 1 month ago
MIC_twl.tsv Refresh after publishing 1 month ago
MRK_twl.tsv Refresh after publishing 1 month ago
NAM_twl.tsv Refresh after publishing 1 month ago
NEH_twl.tsv Refresh after publishing 1 month ago
NUM_twl.tsv Refresh after publishing 1 month ago
OBA_twl.tsv Refresh after publishing 1 month ago
OBS_twl.tsv First commit 2 months ago
PHM_twl.tsv Refresh after publishing 1 month ago
PHP_twl.tsv Fixed occurrence bug for phrases 1 month ago
PRO_twl.tsv Refresh after publishing 1 month ago
PSA_twl.tsv Refresh after publishing 1 month ago
README.md First attempt to customise ReadMe 2 months ago
REV_twl.tsv Fixed occurrence bug for phrases 1 month ago
ROM_twl.tsv Fixed occurrence bug for phrases 1 month ago
RUT_twl.tsv Refresh after publishing 1 month ago
SNG_twl.tsv Refresh after publishing 1 month ago
TIT_twl.tsv Refresh after publishing 1 month ago
ZEC_twl.tsv Refresh after publishing 1 month ago
ZEP_twl.tsv Refresh with latest data 1 week ago
manifest.yaml Invalid Fix NT validation demo errors 1 month ago

README.md

en_twl

Links from the original languages to Translation Words.

Previously the links in UHB and UGNT were used (but that didn’t enable them to be customized for Gateway Languages).

Editing the UTN

To edit the UTN files there are three options:

  • Use LibreOffice (Recommended)
  • Use a text editor on your computer
  • Use the online web editor in DCS

Each of these options and their caveats are described below.

The first two options require you to clone the repository to your computer first. You may do this on the command line or using a program such as SmartGit. After making changes to the files you will need to commit and push your changes to the server and then create a Pull Request to merge them to the master branch.

Alternately, you may download the master branch as a zip file and extract that locally. After editing you would need to use the upload file feature in DCS to get your changes ready for a Pull Request.

Editing in LibreOffice

This is the recommended way to edit the TSV files. You may download LibreOffice for free.

After you have the file on your computer, you may open the respective TSV file with LibreOffice. Follow these notes on the Text Import Screen:

  • Set “Separated by” to “Tab”
  • Set “Text Delimiter” to blank, you will need to highlight the character and use backspace or delete to remove it

It should look like this:

When you are done editing, click Save and then select “Use Text CSV Format” on the pop up dialogue. Note that even though it says CSV, it will use tab characters as the field separators.

Note: Other spreadsheet editors should not be used because they will add or remove quotation marks which will affect the entries negatively.

Editing in a Text Editor

You may also use a regular text editor to make changes to the files.

Note: You must be careful not to delete or add any tab characters when editing with this method.

Editing in DCS

If you only need to change a word or two, this may be the quickest way to make your change. See the protected branch workflow document for step by step instructions.

Note: You must be careful not to delete any tab characters when editing with this method.

Structure

The UTWL are structured as TSV files to simplify importing and exporting into various formats for translation and presentation. This enables the tWLs to be keyed to the original Greek and Hebrew text instead of only a Gateway Language translation.

TSV Format Overview

A Tab Separated Value (TSV) file is like a Comma Separated Value file except that the tab character is what divides the values instead of a comma. This makes it easier to include prose text in the files because many languages require the use of commas, single quotes, and double quotes in their sentences and paragraphs.

The UTWL are structured as one file per book of the bible and encoded in TSV format, for example, GEN_twl.tsv. The columns are Reference, ID, Tags, SupportReference, Quote, Occurrence, and OccurrenceNote.

UTN TSV Column Description

The following lists each column with a brief description and example.

  • Reference – Chapter number (e.g. 1) then colon then verse number (e.g. 3) or intro
  • ID – Four character alphanumeric string unique within the verse for the resource (e.g. swi9)
    • This will be helpful in identifing which links came from the English resources and which links have been added by GLs.
    • The Universal ID (UID) of a note is the combination of the Book, Chapter, Verse, and ID fields. For example, tit/1/3/swi9.
      • This is a useful way to unambiguously refer to links.
      • An RC link can resolve to a specific note like this: rc://en/tn/help/tit/01/01/swi9.
  • Tags – (optional) any of keyterm or name, separated by ; if there’s more than one
  • SupportReference
    • A link to a translation word, like rc://*/tw/dict/bible/names/paul or rc://*/tw/dict/bible/kt/pray
  • OrigQuote – Original language quote (e.g. ἐφανέρωσεν↔τὸν λόγον αὐτοῦ)
    • Software (such as tC) should use this for determining what is highlighted
    • An left right arrow character (↔) indicates that the quote is discontinuous, software should interpret this in a non-greedy manner
  • Occurrence – Specifies which occurrence in the original language text the entry applies to.
    • -1: entry applies to every occurrence of OrigQuote in the verse
    • 0: entry does not occur in original language (for example, “Connecting Statement:”)
    • 1: entry applies to first occurrence of OrigQuote only
    • 2: entry applies to second occurrence of OrigQuote only
    • etc.
  • Annotation – not used for Translation Word Links