Takao-san, Thanks for your explanation, you are certainly better experienced in this area than I am, if you feel that this is the correct way for Solaris then I will defer to you.
I'm quite surprised to find that Fedora 8 has this when Alex works for RedHat, but what do I know ;) Thanks, Darren. Takao Fujiwara - Tokyo S/W Center wrote: > > Darren Kenny wrote: >> Takao-san, >> >> How does this effect the behaviour? > > It makes the filename with the current encoding. > My understanding is Fedora 8 also has the same setting. > >> As I understood it - regardless of locale in GNOME - filename were encoded in >> the UTF-8 locale - at least this is what Alex Larsson (of GNOME VFS fame) >> said. >> >> If that is correct, how does this change alter that? > > I'm not sure which description you indicate however I guess it explains the > internal encoding instead of the input/output encodings. > > I recognize this kind of topics are introduced in ARC but I was not sure if I > should comment it. > The main problem is the users write the filenames with the current encoding, > e.g. mkdir foo-multibytes, then if applications output UTF-8 only, the file > path includes multi encoded file paths, it causes SEGV in many applications. > Then our basical policy is to output the filenames with the current encodings > especially for local path "file:///" so that applications work fine. > > We also defines G_BROKEN_FILENAMES for none UTF-8 filenames. > Currently none UTF-8 locales are supported so we need to avoid critical > problems likes crashes. > > All I can say is the saved encoding should be UTF-8 likes .desktop, .scheme > files. > > Does it make sense? > > I'ld also like to see if we have actual problems in case we put > filename_encoding=locale. > > Thanks, > fujiwara > >> Thanks, >> >> Darren. >> >> Takao Fujiwara - Tokyo S/W Center wrote: >> >>> I'ld like to change the default parameter to work on none UTF-8 locales. >>> >> > >
