Bug 70228 - G_BROKEN_FILES=1?
Summary: G_BROKEN_FILES=1?
Status: CLOSED DUPLICATE of bug 70686
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: glib
Version: beta4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Jay Turner
Depends On:
Blocks: 67218
TreeView+ depends on / blocked
Reported: 2002-07-31 05:45 UTC by David Joo
Modified: 2015-01-07 23:58 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2002-08-14 01:21:48 UTC

Attachments (Terms of Use)
set G_BROKEN_FILENAMES for CJK locales (872 bytes, patch)
2002-08-14 01:18 UTC, Paul Gampe
no flags Details | Diff

Description David Joo 2002-07-31 05:45:04 UTC
Description of Problem:
Because CJK is not going to use UTF-8, there is problem showing file names and
directories in native languages.

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

How Reproducible:

Steps to Reproduce:
1. creat a file in terminals (using native languages)
2. try to open it using gedit

Actual Results:
The filename or directory name is not shown

Expected Results:

Additional Information:
G_BROKEN_LANGUAGES=1 should be exported as default

Comment 1 Owen Taylor 2002-08-02 15:50:50 UTC
(Making public)

Comment 2 Owen Taylor 2002-08-13 23:20:22 UTC
*** Bug 69767 has been marked as a duplicate of this bug. ***

Comment 3 Paul Gampe 2002-08-14 01:18:16 UTC
Created attachment 70444 [details]
set G_BROKEN_FILENAMES for CJK locales

Comment 4 Paul Gampe 2002-08-14 01:21:43 UTC
The attached patch sets G_BROKEN_FILENAMES for the CJK locales.  I have  
confirmed that filenames created in native encoding via touch in 
gnome-terminal and gedit via file->save, are inter-operable and can be 
displayed via nautilus correctly.

Comment 5 Owen Taylor 2002-08-14 02:45:27 UTC
Havoc fixed this by installing  profile.d file that sets G_BROKEN_FILENAMES
(for all locales, doesn't matter for UTF-8 locales) from GLib ...
see bug #70686.

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

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