-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
None
-
Affects Version/s: None
-
Component/s: None
Hi,
Congratulations on opening Atlassian in Korea.
Also, thank Atlassian for translating in Korean.
I have little concern about these recent change in Korean Translation by Jason Ryu [Atlassian].
How can I have a conversation with him regarding Korean translation?
His translation is fine but we've been using JIRA for years, and he brought up new terms which is just simple pronunciation of English words in Korean.
I agree that most of Korean people who use JIRA are highly skilled, however as Korean we all have precious liability to keep our language clean from fancy imported words.
First, I suggest create Guideline for Korean.
(Actually I did that years ago in TRANS-600)
Secondly, we need to create a way to be unified and simplified.
Please, do not translate "OPEN" as just "오픈" which is just pronunciation of its word.
As well as, "ADD-ON" as "애드온"
These are NOT translation. We have such a good words for "Open" and "Add-on" just like "열린", "추가 기능".
Thirdly, I agree that some wording is not available in Korean.
For example, "Issue" includes all kinds of problem or incident however In Korean we have several distiguished words like "Problems", "Incident", "Accident"... None of Korean just describe "Issue" just like JIRA.
So in this case, let's keep "Issue" as "이슈"
I really would like to have conversation with Jason Ryu before it is too late.
We need to work together and please don't ignore what we've been facing here for years.
Facing new translation is quite annoying for everyone.
Thank you.
CJ Lee