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

[Korean] Korean document have weird expressions like '_제네릭_' #167

Closed
KunHwanAhn opened this issue Sep 15, 2022 · 2 comments · Fixed by #171
Closed

[Korean] Korean document have weird expressions like '_제네릭_' #167

KunHwanAhn opened this issue Sep 15, 2022 · 2 comments · Fixed by #171

Comments

@KunHwanAhn
Copy link
Contributor

It looks like that intended expression as Italic, 제네릭.

In Korean, most of words are composited with postposition(e.g. ~는, ~을). I think it is not correct translation.

In Markdown, in order to express words with italic, we can choose one between *Italic* and _italic_.

What do you think about using *itailc* instead of _italic_. Or we can give some whitespace between word and postposition

Please give any feedback to me. 🙏


한글 문서를 보다보면 _제네릭_과 같이 적혀있는 문서가 좀 있는 것 같은데, 이게 우리나라 조사(예> ~는, ~을)와 붙으면 마크다운에서 이탤릭 표현으로 인식을 못하고 그냥 하나의 단어로 취급해서 이탤릭체가 적용이 안되는 것 같아보이는데요.

마크다운에서 이탤릭체를 쓸 때, *이탤릭*, _이탤릭_, 이 2가지를 모두 허용하고 있는데, 이탤릭체 표현하는 곳을 *이탤릭*으로 바꾸는 것은 어떨까요? 아니면 단어와 조사 사이에 빈공백 하나 주는 방향도 괜찮을 것 같습니다.

피드백 부탁드립니다! 🙏

@KunHwanAhn
Copy link
Contributor Author

KunHwanAhn commented Sep 15, 2022

Following is one the examples.

In markdown code

`T<U>` 구문에 대한 내용은 _제네릭_을 다룰 때 좀 더 알아보겠습니다.

Rendered Doc

스크린샷 2022-09-15 21 31 11

@bumkeyy
Copy link
Contributor

bumkeyy commented Sep 15, 2022

@KunHwanAhn

안녕하세요.
_ 보다는 *를 사용하는게 더 괜찮은 것 같네요.

이미 적용되어 있는 부분도 많을 것 같아서, 조금씩 수정하면 좋을 것 같습니다 👍

의견 감사합니다!

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.

2 participants