From: Pascal J. B. <pj...@in...> - 2011-04-11 02:35:38
|
Sam Steingold <sd...@gn...> writes: >> * Vladimir Tzankov <igmnaxbi@tznvy.pbz> [2011-04-08 16:42:45 +0300]: >> >> On 4/5/11, Sam Steingold <sd...@gn...> wrote: >>> it would be nice if you could investigate this. >>> (build with "./configure --with-debug --cbc build-g", run under gdb, >>> break in legal_namechar, and see why the char 160 is illegal when >>> *PATHNAME-ENCODING* is ISO-8859-1). >> >> legal_namebyte():825 is reached with ch == 160 and this is form config.h: >> #define VALID_FILENAME_CHAR ((ch >= 1) && (ch <= 127) && (ch != 47)) > > is this actually correct? only ascii pathnames on mac os x? oh well... Not at all. On MacOSX, the pathnames are encoded in UTF-8 with a certain normalization. http://developer.apple.com/library/mac/#qa/qa2001/qa1173.html -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. |