Bug 69767

Summary: Gedit can't save with Korean filename &....
Product: [Retired] Red Hat Linux Beta Reporter: David Joo <djoo>
Component: geditAssignee: Owen Taylor <otaylor>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: beta3CC: eng-asia-list
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-08-14 06:51:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67217    

Description David Joo 2002-07-25 05:48:01 UTC
Description of Problem:
Gedit can't save a file with Korean filename.
Nor can't open files that has been created with touch and vi on gnome-terminal
(actually, it won't even show in "Open") And if you run gedit from terminal you
will be able to see an error message saying (Invalid Utf-8) with all other
strange chars.

Version-Release number of selected component (if applicable):


How Reproducible:
Always!

Steps to Reproduce:
1. Open a gnome-terminal
2. gedit &
3. type Korean (using Ami and shift+space)
4. try to save it with Korean filename (gksrmf-> in korean it will be "korean")

Actual Results:
The program will hang

Expected Results:
Saves it with Korean name and should be able to be seen on gnome-terminal with "ls"

Additional Information:
for not showing Korean directories and files that has been created with "touch",
"vi" and "mkdir" can be seen by;
#export G_BROKEN_FILENAMES=1

Comment 1 Owen Taylor 2002-08-13 23:20:27 UTC

*** This bug has been marked as a duplicate of 70228 ***

Comment 2 Owen Taylor 2002-08-13 23:22:29 UTC
(actually, I'm not *entirely* sure this is a duplicate; part of it
is, but it may not all be duplicate. Unfortunately, even with
G_BROKEN_FILENAMES set, gtkfilesel doesn't work very well with
non-UTF-8 fileanmes, and there is no way that is going be able
to be fixed in just a few days.)

Comment 3 Owen Taylor 2002-08-14 06:51:07 UTC
Reopening, after reproducing with G_BROKEN_FILENAMES set

Comment 4 Owen Taylor 2002-08-15 19:43:08 UTC
This was fixed in gedit-2.0.2.