Here is some additional info from sanitizer.log:

  Part (pos="3729"):
    SanitizeFile (filename="$B#G#M;n83<j=g=qO;2A%/%m%a!<%H(B.xls, =?ISO-2022-JP?B?GyRCI0cjTTtuODM8aj1nPXFPOzJBJS8lbSVhITwlSBsoQi54bHM=?=", mimetype="application/"):
      Match (names="$B#G#M;n83<j=g=qO;2A%/%m%a!<%H(B.xls", rule="1"):
        Enforced policy: accept

      Replaced file name with: __B#G#M;n83_j=g=qO;2A%_%m%a!_%H_(B.xls

  Total modifications so far: 3


Ronnie Gilkey

On Fri, 2005-07-01 at 12:18, Ronnie Gilkey wrote:
Hello all,

I am having trouble with filenames that are encoded with the ISO-2022-JP
unicode character set.

I have added the environment variables LC_ALL and LANG to my environment
and all other recommendations in the UNICODE.TXT file.  I have verified
that Anomy recognizes them using this piece of code inside of the
SanitizeFile subroutine:

open (ANOMYOUT,">/var/ronnie.$$") or die "Can't open file\n";
foreach my $envkey (sort (keys %ENV)) {
        print ANOMYOUT $envkey . "$ENV{$envkey}";
close (ANOMYOUT);

After the file comes out of anomy it has been renamed to:


If I set "feat_files = 0" the problem can be avoided, however I do not
want to turn of file sanitization.

Any thoughts?


Ronnie Gilkey


- 8< - - -
This mailing list's home page is:
There you can find subscription instructions and possibly an archive. is a free Icelandic mailing list service.
- - - >8 -