comment on

Jim has a point, but its not insurmountable, see

Win32::Unicode, Win32::Unicode::Native, Re^5: Is File::Find Unicode-(Conformant|Compliant|Enabled|Capable)?

stuffing stuff into global namespace should be possible with monkeypatching, for File::Find , File::Find::Rule.... or for CORE ... someone just has to do it or at minimum file a bug report

and what might be slightly harder is getting overload file test operators to work update they should work Re: Check if unicode directory exists
Bug #60888 for perl5: Win32: support full unicode in filenames (use Wide-system calls)
Bug #75000 for perl5: Unicode symbols damaged in $File::Find::name

so its 90% done, dare I say even 95%, just needs more tests and more bug reports and a little cooperation ...

In reply to Re^3: Trouble with File::Find::Rule (win32 unicode overload file test operators) by Anonymous Monk
in thread Trouble with File::Find::Rule by sowais

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks