Re: [BUG] with non-ascii characters in dir names

Jan Vroonhof writes: Jan> Judging from some grepping through the source. The data should probably Jan> be converted into file-name-coding-system, using Jan> GET_C_STRING_FILENAME_DATA_ALLOCA (defined in buffer.h [1]) You're right, this corrects the bug. This brings me a question that might be stupid, but isn't it likely that most use of XSTRING_DATA through the code will be bogus in the same fashion[1]? And what about if we don't know about the coding system ? I mean take the same function, unix_create_process, where the environement is massively copied for the child to be forked. What should we do about it ? Footnotes: [1] Like, isn't it an artefact of non mule-ized stuff ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19