Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||KO: currencies were translated as language|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Priority:||P3||CC:||issues, pavel, petr.dudacek|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
Description jeongkyu.kim 2005-07-27 01:11:12 UTC
In language option dialog, each currency was translated as language. For example, 'KRW 한국어(대한민국)' should be 'KRW 대한민국 원(대한민국)'. Unfortunately, OO.o English version does not specify name of each currency. Due to the reason, it seems to be hard to get correct translation of each currency for now. The possible workaround is to take '어' out of currency name, such as 'KRW 한국 어(대한민국)' -> 'KRW 한국(대한민국)'.
Comment 1 jeongkyu.kim 2005-07-27 01:12:07 UTC
Created attachment 28242 [details] screenshot shows incorrect translation of currencies
Comment 2 jeongkyu.kim 2005-07-27 01:16:18 UTC
jeongkyu -> Ian, The screenshot will show you where you can find currency list. Also, it shows garbled text for some currencies. I wonder if it is caused by some problems of my system (Windows 2003, English). Would you check that on your system?
Comment 3 petr.dudacek 2005-07-27 10:44:55 UTC
Accept issue (change status to STARTED) target =2.0.1
Comment 4 petr.dudacek 2005-07-27 12:08:54 UTC
Hi Jeongkyu, I cannot find the occurence of 'KRW 한국어(대한민국)' all I could find was 한국 어(대한민국) which is a translation of the english "Korean (RoK)". Is this the string i need to change? Thanks, Ian details below: KeyId 368384 Language Korean PRJ svx Filename source\dialog\langtab.src Build SRC680 GID RID_SVXSTR_LANGUAGE_TABLE LID LANGUAGE_KOREAN Type pairedlist HelpId ShortCut 0 Status translated externally Editor Seen in source 2005-07-25 12:32:00.0 Changed 2005-01-28 16:40:00.0 PForm Export needed false Reflected in
Comment 5 pavel 2005-12-14 14:20:02 UTC
iano: it looks like that Korean people are very bad at issues handling and their issues are not fixed because of that :-( Move target to 2.0.2.
Comment 6 jeongkyu.kim 2005-12-15 02:39:49 UTC
Hi pjanik, Sorry for adding you to cc without permission. I just wanted to hear from you what is so bad for Korean people at issue handling. If you let me know that, I will try to improve it.
Comment 7 pavel 2005-12-15 05:27:16 UTC
jeongkyu: Hi. It was not meant as "people who speak Korean" but "people who handle Korean issues". The problem is that yesterday, I reassigned many issues where Iano asked someone who handles Korean issues and reassigned to him. The person then either commented or not commented in time. And after he commented/answered to iano, he forgot to reassign back to iano. Iano is not informed about the answer without reassigning back to him. The problem is the all issues had target 2.0.1. Right now we are in the RC phase of 2.0.1 and we want all issues to be cleared/fixed. Sorry, I should be more verbose when comenting before. No problem putting me in CC: to any issue. If I do not agree, I can remove myself afterwards :-) Thanks for supporting OOo!
Comment 8 jeongkyu.kim 2005-12-15 08:45:49 UTC
Hi pavel, > jeongkyu: Hi. It was not meant as "people who speak Korean" but "people who > handle Korean issues". I already understood it. :-) > The problem is that yesterday, I reassigned many issues where Iano asked someone > who handles Korean issues and reassigned to him. The person then either > commented or not commented in time. And after he commented/answered to iano, he > forgot to reassign back to iano. Iano is not informed about the answer without > reassigning back to him. I understand what you mean and I feel guilty about that. Actually, I already recognized this issue was assigned to me. However, my recent situation has not allowed me to organize my jobs for OOo. I moved back to my home country Korea from US after 4 years and got a new job here etc. And there were more important OOo issues that I needed to focus on. Thus I hope you to understand my bad handling of OOo issues. :-) And, I will arrange up those asap. Thanks for your concern and effort for OOo. Jeongkyu
Comment 9 pavel 2006-02-08 08:56:58 UTC
So what is the status of this issue? Shouldn't we retarget again?
Comment 10 jeongkyu.kim 2006-02-08 09:12:04 UTC
I belive that there is no progress on this issue for 2.0.2. Let me try to reset target milestone.