Bug 532392 - Wrong button name of gimp when save change
Summary: Wrong button name of gimp when save change
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora Localization
Classification: Fedora
Component: Chinese Simplified [zh_CN]
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Yijun Yuan
QA Contact: Yijun Yuan
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-02 02:59 UTC by Amos Kong
Modified: 2015-05-25 00:05 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2009-11-02 08:34:19 UTC


Attachments (Terms of Use)
screen snapshot png file (156.57 KB, image/png)
2009-11-02 03:00 UTC, Amos Kong
no flags Details

Description Amos Kong 2009-11-02 02:59:18 UTC
Description of problem:
I create a new file in gimp, when I directory close the main window,  a new dialog window display, the two button name are all "保存"

Save  --> '保存'
un-Save --> '不保存'

And the function of those two button seems fine.

Version-Release number of selected component (if applicable):
GIMP 2.6.7
Fedora 11



How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Amos Kong 2009-11-02 03:00:59 UTC
Created attachment 367061 [details]
screen snapshot png file

This is the screen snapshot file.

Comment 2 He Rui 2009-11-02 06:42:11 UTC
The same issue also happened in f12-20091028 live image.

Comment 4 Yijun Yuan 2009-11-02 08:36:51 UTC
I get to know this through i18n-zh mailing list
http://groups.google.com/group/i18n-zh

if you are interested please join the i18n-zh team. BTW fedora contributors meet at #fedora-zh of freenode, too.

Comment 5 Amos Kong 2009-11-03 03:09:06 UTC
(In reply to comment #4)
> I get to know this through i18n-zh mailing list
> http://groups.google.com/group/i18n-zh

Have joined in, my gmail account (kongjianjun@gmail.com)
 
> if you are interested please join the i18n-zh team. BTW fedora contributors
> meet at #fedora-zh of freenode, too.  

Thanks.


Note You need to log in before you can comment on or make changes to this bug.