drakepc
/
fr_tm
forked from WA_Training/fr_tm
1
0
Fork 0
Files Issues Pull Requests Releases Wiki Activity See in Reader

Update 'translate/tA Decisions.md'

This commit is contained in:
Susan Quigley 2018-10-04 14:48:34 +00:00
parent e4c888ca7f
commit f067784ef4
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
translate/tA Decisions.md
View File

@ -5,8 +5,12 @@ Oct 1, 2018, we started going through tA to sure that all the verses that are s
Oct 4, 2018, we realized that if translators compare the ULB text in tA with the ULB text in en_ULB, they might find it confusing if the capitalization and punctuation are different. So moving on with our work, we'll make sure that the punctuation and capitalizaton are the same.
Questions:
If the examples in en_ta need to be from the ULB, which style would be more helpful for the translators?
Do the examples in en_ta need to be from the ULB? Could we have a note at the beginning saying that the examples are from previous or current versions of the ULB? Perhaps we could remove "(ULB)" after the verse reference.
Even if we do not need to make the examples the same as the ULB, it would still be good to check the verse references since there are errors there.
1. If the examples in en_ta need to be from the ULB, which style would be more helpful for the translators?
1. Do the examples in en_ta need to be from the ULB? Could we have a note at the beginning saying that the examples are from previous or current versions of the ULB? Perhaps we could remove "(ULB)" after the verse reference.
Comments
1. If all of these materials are intended to be dynamic, it seems it will be impossible to guarantee that all the examples in en_ta perfectly match the current ULB -- unless we do this task every time we make a new version available.
1. Even if we do not need to make the examples the same as the ULB, it would still be good to check the verse references since there are errors there.