[Korean grammar] -느니만큼 Expressing Causes and Reasons

Also Read

가: 여러분, 드디어 우리 회사가 신도시 개발 프로젝트를 따냈습니다.
Everyone, our company has finally landed the contract for the new city development project.
나: 사장님, 정말 잘됐어요. 큰돈이 걸린 일이니만큼 경쟁이 아주 치열했잖아요.
That’s truly wonderful news. It was a really fierce competition to the extent that a large amount of money was involved, right?
가: 그렇지요. 모두 그동안 열심히 해 준 여러분 덕분입 니다.
Right. It’s all thanks to the hard work everyone put into the effort.
나: 계약을 어렵게 따냈으니만큼 저희도 더 열심히 뛰겠 습니다.
To the extent that it was difficult to land the contract, we’ll all work even harder to make our work stand out.


This expression is used to indicate that the preceding clause forms the reason or basis for the following clause.

• 손님들이 돈을 많이 내고 먹느니만큼 서비스에 좀 더 신경을 쓰는 게 좋겠어요.
To the extent that customers spend a lot of money on their food, we should pay more attention to the service.

• 출산일이 얼마 남지 않았으니만큼 준비할 게 많겠어요.
You must have a lot to prepare as there isn’t much time left until the due date.

• 회사의 중요한 행사니만큼 직원들 모두 적극 참여해 주십시오.
To the extent that it is an important company event, I request that all employees actively participate.

1. This expression can be replaced with 만큼 with no major change in meaning.
• 손님들이 돈을 많이 내고 먹는 만큼 서비스에 좀 더 신경을 쓰는 게 좋겠어요.
• 출산일이 얼마 남지 않은 만큼 준비할 게 많겠어요.

2. This expression is sometimes used while repeating the immediately preceding noun. In such cases, the repetition serves to emphasize the noun’s meaning within that particular context.
가: 친구와 동남아에 가려고 하는데 여름옷을 사려면 어디로 가야 할까요?
나: 지금 겨울이잖아요. 계절이 계절이니만큼 여름옷을 구하기가 쉽지는 않을 거예요.

가: 영업 일을 하시니까 사람들을 많이 만나시겠네요.
나: 네, 직업이 직업이니만큼 사람들을 많이 만나게 돼요.

While similar to -(으)니까 with respect to expressing a reason, the expression -느니만큼 differs in its consideration of the degree of the situation in the preceding clause when expressing the action or state of affairs in the following clause.



>> You can click on the title of each grammar below to see other grammars which also express 'Causes and Reasons'


Share this

Author:

안녕하세요? 즐거운 하루를 보내세요!ㅎㅎ

0 comments: