Re: UTF-8 sequences in filenames

["Dmitry G. Mastrukov" <dmitry taurussoft org>]

В Срд, 05.03.2003, в 10:29, Dmitry G. Mastrukov написал:
> Hi!
> 
> I'd like to raise problem we (in Russian community) encountered with
> filenames.
> The problem exists in non-unicode locales (ru_RU.KOI8-R, ru_RU.CP1251)
> with mamy GNOME apps (gedit, glade, nautilus at least). Files with
> national filenames are viwed through file selector (G_BROKEN_FILENAMES
> is set) and can be opened. But newly created files looks on filesystem
> (in mc for example) as UTF-8 sequences.
> We have some preliminary patches to gnome-vfs but we have no confidence
> in that gnome-vfs is only source of problem. It should be good to find
> out thougths of gnome-vfs developers about that.
> We see two possibilities:
> 1. Gnome-vfs is broken and need patching. Seems it is not using
> g_filename_from_utf8/uri() functions from glib at all. Then where is
> control point for possible conversion? In other words which public
> functions work with "locale-dependant" filenames and which work with UTF
> definitely? Brief look at gedit sources shows
> gnome_vfs_get_local_path_from_uri is used to get filename to feed to
> fopen(). So it should produces locale filename on output. Also may be
> do_action() functions in method/file-method.c and some other methods
> should use g_filename_fron_utf8/uri().
More deep tests show that Nautius, grecord, gThumb with
G_BROKEN_FILENAMES=1 work fine, recodin to locale occurs. Seems
gnome-vfs is mostly OK, but gedit and glade put UTF8 sequences in
filenames in any case.

Regards,
Dmitry