Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update the reasons for each case #38

Closed
Tracked by #15
eubinecto opened this issue Mar 24, 2022 · 1 comment · Fixed by #39
Closed
Tracked by #15

update the reasons for each case #38

eubinecto opened this issue Mar 24, 2022 · 1 comment · Fixed by #39

Comments

@eubinecto
Copy link
Owner

eubinecto commented Mar 24, 2022

What?

Update the reasons with this:

friends and junior:
  Comfortable and informal:
    politeness: 1
    reason: A comfortable and informal situation is a very relaxed situation for all, so friends and juniors will use the intimate style (banmal). 
  formal:
    politeness: 2
    reason: If there are observers around or the situation is more formal, then the speaker is not completely relaxed. Therefore, it is most appropriate to use the formal (-yo) form. 
boss at work:
  Comfortable and informal:
    politeness: 2
    reason: In a less formal situation, for example a company dinner, employees feel a little more relaxed around their bosses, and thus they may use the formal (-yo) form. 
  formal:
    politeness: 3
    reason: In a highly formal environment, e.g. an important meeting, employees will always use the honorific (-bnida) form. This shows the appropriate respect in a high-profile context. 
adult family:
  Comfortable and informal:
    politeness: 1
    reason: With in a relaxed setting, using the intimate style (banmal) is standard, even if a family member is older than you. 
  formal:
    politeness: 2
    reason: If someone outside of the family, e.g. a neighbour, is part of the conversation too, then it is common to use the formal (-yo)¬ form towards family members to seem polite in front of others. 
@eubinecto eubinecto mentioned this issue Mar 24, 2022
53 tasks
@eubinecto
Copy link
Owner Author

Refining the sentences

I've revised the rules to make it sound more natural and clear:

# https://docs.google.com/document/d/13ZiGYDxqpWb93JALVOLSNLo0lHO73TYjKmEKOlCpc4w/edit
friends and junior:
  comfortable & informal:
    politeness: 1
    reason: A comfortable and informal situation is a very relaxed situation for all, so you may speak to your friends and juniors without honorifics (`-어`).
  formal:
    politeness: 2
    reason: If there are observers around or the situation is rather formal, then you and your listener may not find it completely relaxing. If so, you should speak with polite honorifics (`-어요`) even when you are speaking to your friends and juniors.
boss at work:
  comfortable & informal:
    politeness: 2
    reason: If you are in an informal situation with your boss, e.g. a company dinner, then you and your boss may find it a little more relaxing than at the work place. Therefore, it is not necessary to speak with formal honorifics, and you may speak to your boss with polite honorifics (`-어요`).
  formal:
    politeness: 3
    reason: If you are in a highly formal environment, e.g. an important meeting, you should always speak with formal honorifics (`-습니다`). This shows the appropriate respect to your listeners in a high-profile context.
adult family:
  comfortable & informal:
    politeness: 1
    reason: If you are in a relaxed setting, it is customary and allowed to speak to your family members without honorifics (`-어`) even when they are older than you.
  formal:
    politeness: 2
    reason: If someone outside of your family, e.g. a neighbour, is partaking the conversation too, then it is customary to speak to your family with polite honorifics (`-어요`) so that you and your family come acorss polite to the outsiders.

eubinecto added a commit that referenced this issue Mar 24, 2022
[#38] the reasons for the rules are refined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant