Prepare to publish v44 Co-authored-by: Robert Hunt <Freely.Given.firstname.lastname@example.org> Reviewed-on: #1698 Co-Authored-By: Robert Hunt <email@example.com> Co-Committed-By: Robert Hunt <firstname.lastname@example.org>
|3 days ago|
|.github||2 months ago|
|LICENSE.md||1 month ago|
|README.md||3 days ago|
|en_tn_01-GEN.tsv||9 months ago|
|en_tn_02-EXO.tsv||1 month ago|
|en_tn_03-LEV.tsv||9 months ago|
|en_tn_04-NUM.tsv||9 months ago|
|en_tn_05-DEU.tsv||1 month ago|
|en_tn_06-JOS.tsv||9 months ago|
|en_tn_07-JDG.tsv||1 month ago|
|en_tn_08-RUT.tsv||2 months ago|
|en_tn_09-1SA.tsv||1 month ago|
|en_tn_10-2SA.tsv||1 month ago|
|en_tn_11-1KI.tsv||9 months ago|
|en_tn_12-2KI.tsv||9 months ago|
|en_tn_13-1CH.tsv||9 months ago|
|en_tn_14-2CH.tsv||9 months ago|
|en_tn_15-EZR.tsv||3 days ago|
|en_tn_16-NEH.tsv||1 month ago|
|en_tn_17-EST.tsv||1 month ago|
|en_tn_18-JOB.tsv||9 months ago|
|en_tn_19-PSA.tsv||9 months ago|
|en_tn_20-PRO.tsv||9 months ago|
|en_tn_21-ECC.tsv||9 months ago|
|en_tn_22-SNG.tsv||9 months ago|
|en_tn_23-ISA.tsv||1 month ago|
|en_tn_24-JER.tsv||9 months ago|
|en_tn_25-LAM.tsv||9 months ago|
|en_tn_26-EZK.tsv||9 months ago|
|en_tn_27-DAN.tsv||9 months ago|
|en_tn_28-HOS.tsv||9 months ago|
|en_tn_29-JOL.tsv||7 months ago|
|en_tn_30-AMO.tsv||9 months ago|
|en_tn_31-OBA.tsv||2 months ago|
|en_tn_32-JON.tsv||1 month ago|
|en_tn_33-MIC.tsv||9 months ago|
|en_tn_34-NAM.tsv||9 months ago|
|en_tn_35-HAB.tsv||9 months ago|
|en_tn_36-ZEP.tsv||9 months ago|
|en_tn_37-HAG.tsv||9 months ago|
|en_tn_38-ZEC.tsv||9 months ago|
|en_tn_39-MAL.tsv||9 months ago|
|en_tn_41-MAT.tsv||9 months ago|
|en_tn_42-MRK.tsv||9 months ago|
|en_tn_43-LUK.tsv||4 months ago|
|en_tn_44-JHN.tsv||3 months ago|
|en_tn_45-ACT.tsv||3 months ago|
|en_tn_46-ROM.tsv||1 month ago|
|en_tn_47-1CO.tsv||9 months ago|
|en_tn_48-2CO.tsv||1 month ago|
|en_tn_49-GAL.tsv||9 months ago|
|en_tn_50-EPH.tsv||1 week ago|
|en_tn_51-PHP.tsv||9 months ago|
|en_tn_52-COL.tsv||9 months ago|
|en_tn_53-1TH.tsv||9 months ago|
|en_tn_54-2TH.tsv||9 months ago|
|en_tn_55-1TI.tsv||1 month ago|
|en_tn_56-2TI.tsv||1 week ago|
|en_tn_57-TIT.tsv||1 month ago|
|en_tn_58-PHM.tsv||9 months ago|
|en_tn_59-HEB.tsv||9 months ago|
|en_tn_60-JAS.tsv||9 months ago|
|en_tn_61-1PE.tsv||9 months ago|
|en_tn_62-2PE.tsv||9 months ago|
|en_tn_63-1JN.tsv||9 months ago|
|en_tn_64-2JN.tsv||2 weeks ago|
|en_tn_65-3JN.tsv||1 month ago|
|en_tn_66-JUD.tsv||9 months ago|
|en_tn_67-REV.tsv||9 months ago|
|manifest.yaml Valid||3 days ago|
|media.yaml||2 years ago|
This is the repository for the unfoldingWord® Translation Notes (UTN) resource.
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.
To edit the UTN files there are three options:
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
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.
This is the recommended way to edit the TSV files. tC Create is a web-based application that you can access here. NOTE: you need to have a Door43 account in order to use tC Create.
Once you log in, simply follow the prompts to open the file you wish to edit.
When you are done editing, click Save button at the top right corner of the screen.
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.
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. Also, you CANNOT manually input the tab characters using the tab bar on your keyboard, because DCS will save them as spaces and not as tab separators. The best way to insert tab separators is by copying and pasting tab characters from an existing tNote.
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.
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
The following lists each column with a brief description and example.
Book- USFM book code name (e.g.
Chapter- Chapter number (e.g.
Verse- Verse number (e.g.
ID- Four character alphanumeric string unique within the verse for the resource (e.g.
IDfields. For example,
OrigQuote- Original language quote (e.g.
ἐφανέρωσεν…τὸν λόγον αὐτοῦ)
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
GLQuote(OPTIONAL) - Gateway language quote (e.g.
he revealed his word)
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]])
Below are a few formatting guidelines that govern the composition of transationNotes.
Here are some important technical notes to keep in mind as you translate tN:
OccurrenceNotecolumn needs to be translated
GLQuotecolumn 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.
As a translator of UTN into a GL, you may need to add new notes. Follow these steps to do this:
Add a new row in the correct book, chapter, verse order.
Fill out each field for the row according to the UTN TSV Column Description above, taking note of these instructions:
IDfor this note, which must unique among the notes in the verse.
GLQuotefield. Have a reviewer who knows Greek and your GL come back and add the approprate text from the UGNT that the note refers to.
See the LICENSE file for licensing information.