Multilingual Alignment

Overview:

To fully understand the basis of the proposal, the following problems respective solutions are fundamental.

The previous mindset

• Quotes come from the tool's resources.
• The quotes come from and confirmed with each release of the ULB.
• Alignment data from ULB => UGNT => UDB used to generate quotes.
  • For UGNT, reference ULB => UGNT alignment data to get which UGNT word(s) to highlight.
  • For UDB, reference UGNT => UDB alignment data to get which UDB words(s) to highlight.
• The tW articles for each word include Strongs numbers that could be used for highlighting/confirming UGNT.

Problems and Solutions

1. Problem: Complicated mapping of languages.
   • Solution: Pivot on UGNT.
2. Problem: Dual workflows for English and Gateway languages is just way too complicated.
   • Solution: Treat English as a Gateway Language, so there is only one workflow.
3. Problem: English isn't treated like Gateway languages because all checks are based on it.
   • Solution: Base all checks off of UGNT and treat English as a Gateway Language.
4. Problem: English is being elevated and treated as the source when it really is a gateway.
   • Solution: Base all checks off of UGNT and treat English as a Gateway Language.
5. Problem: English ULB is changing at a steady pace and invalidates checks when updated.
   • Solution: Base all checks off of UGNT and treat English as a Gateway Language.
6. Problem: Basing checks off of UGNT requires alignment data.
   • Solution: Align the ULB to UGNT and then confirm the checks are valid.

What the future holds

Now imagine that tC based all of its checks off of the UGNT. Here are the steps to add any language reference Bible as the Gateway Language for checking. Performing this on English ensures that the process works for other Gateway Languages.

1. Base checks off of UGNT using Greek/Strong's number occurrences.
2. Align the Gateway Language Reference Bible to the UGNT using new tC Alignment Tool.
3. Perform the checks, to validate the Gateway Language is ready to use as a reference Bible for that Tool.
4. Translate the Supplemental resources such as notes and articles for the checking tools.
5. Translate the User Interface Strings.
6. Package and Release as a Gateway Language Resource Package.