See in Reader
fixed #21 made image links https
This commit is contained in:
Joel Lonbeck
parent
2697f6e2b4
commit
26bb310e65
14
REVIEWME.md
14
REVIEWME.md
|
|
@ -20,15 +20,15 @@ unknown tA module 'gl' in link: https://git.door43.org/Door43/en-ta-gl/src/maste
|
|||
`/figs-exclusive` has image links.
|
||||
Are we going to move tA images into their own Resource Container?
|
||||
```
|
||||
skipped link: http://cdn.door43.org/ta/jpg/vocabulary/we_us_inclusive.jpg
|
||||
skipped link: http://cdn.door43.org/ta/jpg/vocabulary/we_us_exclusive.jpg
|
||||
skipped link: https://cdn.door43.org/ta/jpg/vocabulary/we_us_inclusive.jpg
|
||||
skipped link: https://cdn.door43.org/ta/jpg/vocabulary/we_us_exclusive.jpg
|
||||
```
|
||||
|
||||
`/figs-inclusive` has image links.
|
||||
Are we going to move tA images into their own Resource Container?
|
||||
```
|
||||
skipped link: http://cdn.door43.org/ta/jpg/vocabulary/we_us_inclusive.jpg
|
||||
skipped link: http://cdn.door43.org/ta/jpg/vocabulary/we_us_exclusive.jpg
|
||||
skipped link: https://cdn.door43.org/ta/jpg/vocabulary/we_us_inclusive.jpg
|
||||
skipped link: https://cdn.door43.org/ta/jpg/vocabulary/we_us_exclusive.jpg
|
||||
```
|
||||
|
||||
`/guidelines-sonofgodprinciples` has link to tW pdf download.
|
||||
|
|
@ -44,19 +44,19 @@ skipped link: https://unfoldingword.org/en/?resource=translation-words
|
|||
`/translate-original` has link to image.
|
||||
Are we going to move tA images into their own Resource Container?
|
||||
```
|
||||
skipped link: http://cdn.door43.org/ta/jpg/ol2sl2sl2tl_small_600-174.png
|
||||
skipped link: https://cdn.door43.org/ta/jpg/ol2sl2sl2tl_small_600-174.png
|
||||
```
|
||||
|
||||
`/translate-process` has link to image.
|
||||
Are we going to move tA images into their own Resource Container?
|
||||
```
|
||||
skipped link: http://cdn.door43.org/ta/jpg/translation_process.png
|
||||
skipped link: https://cdn.door43.org/ta/jpg/translation_process.png
|
||||
```
|
||||
|
||||
`/translate-source-version` has link to image.
|
||||
Are we going to move tA images into their own Resource Container?
|
||||
```
|
||||
skipped link: http://cdn.door43.org/ta/jpg/versioning.jpg
|
||||
skipped link: https://cdn.door43.org/ta/jpg/versioning.jpg
|
||||
```
|
||||
|
||||
`/writing-apocalypticwriting` has link to tW pdf download.
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@ Some languages have more than one form of "we:" an **inclusive** form that means
|
|||
|
||||
See the pictures. The people on the right are the people that the speaker is talking to. The yellow highlight shows who the inclusive "we" and the exclusive "we" refer to.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Reason this is a translation issue
|
||||
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@ Some languages have more than one form of "we": an **inclusive** form that means
|
|||
|
||||
See the pictures. The people on the right are the people that the speaker is talking to. The yellow highlight shows who the inclusive "we" and the exclusive "we" refer to.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**Reason this is a translation issue** - The Bible was first written in the Hebrew, Aramaic, and Greek languages. Like English, these languages do not have separate exclusive and inclusive forms for "we." Translators whose language has separate exclusive and inclusive forms of "we" will need to understand what the speaker meant so they can decide which form of "we" to use.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,6 @@ If the translator does not understand the original language, he will have to use
|
|||
|
||||
Consider the example below. A translator uses a Swahili New Testament as the source for a new target language translation. However, the particular Swahili Bible version he is using was actually translated from English — not directly from the Greek (the original language of the NT). So it is possible that some of the meaning has changed in the chain of translation from the original to the target languages.
|
||||
|
||||
|
||||
|
||||
|
||||
The only way to make sure the translation is as accurate as possible is to compare the new translation with the original languages. Where this is not possible, use the ULB as the source text, along with other Bible translations that were translated from the original languages.
|
||||
|
|
@ -6,4 +6,4 @@ There are two things to do in translation:
|
|||
1. Discover the meaning in the source language text (See: [Discover the Meaning of the Text](en/ta/translate/man/translate-discover))
|
||||
1. Re-tell the meaning in the target language translation (See: [Re-telling the Meaning](en/ta/translate/man/translate-retell))
|
||||
Instructions for translation sometimes divide these two things into smaller steps. The graphic below shows how these two fit into the translation process.
|
||||
|
||||
|
||||
|
|
@ -9,7 +9,7 @@ Before starting a translation project, please ensure that you have the latest ve
|
|||
|
||||
Version numbers are only given when a work is released, not when they are edited. Revision history is kept in Door43, but this is different than a work being given a version number.
|
||||
|
||||
|
||||
|
||||
|
||||
Each source text is given a whole number for each release (version 1, 2, 3, etc). Any translations based on that source text will take the version number of the source text and add .1 (a translation from English OBS version 4 would become version 4.1). Any further translation based on the intermediate translation would add another .1 to the version number it was created from (for example 4.1.1). New releases of any of these texts increment their "decimal place" by 1.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue