On Thu, 9 Mar 2006 01:40:36 +0100 Atman Sense <mattenklicker@xxxxxxx> wrote: > > > Drag and Drop from/to folders with spaces does not work, also > > > file-type associated actions. > > Oh, yes, not spaces, but unusual characters like umlauts are the > problem. A click on copy-button works, drag&drop doesn't. Self-defined > filetype-actions also. > > Cannot create file /tmp/test test mit ö und ü/asdfa - Die > Argumentliste ist zu lang > > ran with env -i, a change to a umlaut-folder is impossible: > The directory '/tmp/test 3 mit ü/' does not exist! These are most likely a problem with filesystem encoding. emelFM2 converts item names from and to localised encoding as needed, _except_ if it decides that such conversion is not necessary. Such decision is based on $G_FILENAME_ENCODING, $G_BROKEN_FILENAMES, the default encoding for the user's locale, and whether $LANGUAGE or $LANG is some flavour of english. To quote from the INSTALL document: NOTE: If your filesysten encodes path/file names in something other than utf-8/ascii (e.g. with german umlauts), you should also have: 1. set the environment variable G_FILENAME_ENCODING=character set name (or a comma-separated list of such names, and glib uses the first name in that list). OR 2. set the environment variable G_BROKEN_FILENAMES=1. In that case, glib assumes that the locale encoding is used for names. G_FILENAME_ENCODING takes priority over G_BROKEN_FILENAMES. (The above are glib requirements, not emelfm2 requirements per se.) Regards Tom -- Users can unsubscribe from the list by sending email to emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by logging into the web interface.