It's not necessarily File::Find::Rule that arbitrarily changes the representation of the file name.
I recall that a few years ago I had to test the compatibility of our application at $work with various operating systems, and there were differences related to unicode normalization: browsers on OSX tended to return accented characters typed into a password field in their decomposed form (basic letter + combining accent), while those on Windows and Linux returned the composed form (accented letter). Perhaps this reflects a widespread custom on these operating systems, or a feature in an underlying library.
You could try ls | xxd to check the actual representation of your file names in the file system. On my linux box most files (that have accented characters in their names) are in the composed form, but I've found a few that aren't.
In reply to Re: File::Find::Rule returns different filenames if they have chars with accents: OSX vs Linux
by kikuchiyo
in thread File::Find::Rule returns different filenames if they have chars with accents: OSX vs Linux
by bliako
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |