This is a noble goal. For those passages that are clearly intended to apply to men and women alike, we want the text somehow to reflect that. No one should feel like an afterthought in God's plan. But this approach to translation is not without its difficulties:
- Many gender-neutral translations change passages that really should be left in the masculine. For example, being a "son of God" is not exactly equivalent to being a "child of God." Not that sons are better than daughters, but that there were certain unique aspects to the sonship relationship in the culture of the author that get lost in these translations - the idea of inheritance, responsibility, carrying on the family name, and so on. Those ideas are part of the imagery of the phrase, but we lose it when the translation only focuses on the more generic child relationship.
- In order to make a passage gender-neutral, often times the translator has to resort to an awkward phrase (for example, using "sons and daughters" every time "sons" occurs). The extra wording can clutter up a sentence easily. Using the masculine, with an inclusive meaning, reads more smoothly.
- Or, the translator will use a plural ("they," "them," "theirs") instead of the singular in order to neuter the sentence. This effectively takes gender out of it, but then you've changed the nuance of a phrase, losing the personal touch of an individual relationship with God, and sometimes sounding grammatically incorrect.
The noble goal has plenty of landmines. An attempt to clarify the meaning of a passage can actually skew the meaning of the passage, which by definition would be a poor translation.
For more information about the new NIV and the translation choices they made, see the following websites: http://www.cbmw.org/Blog/Posts/CBMW-Responds-to-New-NIV2011 and http://galvestondailynews.com/ap/bee3b4/.
The NET (http://net.bible.org) does a very reasonable job of indicating when a passage is meant to be gender-inclusive. They make pretty good choices of when to retain the masculine wording, and every time they choose a more gender-inclusive phrase than the original language, they make a clear note of it. So, you always know what the original said, plus you get a good indication of which verses are meant to transcend gender.
The interesting point for me in this is the translation principle - if the text says "men," but the text means "men and women," what's the best way to translate it? If it says "men" and means "men," then the answer is simple (but some translations still change it!). But should a translation mirror the verbal text or the meaning of the text? The answer is that both can be good choices, as long as the reader knows what you've done. The translator should either leave the text alone and let the readers and commentators decide, or they should change the text with a clear note of what the original says. That's why I like the NET - they do this well. Only when it's obvious to be inclusive should the translator even consider a more inclusive phrase. When in doubt, the translation should leave the text as is.
Translating the Bible is filled with difficult choices. With the hub-bub around the new NIV, I don't want to immediately criticize it just because some gender-loaded terms got translated in an inclusive way. That can be a valid translation. However, as the CBMW article above notes, there are enough of unnecessary changes in the new NIV, changes that skew the meaning, to be a very strong concern. (Furthermore, there are enough difficulties with the current NIV that I choose not to use it, and especially not for teaching.)
We should all know that the original languages used the masculine for a convenient and clear style, not to exclude women from God's grace. A good friend of ours, Dr. Fred Sanders, made the recent observation that it's not just the women who have to tolerate being called "sons of God" - we men have to tolerate being called the "bride of Christ"!
No comments:
Post a Comment