|
From: Daniel R. <no...@me...> - 2002-11-14 12:33:34
|
lör 2002-11-09 klockan 18.41 skrev Tobias Rundström: > On fre, nov 08, 2002 at 04:09:21 +0100, Daniel Resare wrote: > > 1) Do nothing. This is the FTP way, and non-ascii paths will not work reliably > > Nah. > > > 2) Do all charset conversion on the client and announce the charset that the > > server perhaps in the response of the hello command. If opt for this method, > > it would be a good idea to say that the encoding of the server must be > > ascii-compatible, so that communicating with the server in pure ascii will > > always work. > > This is much harder then UTF-8 IMHO. > > > 3) Mandate UTF-8. No charset info would need to be exchanged at on session > > setup. > > Yes this is the best way in my point of view. It might be some work done in > the server to get this to work smooth, but then we don't need to answer 1000 > support questions about incorrect charsets and such. > > GLib contains good functions for utf-8 convertion. We should take a better > look at them and see how much we can get for "free". > What you're looking for is g_filename_to_utf8() http://developer.gnome.org/doc/API/2.0/glib/glib-Character-Set-Conversion.html#g-filename-to-utf8 /noa |