-
Notifications
You must be signed in to change notification settings - Fork 11
translationWords based on Greek Strong's Workflow
Christopher Klapp edited this page Jul 24, 2017
·
1 revision
- tW article occurrences based off of Greek/Strong's numbers.
a. tW articles include a list of covered Strong's Numbers.
b. Generate a list of checks for each tW article based on Strong's Number occurrences.
c. Find Strong's conflicts and determine which article applies.
- Strong's conflict is the same number in multiple articles. Which one applies?
- Conflict may be resolved using English occurrences that were already generated.
- Store resulting list in the data.
- tW checks based off of filtered Greek/Strong's occurrences list.
- Import script converts them into tC
groupData
JSON format.
- Import script converts them into tC
- Use the new list of words and occurrences in tW based off of Greek.
- Update scripts to import and generate the index and all groupData.
- Update tW UI.
- Check Info card to include Greek and English word info.
- Build the tool.
- Save the data.
- If using USFM 3 word markers, it is added to existing data.
- Recommend auto exporting of USFM to ease tX publishing.
- If using another data format such as CSV, it will require additional planning.
Without this step, English will not have highlighted words/phrases. This may seem like a step back but it is confirming that the ULB is ready as a GL. This also forces us to follow the same path for adding English ULB as a checking reference Bible the same way all GL reference Bibles will be added. Thus giving tested directions to the GL resource teams in preparing for tC.
- English ULB is aligned to Greek using new tC aligner tool.
- Data stored in the target language using USFM 3 word markers.
- English ULB is checked using Greek/Strongs version of tW.
- Data stored in the selections/highlights of the target, English ULB, will be used for future highlighting.
- Update tC to import alignment and selections data.
- English ULB checking data for alignments to be exposed in DCS v3 API.
- If using USFM 3 word markers, this can be an update to existing USFM data.
- If using CSV or JSON, this will require another set of files to be published.
- Update tC resources reducer to include alignment data if not in USFM 3 word markers.
- Maybe English ULB checking data for tW selections to be exposed in DCS v3 API.
- English ULB checking data for alignments to be exposed in DCS v3 API.
- Update tC Scripture Pane to highlight reference Bibles with alignment data.
- Highlight Greek occurrence based off of tW check data.
- Highlight the GL occurrence based off of linking to Greek occurrence.
- Update tW to use both Greek and GL data (covered above).