Closed
Bug 483771
Opened 16 years ago
Closed 16 years ago
Korean name for "History" menu item is misleading
Categories
(Mozilla Localizations :: ko / Korean, defect)
Mozilla Localizations
ko / Korean
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gaemon, Assigned: channy)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ko; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ko; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7
in Korean version of firefox, "History" top menu item is translated as "Ba-ro-ga-gi (바로 가기)". problem is, "바로 가기" is also the translation of "MS Windows Shortcut" in Korean version of Windows.
even though I'm a Ubuntu user and rarely use Windows, it always bugs me and sometimes I mistake that menu as the Bookmarks menu. besides, "바로 가기" is actually closer in meaning to "Shortcut" in Korean and has nothing to do with "History".
I suggest this item is translated as "발자국 (means footprint)" or "발자취" or somesuch. Korean version of IE calls this item as "열어본 페이지 목록 (list of pages opened so far)", but of course this is too long to be a menu item.
Reproducible: Always
Steps to Reproduce:
N/A.
Actual Results:
N/A
Updated•16 years ago
|
Assignee: nobody → channy
Component: Menus → ko / Korean
Product: Firefox → Mozilla Localizations
QA Contact: menus → admin
| Assignee | ||
Comment 1•16 years ago
|
||
Thanks for comments.
"바로 가기" is not meaning only "shortcut" but also "go directly". As you know "History" menu has URLs for back/forward and histories to go directly. It was chosen in early stage in Mozilla 1.0 "Go" menu so it's hard to be changed because of many users are good at even though someone suggested me to change to "이동".
Actually "History" must be translated into "방문 기록" rather than "발자취", but it was already here in Firefox. You can see them sidebar or History menu too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•