Layout oriented determine plain meaning
MJ. Smith
MVP Posts: 54,536 
Note that Logos already provides Guide Sections which would be useful as supporting documentation along side the text window.
1. Starting view: English/Original language in parallel with the ability to spin through the following views much as I can spin through parallel resources.
2. See with a filter identifying the original language variants in the manuscripts - this shows me where translations are most apt to varies because of different choices for the underlying text.
2a. A simplified version of this filter would show only the current critical text, the Textus Receptus, and the Patriarchal Text as variations
3. See with a filter identifying all the ambiguous lemmas, homographs, etymological components (etymological affixes), and polyvalent lemmas. Yes, this clumps a number of items together but they all relate to finding the right word with the right meaning. It allows me to make judgments without undue pressure from the interlinears.
4. See with a filter identifying ambiguous morphology. Again, it allows me to learn to read an unparsed text and to make my own judgments without undue pressure from the interlinears.
5. See in a format showing me the variations in the translations based on the different traditions: Jewish, Dead Sea, Targum, Septuagint, Peshitta, Vulgate
6. See with a filter identifying polymorphemic words (compound words), idioms, fixed order phrases, et. al. i.e. allowing me to identify the true "words" of the text rather than the typographic words.
7. See with a filter identifying words and phrases that are likely figurative rather than literal in nature.
8. See with a filter identifying probable semantic roles and case frames - with access in a side panel to the case frames available to the verb.
9. A probable arrow arc dependency syntactic diagram - note this format fits much better on a screen and is easy for the user to manipulate.
10. See with a filter identifying words generally given non-literal meaning because of reading the text canonically, in light of the cross ... e.g. "Holy Spirit" used anachronously in the Old Testament. It should also show words generally given multiple meanings because of reading the text prophetically.
This is the point where I think I've probably found the plain meaning of the text. I suspect my workflow could be improved by experienced scholars in the original language/early translations texts.
Example of arrow arc dependency syntax diagram is attached - the current syntax data should be able to be mapped into this style of presentation.
1. Starting view: English/Original language in parallel with the ability to spin through the following views much as I can spin through parallel resources.
2. See with a filter identifying the original language variants in the manuscripts - this shows me where translations are most apt to varies because of different choices for the underlying text.
2a. A simplified version of this filter would show only the current critical text, the Textus Receptus, and the Patriarchal Text as variations
3. See with a filter identifying all the ambiguous lemmas, homographs, etymological components (etymological affixes), and polyvalent lemmas. Yes, this clumps a number of items together but they all relate to finding the right word with the right meaning. It allows me to make judgments without undue pressure from the interlinears.
4. See with a filter identifying ambiguous morphology. Again, it allows me to learn to read an unparsed text and to make my own judgments without undue pressure from the interlinears.
5. See in a format showing me the variations in the translations based on the different traditions: Jewish, Dead Sea, Targum, Septuagint, Peshitta, Vulgate
6. See with a filter identifying polymorphemic words (compound words), idioms, fixed order phrases, et. al. i.e. allowing me to identify the true "words" of the text rather than the typographic words.
7. See with a filter identifying words and phrases that are likely figurative rather than literal in nature.
8. See with a filter identifying probable semantic roles and case frames - with access in a side panel to the case frames available to the verb.
9. A probable arrow arc dependency syntactic diagram - note this format fits much better on a screen and is easy for the user to manipulate.
10. See with a filter identifying words generally given non-literal meaning because of reading the text canonically, in light of the cross ... e.g. "Holy Spirit" used anachronously in the Old Testament. It should also show words generally given multiple meanings because of reading the text prophetically.
This is the point where I think I've probably found the plain meaning of the text. I suspect my workflow could be improved by experienced scholars in the original language/early translations texts.
Example of arrow arc dependency syntax diagram is attached - the current syntax data should be able to be mapped into this style of presentation.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Tagged:
2
Comments
-
This tool is useful to (1) make one's own translation (2) determine how a particular translation handled the text and (3) determine why multiple translations differ. Ultimately a second portion in which the user's choices built an interlinear + translation with the ability to add notes to each element would make it a decent student translation tool.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0