주어 상승/비상승 구문의 한/영 통ㆍ번역Korean-to-English Interpreting and Translation of Subject Raising and Non-Subject Raising Constructions
- Other Titles
- Korean-to-English Interpreting and Translation of Subject Raising and Non-Subject Raising Constructions
- Authors
- 이광호
- Issue Date
- 2014
- Publisher
- 한국통번역교육학회
- Keywords
- context; sentence structure; translation; non-raising; meaning; subject raising; interpreting; 맥락; 문장 구조; 번역; 비상승; 의미; 주어 상승; 통역
- Citation
- 통번역교육연구, v.12, no.1, pp 91 - 107
- Pages
- 17
- Indexed
- KCI
- Journal Title
- 통번역교육연구
- Volume
- 12
- Number
- 1
- Start Page
- 91
- End Page
- 107
- URI
- https://scholarworks.gnu.ac.kr/handle/sw.gnu/19831
- DOI
- 10.23903/kaited.2014.12.1.005
- ISSN
- 1738-1223
2671-972X
- Abstract
- In this paper I focused on the problems arising due to syntactic differences of subject raising and non-subject raising constructions of English and Korean. In English a predicate such as seem and likely is a subject raising predicate. In Korean a predicate such as (kes) kat-ta is a subject raising predicate. In English subject and non-subject raising constructions appear to have different sentence structures, but in Korean it appears that there is no difference between the two types of constructions. The English subject and non-subject raising constructions have different implications and usages and so they are used in different contexts or situations. If they are misused in inappropriate contexts, they would sound wrong. The same is true of Korean subject and non-subject raising constructions. However, as Korean subject and non-subject raising constructions appear to have the same kind of structure, interpreters and translators may experience trouble when interpreting and translating the constructions into English. In this paper I discussed this problem in detail and suggested a way to overcome the problem.
- Files in This Item
- There are no files associated with this item.
- Appears in
Collections - 인문대학 > 영어영문학부 > Journal Articles

Items in ScholarWorks are protected by copyright, with all rights reserved, unless otherwise indicated.