Issue 107959

Created attachment 66860 [details]
[KO] Writer : F4 > Database list > The connection to the data source

@jihui_choi
Please check and correct for all your reports
- select a correct Version for your reports, "Current" is completely useless 
- Please contribute a description of the problem in English with only Menu 
  text translations in KO. Also without KO language knowledge it should be   
  possible to find out for what menu item (or similar) the problem exists, so 
  that we can check whether also other languages are affected

@rainerbielefeld //
1. select a correct Version for your reports, "Current" is completely useless
>> If "current" is completely useless, why it is on the list? Moreover "current" is the default value. So the 
default value of the list is totally useless? I can't understand.
"Current" doesn't mean any specific version. If you knew which version has the problem, you could select the 
version, but if you didn't know, you couldn't. I think "current" is for that situation and I'm not sure whether 
those problems are already fixed or not.
Anyway I've checked those problems in 3.1.1 and 3.2.0 rc1 and I'll change version of all my reports as soon as 
possible.


2.Please contribute a description of the problem in English with only Menu 
  text translations in KO. Also without KO language knowledge it should be   
  possible to find out for what menu item (or similar) the problem exists, so 
  that we can check whether also other languages are affected
>> Now I'm trying to make a process for reporting some wrong translation using Issue tracker. It is not only 
for me, but also for all members of korean translation team. There are some points.
 i) Many people don't like to use English and aren't familiar. If I say, "if you want to report something, you 
should use English.", no one will report. I'm sure about this.
 ii) Someone who wants to fix problems of translation must know the language. How can you fix the problem if 
you don't know Korean? How do you know the new word is correct or not? This is the big problem. And if you can 
speak Korean, I don't need to report in English.
 iii) Most of my reports are assigned to myself. It means I'll fix the problems. Or someone who can speak 
Korean and have a permission to access in Pootle will. At this moment only few people who I know have the right 
and all of them can speak Korean.
 iv) Last I'm a newbie in Issue tracker, so there might be some mistakes. I apologize about them.
 v) I'll be trying to make my report simple and readable for everyone(include non-korean speakers.) something 
like this.
 - title of the issue(in English) : [KO] Writer : F4 > Database list > The connection to the data source
 - application : 라이터
 - position : F4 > 데이터베이스 목록 : 데이터베이스의 테이블 목록을 볼 때 오류 메세지
 - original text : The connection to the data source..
 - current translation : &quote;&quote;파일이 없습니다.
 - suggestion : none.
 - explanation : 인용 부호 사용 중에 문제가 생긴 것 같네요.

If you have some other suggestions or advices, please let me know. Thank you.

@jihui_choi
"Current" is in the list because there are issues that are not connected to a
particular version ("www", ...). You should use the oldest version in what you
find the problem.

Or course it is most likely that your reported issues only affect Korean
translation, but I often find issues where the situation is some more
sophisticated, and that can be found out better if some more explication like
complete menu tree and explication of the wrong used words (like "ऒणकेशध" means
"dogfish", required is "ऒणकेशस" for "continue search"'. 

@rainerbielefeld //
> "Current" is in the list because there are issues that are not connected to a
particular version ("www", ...).
>
Ok. Now I understand.

I don't know which way is better. I want to try to use several ways.
Thank you for your kindness.

Reset assigne to the default "issues@openoffice.apache.org".