unfoldingWord® Translation Notes (9-column TSV format) https://www.unfoldingword.org/utn/
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.
Joel D. Ruark 08dfd0fd4c Remove extraneous backslash characters (#1545) 3 days ago
.github updated issue template 3 years ago
LICENSE.md Preparing for v29 prepublish 5 months ago
README.md Prepare for v35 -- some small syntax fixes (#1534) 1 week ago
en_tn_01-GEN.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_02-EXO.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_03-LEV.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_04-NUM.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_05-DEU.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_06-JOS.tsv Correct Hebrew snippet errors (#1385) 6 months ago
en_tn_07-JDG.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_08-RUT.tsv Prepare for v35 -- some small syntax fixes (#1534) 1 week ago
en_tn_09-1SA.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_10-2SA.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_11-1KI.tsv Fix format errors found by TX (#1383) 6 months ago
en_tn_12-2KI.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_13-1CH.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_14-2CH.tsv Fix format errors found by TX (#1383) 6 months ago
en_tn_15-EZR.tsv BP Editing [EZR] (#1490) 1 month ago
en_tn_16-NEH.tsv Remove extraneous backslash characters (#1545) 3 days ago
en_tn_17-EST.tsv Fix final warnings (#1541) 5 days ago
en_tn_18-JOB.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_19-PSA.tsv Fix format errors found by TX (#1383) 6 months ago
en_tn_20-PRO.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_21-ECC.tsv Fix format errors found by TX (#1383) 6 months ago
en_tn_22-SNG.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_23-ISA.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_24-JER.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_25-LAM.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_26-EZK.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_27-DAN.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_28-HOS.tsv Fix format errors that TX found (#1381) 6 months ago
en_tn_29-JOL.tsv Fixed invalid periods before tA links at the end of notes. (#1413) 4 months ago
en_tn_30-AMO.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_31-OBA.tsv Proofread BP [OBA] (#1544) 3 days ago
en_tn_32-JON.tsv Prepare for v35 -- some small syntax fixes (#1534) 1 week ago
en_tn_33-MIC.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_34-NAM.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_35-HAB.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_36-ZEP.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_37-HAG.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_38-ZEC.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_39-MAL.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_41-MAT.tsv Fix format errors that TX found (#1381) 6 months ago
en_tn_42-MRK.tsv Fix format errors that TX found (#1381) 6 months ago
en_tn_43-LUK.tsv Corrected zero-width and non-breaking spaces that tC-Create put in Luk, Tit, 1Ti, and 3Jn. (#1495) 1 month ago
en_tn_44-JHN.tsv RJHsmall1TiFixes (#1511) 3 weeks ago
en_tn_45-ACT.tsv RJHsmall1TiFixes (#1511) 3 weeks ago
en_tn_46-ROM.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_47-1CO.tsv Corrected Greek snippet errors found by TX (#1380) 6 months ago
en_tn_48-2CO.tsv Fix format errors that TX found (#1381) 6 months ago
en_tn_49-GAL.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_50-EPH.tsv Correct ellipsis errors in Ephesians notes (#1543) 3 days ago
en_tn_51-PHP.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_52-COL.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_53-1TH.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_54-2TH.tsv Corrected Greek snippet errors found by TX (#1380) 6 months ago
en_tn_55-1TI.tsv Corrected Bible link format in 1Ti (#1517) 3 weeks ago
en_tn_56-2TI.tsv Corrected Greek snippet errors found by TX (#1380) 6 months ago
en_tn_57-TIT.tsv fixMissingClosingParenthesis (#1536) 1 week ago
en_tn_58-PHM.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_59-HEB.tsv Corrected Greek snippet errors found by TX (#1380) 6 months ago
en_tn_60-JAS.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_61-1PE.tsv Fixed format errors found by TX (#1382) 6 months ago
en_tn_62-2PE.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_63-1JN.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_64-2JN.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_65-3JN.tsv fixMissingClosingParenthesis (#1536) 1 week ago
en_tn_66-JUD.tsv Remove stray breaks (<br>) after intros (#1379) 6 months ago
en_tn_67-REV.tsv Fix format errors that TX found (#1381) 6 months ago
manifest.yaml Valid Publish v36 (#1542) 5 days ago
media.yaml Updates for v14 (#1132) 1 year ago

README.md

drawing # unfoldingWord® Translation Notes

This is the repository for the unfoldingWord® Translation Notes (UTN) resource.

Description

unfoldingWord® Translation Notes are open-licensed exegetical notes that provide historical, cultural, and linguistic information for translators. It provides translators and checkers with pertinent, just-in-time information to help them make the best possible translation decisions.

Downloading

If you want to download the UTN to use, go here: https://www.unfoldingword.org/utn. UTN is also included in tS and tC.

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 notes 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 UTN are structured as TSV files to simplify importing and exporting into various formats for translation and presentation. This enables the tNs 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 UTN are structured as one file per book of the bible and encoded in TSV format, for example, 01-GEN.tsv. The columns are Book, Chapter, Verse, ID, SupportReference, OrigQuote, Occurrence, GLQuote, and OccurrenceNote.

UTN TSV Column Description

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

  • Book - USFM book code name (e.g. TIT)
  • Chapter - Chapter number (e.g. 1)
  • Verse - Verse number (e.g. 3)
  • ID - Four character alphanumeric string unique within the verse for the resource (e.g. swi9)
    • This will be helpful in identifing which notes are translations of the original English tNs and which notes 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 notes.
      • An RC link can resolve to a specific note like this: rc://en/tn/help/tit/01/01/swi9.
  • SupportReference
    • Normally a link to a supporting reference text or blank
    • This will usually be a link to translationAcademy, like rc://*/ta/man/translate/figs-metaphor
  • OrigQuote - Original language quote (e.g. ἐφανέρωσεν…τὸν λόγον αὐτοῦ)
    • Software (such as tC) should use this for determining what is highlighted rather than using the GLQuote field
    • An ellipsis 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.
  • GLQuote (OPTIONAL) - Gateway language quote (e.g. he revealed his word)
    • Software (such as tC) should disregard this field.
    • This field is a reference text for GL translators
    • For certain notes, this field represents the display text for notes that do not relate to a specific word or phrase in the text. There are two such cases in the tN:
      • “Connecting Statement:” and
      • “General Information:”
    • GL translations teams should not translate this column. They do need to provide a translation of the above 2 statements.
  • OccurrenceNote - The Markdown formatted note itself. For example, Paul speaks of God’s message as if it were an object that could be visibly shown to people. Alternate translation: “He caused me to understand his message” (See: [[rc://en/ta/man/translate/figs-metaphor]])
    • The text should be Markdown formatted, which means the following are also acceptable:
      • Plaintext - if you have no need for extra markup, just use plain text in this column
      • HTML - if you prefer to use inline HTML for markup, that works because it is supported in Markdown

Composing translationNotes

Below are a few formatting guidelines that govern the composition of transationNotes.

  • All tNotes should reference ONLY a single translationAcademy article. If a second article needs to be referenced, an additional tNote should be added.
  • All tNotes should reference one of the “Just-in-Time” articles from translationAcademy, i.e., those with file names beginning with “figs-” or “grammar-” “translate-” or “writing-.”
  • The ULT term/concept being discussed in each Note should be in bold type, NOT in “quotation marks.”
  • Only use quotation marks to indicate suggested translations. Do not precede the suggestion with the word “that” (which turns them into indirect quotes) i.e., You could say that “they were planning to assassinate him.” Corrected to: You could say, “they were planning to assassinate him.”
  • It is not enough to enclose “for example” in commas mid sentence and follow it with an example, i.e., You can say this with an active form, for example, “Mordecai found out what they were planning.” Corrected to: You can say this with an active form such as “Mordecai found out what they were planning.” Another example might include: You can say this with an active form, and you can say who did the action. For example, you can say, “Then the king’s servants investigated Mordecai’s report and found out that it was true.”
  • When beginning a tNotes with the word “Here,” the term should be followed by a comma. For instance: “Here, the ULT term means __________.”
  • Do NOT include a period at the end of the “Alternate translation:” fragment at the end of a tNote. The “Alternate translation” should be formatted as a floating sentence fragment immediately followed by the translationAcademy hyperlink (if applicable), i.e., Alternation translation: “in the presence of Yahweh” (See: Metaphor)
  • When composing tNotes using tC Create, all hyperlinks should be typed in “Markdown” mode instead of “Preview” mode. Hyperlinks entered in Preview mode will not be saved in their proper format.
  • Scripture references within the same book should be referenced using both chapter and verse, separate by a colon, i.e. 3:16. To use this same example, the proper hyperlink format places the hyperlink text in brackets [3:16] immediately followed by the link itself in parentheses (../03/16.md). There should not be a space between the brackets and the parentheses.
  • The file name in the SupportReference field MUST be an exact match for the hyperlink at the close of the tNote. If they do not match, the link will not work properly.

GL Translators

tN Translation Philosophy

To learn the philosophy of how to translate these notes please see the Translate the translationNotes article in the Gateway Language Manual.

tN Translation Notes

Here are some important technical notes to keep in mind as you translate tN:

  • Only the OccurrenceNote column needs to be translated
  • Do not remove any column in the TSV files
  • You will also need to supply a translation of these 2 phrases which are repeated, “Connecting Statement:” and “General Information:”.
    • These phrases occur many times in the GLQuote column.
    • You may want to use find and replace to update the English text with your GL text. If not, we can do this when preparing the text for publishing.
  • Remember: the GLQuote column is not required to be filled out. Only use this field if it is helpful during the translation process. The software that processes the tNs will use alignment data to identify which words in your GL translation the individual notes refer to.

The section above on Editing the tNs may give you ideas on what software to use. Of course, you can also convert the TSV files into another format, do the translation, and then convert them back to TSV files (just ensure the IDs are preserved if you do this). Follow Translate Content Online to get a copy of this repository to begin your work.

Add Notes

As a translator of UTN into a GL, you may need to add new notes. Follow these steps to do this:

  1. Add a new row in the correct book, chapter, verse order.

  2. Fill out each field for the row according to the UTN TSV Column Description above, taking note of these instructions:

    • Choose a new ID for this note, which must unique among the notes in the verse.
    • If you don’t know Greek, put the GL text that the note refers to in the GLQuote field. Have a reviewer who knows Greek and your GL come back and add the approprate text from the UGNT that the note refers to.

License

See the LICENSE file for licensing information.